Envelope meta debug_id doesn't match artifact's Debug ID, sourcemaps issue

[inomn]

Hi. I'm using Sentry self-hosted.
Can't get sourcemaps work properly.

Using:

"@sentry/react": "7.100.1",
"@sentry/webpack-plugin": "2.22.4",

Webpack:

sentryWebpackPlugin({
      authToken: ...,
      org: '...',
      project: 'frontend',
      url: '...',
      telemetry: false,
      sourcemaps: {
        assets: ['dist/**/*.js.map', 'dist/**/*.js'],
        filesToDeleteAfterUpload: 'dist/**/*.js.map',
      },
      release: {
        name: commitHash,
      },
    })

Sentry init:

Sentry.init({
    dsn: ...,
    environment: ...,
    enabled: ...,
    integrations: [],
    tracesSampleRate: config.sentry.tracesSampleRate,
    beforeSend: beforeSend,
    release: __COMMIT_HASH__,
  });

In the Envelop request (**** masked the actual domain, ignore):

"debug_meta":{"images":[{"type":"sourcemap","code_file":"****/main.1d689e1d484aed78849a.1728037760300.js","debug_id":"72f2a326-6611-40c7-be7f-310f83ab0cbc"}]}

And in Sentry artifact:

~/95f79a98-88ab-414f-9119-69ddda4d429b-149.js
Sourcemap Reference: main.1d689e1d484aed78849a.1728037760300.js.map
Debug ID: 95f79a98-88ab-414f-9119-69ddda4d429b

As a result (I guess that's the reason), this is how Error looks like:

Any suggestions what I'm doing wrong? Thanks!

[lforst]

What Sentry self hosted version are you using? Also do the logs of your self-hosted symbolicator service say anything?

[lforst]

oh crap. Do you know which ones?

[inomn]

@lforst it's an internal package from the internal registry, nothing for the community to worry about. I'll align with the team responsible for this package and check if it solves the issue (as soon as they exclude Sentry from the package). As I understand it is not a good practice to have Sentry in a library\package

I'll post an update later, at least for search\history purposes 👍🏻

[lforst]

Ok that's a relief. Thanks a bunch for raising this though. I think we may need to adjust the snippet to account for this. It is a case I havent thought much about yet but may become really critical in the future!

[inomn]

Hi @lforst , i can confirm that the issue in my case was because of Sentry setup inside of one of npm modules, which lead to multiple debug_id snippets in the bundle, and a mismatch between the debug_id sent by envelop request and the debug_id assigned to the artifact in the Sentry