Source maps not working with Angular+Webpack plugin

[SuNNjek]

Hi,

I'm trying to upload source maps as part of an Angular application build but for some reason, the stack traces still look mangled. I don't know what I'm doing wrong to be honest.

I suspect this is because the paths look wrong here:

The file in question is called 133.bc4ebc49840176eb.js.map, but the source map file path is just the debug ID it seems. I guess it can't find the file because the paths don't match. But I don't know where this name comes from, when I run the build locally these paths are nowhere to be found.

I have enabled source maps for the production build in my angular.json and the webpack config looks like this:

import { sentryWebpackPlugin } from '@sentry/webpack-plugin';
import { CustomWebpackBrowserSchema, TargetOptions } from '@angular-builders/custom-webpack';
import * as webpack from 'webpack';
import * as dotenv from 'dotenv';
import { version } from 'src/version.json';

import * as process from 'node:process';

// Load .env file
dotenv.config();

export default (
	config: webpack.Configuration,
	_options: CustomWebpackBrowserSchema,
	targetOptions: TargetOptions,
): void => {
	// Upload source maps to Sentry on production builds
	if (targetOptions.configuration === 'production' && process.env['SENTRY_AUTH_TOKEN']) {
		config.devtool = 'source-map';
		config.plugins!.push(
			sentryWebpackPlugin({
				url: '[redacted]',
				org: '[redacted]',
				project: '[redacted]',
				authToken: process.env['SENTRY_AUTH_TOKEN'],
				release: {
					name: version,
				},
				debug: true,

				sourcemaps: {
					filesToDeleteAfterUpload: './dist/**/*.map',
				},
			}),
		);
	}
};

The generated JS files have the R._sentryDebugIds = R._sentryDebugIds || {} and the debug IDs actually do match, it's just the path that's different.

Does anyone have a clue what I'm missing here?

[lforst]

Can you share a link to the event in question?

[SuNNjek]

No, I'm sending the event to a self hosted server that's not publicly accessible, sorry

[lforst]

If that is the case I recommend checking the logs of the symbolicator service of your self hosted instance.

[SuNNjek]

Sorry for kind of forgetting about this 😅 I don't have any control over/access to the logs the self-hosted instance either unfortunately but it was recently updated to the latest version and that seems to have done the trick

[kylekz]

I'm seeing something similar with 8.40.0 of the nextjs package on Vercel.

In the deployment build:

~/e783f4c8-ac7e-444a-9936-c08fc6573090-76.js (sourcemap at e783f4c8-ac7e-444a-9936-c08fc6573090-76.js.map, debug id e783f4c8-ac7e-444a-9936-c08fc6573090)
...
~/e783f4c8-ac7e-444a-9936-c08fc6573090-76.js.map
...
[@sentry/nextjs - Client] Info: Successfully uploaded source maps to Sentry

In Sentry on an error:

No Source Map With Matching Debug ID
You already uploaded artifacts with Debug IDs but none of the uploaded source maps had a Debug ID matching this stack frame's Debug ID: e783f4c8-ac7e-444a-9936-c08fc6573090

In Sentry the error refers to path: app:///_next/static/chunks/app/(profile)/profile/[nickname]/page-7047455800761a76.js

In the production build source, this is at the top of that file, as per the sourcemap troubleshooting page:

!function() {
    try {
        var e = "undefined" != typeof window ? window : "undefined" != typeof global ? global : "undefined" != typeof self ? self : {}
          , t = (new e.Error).stack;
        t && (e._sentryDebugIds = e._sentryDebugIds || {},
        e._sentryDebugIds[t] = "e783f4c8-ac7e-444a-9936-c08fc6573090",
        e._sentryDebugIdIdentifier = "sentry-dbid-e783f4c8-ac7e-444a-9936-c08fc6573090")
    } catch (e) {}
}(),

So the debug ID matches but it still can't find it. Here's the error: https://team-reflex.sentry.io/share/issue/de418fd6339d4805be1fabe24ed16aa6/

Configs can be found here:

• https://github.com/teamreflex/cosmo-web/blob/main/next.config.ts
• https://github.com/teamreflex/cosmo-web/blob/main/sentry.client.config.ts
• https://github.com/teamreflex/cosmo-web/blob/main/sentry.server.config.ts

[lforst]

This is a bit unrelated to this discussion. Do you have anything in your build logs?

[lforst]

Actually, we may have an issue with debug ID association at the moment. If you hard-pin your @sentry/cli subdependency to 2.36.1 things should get resolved, but we are on it as we speak.

[kylekz]

Pinning to 2.36.1 appears to have worked, thanks!