Chromium update: use_dynamic_url property set to false causes errors to not be reported with stack trace

[ReneGreen27]

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

[getsantry]

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

[mrduncan]

@ReneGreen27 maybe I'm misunderstanding, but this seems like an SDK problem, is there a reason it was sent to issues?

[ReneGreen27]

@mrduncan this was automatically routed to Issues, I will manually reroute to javascript SDK repo