React Native Source Maps

Symbolication guide

See our symbolication guide for a higher-level overview of integrating uploads into your build systems to see full stacktraces for all your releases.

FAQs

Why isn’t the uploaded source map getting applied to my error?

If the uploaded source map is not being applied correctly, you should verify that:

• The error event was received after the source map was uploaded
• The codeBundleId uploaded with the source map matches that of the app generating the error (if pushing bundles independently to native app builds) or
• The appVersion/appVersionCode/appBundleVersion uploaded with the source map matches that of the app generating the error
• The platform uploaded with the source map matches that of the app generating the error
• The dev flag uploaded with the source map matches the value used when generating source map files with react-native bundle

Where can I see the details of the source maps that I’ve uploaded?

Uploaded source maps can be viewed and deleted by going to Source maps in the project setting page on your dashboard.

How do I delete source maps I’ve uploaded?

Uploaded source maps can be viewed and deleted by going to Source maps in the project setting page on your dashboard.

Do the uploaded source maps get applied retroactively to existing errors?

Once a source map is uploaded it will only get applied to new error events. It does not get applied retroactively to existing errors events.

Why is my mapped stacktrace showing the wrong line of code?

If the stacktrace has been mapped but is pointing to the wrong line of code, it’s often due to the wrong bundle/source map file being uploaded for the file in the reported stacktrace.

See the React Native build integration guide for guidance on different bundle types.