- Integrate the SDK as described in the Getting Started with React Native documentation.
- Upload the symbols that are created with each build using the Incoming page under the app.
- Add a test crash to the app’s code by calling the
generateTestCrashmethod of the crash reporting module as an action to a button.
- Run the app without the debugger connected, crash it and restart it.
- After a few minutes the crash report should be visible in the UI.
The commands below will generate the source map for release builds:
react-native bundle --entry-file index.ios.js --platform ios --dev false --reset-cache --bundle-output unused.jsbundle --sourcemap-output index.ios.map
The Mobile Center Build service automatically generates a valid dSYM and source map .zip file, and uploads it to the Crashes service, meaning you can skip all these steps.
- Open the Incoming page under Crash Reporting on Mobile Center of the app.
- Upload the zip file.
- After the zip file is indexed by Mobile Center new incoming crashes will be symbolicated.
How does Mobile Center parse your .zip file?
Mobile Center first looks for dsym directories at any level. Then it looks for a source map by the title of “index.ios.map”. If “index.ios.map” does not exist, it uses the first “.map” file that is found.
Why are crash reports not visible after a few minutes?
Right now crash reports are only visible if they can be symbolicated. For that to happen the proper symbols (dSYM) need to be uploaded. There will be a UI available later that shows which symbols are missing and how to find them.
What could be another reason for the crash report to not appear?
Make sure the app doesn’t crash on startup, as the SDK wouldn’t have time to send the crash report. This is a limitation for any 3rd party crash reporting service.
The symbols are uploaded but the previous crash reports are not appearing.
As of now only new incoming crashes will be symbolicated. Processing pending crashes is on our roadmap.