1. Verify your events come in from a sdk capable of using debug ids. You can view the sdk sent from the event at the bottom of the issue.
-
You must be on ≥7.47 of the Javascript Sdks
-
If you also use RewriteFrames, you need to be on ≥7.56 instead
- Debug Ids are also not yet supported in all Javascript sdks
2. Verify you are uploading artifacts to Sentry with a tool capable of debug Id Injection.
- Either sentry-cli >2.17.0 or the Javascript Bundler Plugins >2.0.0
- Nothing else is supported! Other tools from our repo, such as our Github action release plugin or our Netlify plugin are not capable of injection.
- When using the sentry-cli with the wizard, verify with the user that the wizard is properly creating the inject command (sentry:sourcemaps) into their package.json
3. Verify there is a debug id being sent to Sentry as part of the event payload. Search for the debug_meta key inside the event’s JSON
- There should a unique id for each file in the stack trace
- The debug_ids will be in the JSON regardless of whether a matching source-map debug id is found/exists
- If you do not have a debug_meta key in your event’s JSON, you may not be deploying the post injected source file. You must inject debug ids before you deploy for the ids to exist in your events. You must also be running the same files as the ones that were injected for debug ids to exist.
4. Verify there is a file with a matching debug id being uploaded prior to when the event was sent. Copy the debug_id from the JSON and search for it in your uploaded artifacts.
-
If using our Javascript Bundler Plugins, the filename is replaced with the debug id
-
Searching for the debug id returns the bundle that includes that specific debug id.
- Bundle Ids are essentially meaningless and should be ignored when debugging
5. Verify that your source maps were uploaded before the events! Once an issue has been processed, it will not be processed again. There is no reprocessing of old events with newly uploaded maps.