-
-
Notifications
You must be signed in to change notification settings - Fork 338
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
Sourcemaps are not resolved in the errors #1169
Comments
Hi @varungupta85 does an error show above the event on the dashboard saying "Source Maps Not Found"? Can you also pass the event json? Thanks! |
hi @jennmueng, yes there is an error on the console saying "Source Maps Not Found". For e.g., check this event: https://sentry.io/organizations/acintyo/issues/2013423438/?project=98211&query=is%3Aunresolved+release%3Acom.galarmapp-3.10.0&statsPeriod=14d. What do you mean by the event json? Please let me know where I can find it and I will share that information with you. |
I see the following in the gradle output
Does it mean that I need to set the
|
@varungupta85 You can find the event json by clicking on "JSON" here: |
@jennmueng Thanks for your response. Setting the release to the updated value helped. |
OS:
Platform:
SDK:
@sentry/react-native
(>= 1.0.0)react-native-sentry
(<= 0.43.2)SDK version: 1.9.0
react-native
version: 0.62.2Are you using Expo?
Are you using sentry.io or on-premise?
If you are using sentry.io, please post a link to your issue so we can take a look:
https://sentry.io/organizations/acintyo/issues/2001332228/?project=98211&query=firstRelease%3A%223.9.1+%284%29%22
Configuration:
(
@sentry/react-native
)I have following issue:
The source maps are no longer resolved in the errors. They used to work fine. For example, check the following error: https://sentry.io/organizations/acintyo/issues/2001743680/?project=98211&query=firstRelease%3Acom.galarmapp-3.4.0. The source maps are resolved fine in this one but they are no longer resolved in my recent releases.
I used to set the
release
as<bundle-id>-<release-number>
but then I saw that in the recent releases, the source maps were tagged with release<release-number> (<distribution-number>)
on the Sentry console. So, I changed the call toSentry.setRelease
accordingly but that didn't help either.Steps to reproduce:
Actual result:
Actual place of error in the code not seen
Expected result:
Actual place of error in the code should be seen
The text was updated successfully, but these errors were encountered: