Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gradle plugin expects DSN for build #703

Closed
jasonab opened this issue May 2, 2024 · 7 comments
Closed

Gradle plugin expects DSN for build #703

jasonab opened this issue May 2, 2024 · 7 comments

Comments

@jasonab
Copy link

jasonab commented May 2, 2024

Integration

sentry

Java Version

21

Version

4.5.1

Steps to Reproduce

gradle clean build

Expected Result

No error message from Sentry

Actual Result

error: Auth token is required for this request. Please run sentry-cli login and try again!

Add --log-level=[info|debug] or export SENTRY_LOG_LEVEL=[info|debug] to see more output.
Please attach the full debug log to all bug reports.

@jasonab
Copy link
Author

jasonab commented May 2, 2024

Note that our DSN is stored in AWS param store, and is therefore loaded dynamically at runtime. I expect this would also be an issue if I had the DSN in a Spring properties file.

@markushi
Copy link
Member

markushi commented May 3, 2024

@jasonab thanks for reaching out! Just for clarification, could you answer the following questions:

  • Are you building an Android app? And if so, do you apply our io.sentry.android.gradle plugin? And which version?
  • Does the error message cause the build to fail?

@jasonab
Copy link
Author

jasonab commented May 3, 2024

This is a Spring application, not Android - I was using v4.5.1. The build did not fail, but was noisy.

@markushi
Copy link
Member

markushi commented May 6, 2024

@jasonab, alright thanks for getting back! We have identified the issue and are working on a fix now!

@markushi markushi transferred this issue from getsentry/sentry-java May 6, 2024
@romtsn
Copy link
Member

romtsn commented May 16, 2024

I believe this should be tackled by #708 now

@romtsn romtsn closed this as completed May 16, 2024
@romtsn
Copy link
Member

romtsn commented May 16, 2024

hey @jasonab the issue has been addressed in the version 4.6.0, which just has been published. Please give it a try and let us know. Thank you!

@jasonab
Copy link
Author

jasonab commented May 16, 2024

yes, I can confirm the problem is fixed - thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Archived in project
Status: Done
Development

No branches or pull requests

4 participants