Sourcemaps from Angular are not used on self-hosted Sentry

Our self-hosted Sentry previously showed de-minified stacktraced using sourcemaps uploaded in build pipeline via sentry-cli. At some point, either on Sentry or Angular update, this stopped working.

Currently we use Sentry 24.9.0 and Angular 19 (though it hasn't worked since at least Angular 17)

Observations:

• Gitlab Pipeline log shows successfully created Sentry release, uploaded sources and sourcemaps
• an issue from the same release shows only minified code
• deployed chunks (referenced in the issue) include debugId (e.g. https://app.dev.dev.luucy.ch/chunk-3KXWWWJQ.js )
• release referenced in the issue shows 216 sourcemap artifacts including sources and sourcemaps - both paired via debugID (corresponding to the one in deployed chunks)

Suspicious observations:

• Sentry endpoint returns empty list of files associated with the release: https://sentry.zensys.cz/api/0/projects/sentry/luucy-fe/releases/fe@3.9.0-0a6cb1d/files/
• And so does sentry-cli: sentry-cli files list --release fe@3.9.0-0a6cb1d --log-level=debug returns empty list

That's strange, since in Sentry UI the issue, release and sourcemap artifacts seem to be linked properly. It shouldn't even matter if I understand correctly, since the mapping should be done by the debugIds.

Any ideas what could be the culprit or how to continue with debugging?





Continue reading...