-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Chromium update: use_dynamic_url property set to false causes errors to not be reported with stack trace #14003
Comments
Auto-routing to @getsentry/product-owners-issues for triage ⏲️ |
@ReneGreen27 maybe I'm misunderstanding, but this seems like an SDK problem, is there a reason it was sent to issues? |
@mrduncan this was automatically routed to Issues, I will manually reroute to javascript SDK repo |
@ReneGreen27 could you get more context on this issue? Is the SDK in this case running in a custom browser extension? |
@ReneGreen27 are they uploading sourcemaps to Sentry? It sounds to me like they rely on the sourcemap url in sourcemaps. A more robust solution would be to use the Sentry CLI or one of our bundler plugins to inject debug ids into their sourcemaps and upload them on build to Sentry which should not be affected by the |
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Chrome 130 is where the customer sees this change occur.
When use_dynamic_url property is set to false this causes errors to not be reported to Sentry properly with a stack trace/ associated sourcemaps. Flipped back to true errors and associated stack traces are correctly reported. Customer is concerned this will not be a viable solution for long: see this Chromium issue thread: https://issues.chromium.org/issues/363027634
They were able to replicate this in both React and Browser sdk
Expected Result
To be able to set use_dynamic_url property to false and still have errors and associated sourcemaps reported properly
Actual Result
When set to true, they see reported errors without any stack trace and reported errors without any reference to source maps.
Product Area
Unknown
Link
No response
DSN
No response
Version
No response
The text was updated successfully, but these errors were encountered: