Stack traces stay minified after I uploaded source maps. Sentry is matching by release and file path, not Debug IDs, and I need to confirm the event’s release, dist, and minified abs_path line up with the uploaded artifacts.

Match the event release and dist to the uploaded artifacts, then match the minified frame abs_path to the artifact path. ~ stands in for protocol and host.

If you can use Debug IDs, use that path instead. See How do I verify Debug IDs for source maps?.

Open the event JSON and read the release and dist tags. Those values must match the artifacts on Project Settings → Source Maps.

If the SDK sets dist, the upload must use the same dist. If the event shows dist: null, the artifacts must have no dist.

[Screenshot: event JSON tags with release "vite1" and dist null.]

[Screenshot: Source Maps Artifact Bundles search for vite1. A bundle shows “1 Release associated” as vite1 and “No dists associated with this release”.]

Use the minified stack. In the event UI, open the frame to see the full URL. In event JSON, copy raw_stacktrace frame abs_path.

In this example the minified abs_path is http://localhost:3000/assets/index-5e0ef25e.js.

[Screenshot: event Stack Trace frame for /assets/index-5e0ef25e.js with tooltip http://localhost:3000/assets/index-5e0ef25e.js.]

[Screenshot: event JSON raw_stacktrace frame with abs_path http://localhost:3000/assets/index-5e0ef25e.js, filename /assets/index-5e0ef25e.js, lineno 1, colno 50914.]

~ replaces the scheme and host. It is not a glob. http://localhost:3000/assets/index-5e0ef25e.js matches ~/assets/index-5e0ef25e.js. It does not match ~/index-5e0ef25e.js.

[Screenshot: Artifact Bundle for release vite1 with minified ~/assets/index-5e0ef25e.js and source map ~/assets/index-5e0ef25e.js.map. That path matches the event abs_path.]

[Screenshot: Artifact Bundle with minified ~/index-5e0ef25e.js and source map ~/index-5e0ef25e.js.map. The assets/ folder is missing, so this path does not match.]

If abs_path includes a dynamic segment, use RewriteFrames so the frame path matches the uploaded artifact name.

Open the deployed minified file. It must contain a //# sourceMappingURL= comment that points at the map, for example //# sourceMappingURL=index-5e0ef25e.js.map.

Sentry matches the stack to the minified file, then follows that comment to the map. Upload both files. A CDN that strips comments can remove sourceMappingURL.

Sentry does not reprocess old events. Upload artifacts before errors occur. Only new events after the upload can use those maps.

See Legacy Uploading Methods. To see how a frame was resolved, see How were my source maps resolved?. If the debugger reports no errors and the stack is still wrong, see Why are my source maps still not working?.