Upload dSYM files to allow Bugsnag to show human-friendly function names, file paths, and line numbers in your iOS, macOS, and tvOS stacktraces.
The symbolication guide provides instructions for configuring your app release process to automate finding and uploading dSYM files to Bugsnag, based on your project settings. Once configured, dSYM files will be uploaded automatically.
To locate dSYM files for upload, see the symbolication guide section on troubleshooting missing dSYM files. The guide breaks down the different steps required for configuring symbolication based on project settings
Symbolicating crash reports requires the contents of the dSYM
binary. To upload, send a POST request to
https://upload.bugsnag.com (or the
address of your upload server, if using Bugsnag On-premise) with the
apiKey- the API key of the project the dSYM should be applied to
dsym- The dSYM file to upload as a form-data file upload. Can be either:
Contents/Resources/DWARFand generally has the same base name as the .dSYM file itself.
projectRoot(optional) - the root path of the project on the filesystem where the application was built. This will be stripped off from the file name in the displayed stacktraces and improves error grouping for errors reported from the same location within the app but with a different project root
Here is an example request using cURL, where the
@ sign indicates that the
dsym parameter is an uploaded file:
curl --http1.1 https://upload.bugsnag.com/ \ -F apiKey=your-api-key-here \ -F dsym=@MyApp.app.dSYM/Contents/Resources/DWARF/MyApp \ -F projectRoot=/Users/joebloggs/workspace/MyApp