Uploading Debug Symbols
Note
A new Cocoa SDK has superseded this deprecated version. Sentry preserves this documentation for customers using the old client. We recommend using the updated Cocoa SDK for new projects.
A dSYM upload is required for Sentry to symbolicate your crash logs for viewing. The symbolication process unscrambles Apple’s crash logs to reveal the function, variables, file names, and line numbers of the crash. The dSYM file can be uploaded through the sentry-cli tool or through a Fastlane action.
With Bitcode
If Bitcode is enabled in your project, you will have to upload the dSYM to Sentry after it has finished processing in the iTunesConnect. We also recommend using the latest Xcode version for submitting your build. The dSYM can be downloaded in three ways.
Use Fastlane
Use the Fastlane’s action, download_dsyms, to download the dSYMs from iTunesConnect and upload to Sentry. The dSYM won’t be generated until after the app is done processing on iTunesConnect so this should be run in its own lane.
lane :upload_symbols do
download_dsyms
upload_symbols_to_sentry(
auth_token: '...',
org_slug: '...',
project_slug: '...',
)
end
If you have a legacy API key instead you can supply it with api_key instead of auth_token.
By default fastlane will connect to sentry.io. For on-prem you need to provide the api_host parameter to instruct the tool to connect to your server:
api_host: 'https://mysentry.invalid/'
Use sentry-cli
There are two ways to download the dSYM from iTunesConnect. After you do one of the two following ways, you can upload the dSYM using sentry-cli.
- Open Xcode Organizer, go to your app, and click “Download dSYMs...”
- Login to iTunes Connect, go to your app, go to “Activity, click the build number to go into the detail page, and click “Download dSYM”
Afterwards manually upload the symbols with sentry-cli:
sentry-cli --auth-token YOUR_AUTH_TOKEN upload-dif --org YOUR_ORG_SLUG --project YOUR_PROJECT_SLUG PATH_TO_DSYMS
By default sentry-cli will connect to sentry.io. For on-prem you need to export the SENTRY_URL environment variable to instruct the tool to connect to your server:
export SENTRY_URL=https://mysentry.invalid/
Without Bitcode
When not using bitcode you can directly upload the symbols to Sentry as part of a build.
Use Fastlane
If you are already using Fastlane you can use it in this situation as well. If you are not, you might prefer the sentry-cli integerated into Xcode.
lane :build do
gym
upload_symbols_to_sentry(
auth_token: '...',
org_slug: '...',
project_slug: '...',
)
end
If you have a legacy API key instead you can supply it with api_key instead of auth_token.
By default fastlane will connect to sentry.io. For on-prem you need to provide the api_host parameter to instruct the tool to connect to your server:
api_host: 'https://mysentry.invalid/'
Upload Symbols with sentry-cli
Your project’s dSYM can be upload during the build phase as a “Run Script”. For this you need to st the DEBUG_INFORMATION_FORMAT to be DWARF with dSYM File. By default, an Xcode project will only have DEBUG_INFORMATION_FORMAT set to DWARF with dSYM File in Release so make sure everything is set in your build settings properly.
You need to have an Auth Token for this to work. You can create an Auth Token here.
- Download and install sentry-cli — The best place to put this is in the /usr/local/bin/ directory
- You will need to copy the script below into a new Run Script and set your AUTH_TOKEN, ORG_SLUG, and PROJECT_SLUG
if which sentry-cli >/dev/null; then
export SENTRY_ORG=example-org
export SENTRY_PROJECT=example-project
export SENTRY_AUTH_TOKEN=YOUR_AUTH_TOKEN
ERROR=$(sentry-cli upload-dif "$DWARF_DSYM_FOLDER_PATH" 2>&1 >/dev/null)
if [ ! $? -eq 0 ]; then
echo "warning: sentry-cli - $ERROR"
fi
else
echo "warning: sentry-cli not installed, download from https://github.com/getsentry/sentry-cli/releases"
fi
- If you are using Xcode 10 or newer, you also need to add the following line to the Input Files section in the Run Script from step 2:
${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}/Contents/Resources/DWARF/${TARGET_NAME}
By default sentry-cli will connect to sentry.io. For on-prem you need to export the SENTRY_URL environment variable to instruct the tool to connect to your server:
export SENTRY_URL=https://mysentry.invalid/
Manually with sentry-cli
Your dSYM file can be upload manually by you (or some automated process) with the sentry-cli tool. You will need to know the following information:
- API Key
- Organization slug
- Project slug
- Path to the build’s dSYM
Download and install sentry-cli — The best place to put this is in the /usr/local/bin/ directory.
Then run this (note that --auth-token
needs to go before upload-dif
):
sentry-cli --auth-token YOUR_AUTH_TOKEN upload-dif --org YOUR_ORG_SLUG --project YOUR_PROJECT_SLUG PATH_TO_DSYMS
By default, sentry-cli will connect to sentry.io. For on-prem you need to export the SENTRY_URL
environment variable to instruct the tool to connect to your server:
export SENTRY_URL=https://mysentry.invalid/