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.