Description
Is there an existing issue for this?
- I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
- I have reviewed the documentation https://docs.sentry.io/
- I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/browser
SDK Version
9.2.0
Framework Version
No response
Link to Sentry event
No response
Reproduction Example/SDK Setup
There is a sandbox app where the issue happens and more details on how it is configured are available in this internal ticket
See the internal comment from 28/02 with a summary of information.
Steps to Reproduce
- Add the Browser SDK to an app with nested iFrames.
- Use webpack plugin to upload source maps to Sentry
sentryWebpackPlugin({
authToken: SENTRY_AUTH_TOKEN,
org: <redacted>,
project: 'editor',
telemetry: false,
});
- Throw an error in the iFrame
Expected Result
The event sent by the SDK has source maps debugIDs attached to them.
Actual Result
The event does not have the DebugID reference under debug_meta
.
Because webpack rename the uploaded files, the fallback of matching abs_path to the uploaded source maps also also fails. Source maps are hosted internally with no access from outside, thus source map fetching also fails.
I can confirm that the minified file has the correct debugID, which is found in the uploaded files to Sentry:
Minified file contains:
p._sentryDebugIds[u]="9ef9d18e-3246-411d-9336-512a031cf002"
...
SENTRY_RELEASE={id:"a5fffa11f6d7735ecd9ddea4d9fd56d64f2b85e1"};
Screenshot from project settings with the uploaded file:

Metadata
Metadata
Assignees
Type
Projects
Status