Sentry Source Maps Not Working

How to fix it

Try these in order — the most common fix is first.

1. 1. Make sure source maps are generated

   Copy steps
   1. Enable sourcemap output (webpack devtool 'source-map', Vite build.sourcemap: true)
   2. Rebuild and confirm .map files exist
   Did this fix it? Yes No

2. 2. Upload with the same release

   Copy steps
   1. Use the Sentry bundler plugin or sentry-cli to upload maps during the build
   2. Set the same release value in Sentry.init
   3. Check Project Settings > Source Maps for a Debug ID on each bundle
   Did this fix it? Yes No

3. 3. Trigger a new event

   Copy steps
   1. Events already processed are not reprocessed
   2. Throw a fresh error after the upload and check the new issue
   Did this fix it? Yes No

Symptoms

Stack traces show minified code, or an issue banner says 'Source code was not found'.

Why it happens

• Build tool does not generate source maps
• Maps uploaded after the first event for that issue
• Release in the SDK differs from the release used at upload
• Stack trace paths do not match uploaded file paths

This guide also covers

• sentry source maps not working
• sentry minified stack trace
• sentry source code was not found

Other Sentry errors

• Sentry Events Not Showing Up
• Sentry Blocked by Ad Blockers (Tunnel Fix)
• Sentry Quota Exceeded: What Happens and How to Fix It
• Sentry Too Many Alerts and Noisy Errors
• Sentry Alert Emails Not Received
• Sentry Self-Hosted Upgrade Failed
• Sentry Next.js Not Sending Events
• Sentry Spans and Performance Quota Running Out