-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
So I'm using debug IDs, but Issue Details is telling me to setup Releases #47229
Comments
Routing to @getsentry/issue-experience for triage, due by Thursday, April 13th at 5:00 pm (sfo). ⏲️ |
Routing to @getsentry/telemetry-experience for triage, due by Friday, April 14th at 15:55 (vie). ⏲️ |
Routing to @getsentry/telemetry-experience for triage, due by Friday, April 14th at 15:59 (vie). ⏲️ |
Routing to @getsentry/issue-experience for triage, due by Thursday, April 13th at 5:00 pm (sfo). ⏲️ |
@Jesse-Box The bot will only allow you to use one label if an issue is untriaged |
Thanks for the heads up @hubertdeng123 ! |
Since we removed these alerts we can close this. #55662 works on giving users proper feedback on their source maps setups. |
Problem
When any
in-app
frame within a given stack trace isn't solved, irrespective of SDK version, we tell the user to set up releases. This is an issue because with the introduction of artifact bundles and debug IDs, a user is more likely to resolve their source map issues with debug IDs than releases.Acceptance Criteria
If an event has unresolved
in-app
stack frames, we show the below message and direct them to the uploading source map docs pageDesign
Userflow can be found here
Ticket blocked by
#47968
The text was updated successfully, but these errors were encountered: