Skip to content

Error events from nested iFrame do not contain source map debugID reference. #15535

Closed as not planned
@rodolfoBee

Description

@rodolfoBee

Is there an existing issue for this?

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

  1. Add the Browser SDK to an app with nested iFrames.
  2. Use webpack plugin to upload source maps to Sentry
sentryWebpackPlugin({
authToken: SENTRY_AUTH_TOKEN,
org: <redacted>,
project: 'editor',
telemetry: false,
});
  1. 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:

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugPackage: browserIssues related to the Sentry Browser SDK

    Type

    No type

    Projects

    Status

    Waiting for: Community

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions