Get readable crash reports in the Crashlytics dashboard

iOS+ Android Unity

By default, Firebase Crashlytics automatically processes your debug symbol (dSYM) files to give you deobfuscated and human-readable crash reports. This behavior is set when you add a run script that initializes Crashlytics to your app's build phase.

Unfortunately, there are a few cases that could cause your dSYM upload to fail, such as bitcode in your app or other unique project configurations. This guide provides some ways to troubleshoot when Crashlytics can't locate your app's dSYM.

Check if Xcode is producing dSYMs

More often than not, dSYM files go missing because Xcode simply isn't producing them. When an upload fails, Crashlytics displays a "Missing dSYM" alert in the Firebase console. If you get this alert, first check that Xcode is producing the correct dSYM for every build:

1. Open your project in Xcode and select the project file in the Xcode Navigator.

2. Select your main build target.

3. Open the target's Build Settings tab, then click All.

4. Search for "debug information format".

5. Set Debug Information Format to DWARF with dSYM File for all your build types.

6. Rebuild your app.

Your crash reports should now appear in the Firebase console. If the problem persists or you encounter other errors, try locating your dSYM and uploading it to Crashlytics manually.

Locate your dSYMs

Sometimes Crashlytics can’t locate your app's dSYM due to bitcode configurations or the console's connectivity. When this happens, there are two additional ways you can troubleshoot:

Download bitcode dSYMs from the App Store

Apple generates new dSYMs for bitcode-enabled builds that have been released to the App Store or submitted to TestFlight. If any of these apply to your app, download a new dSYM for it from the App Store:

1. Log in to App Store Connect, then click My Apps > Activity.
2. Select the build you want to download a dSYM for.
3. Click Build Details > Download dSYM.

Find dSYMs on a local machine

Run the following to display all your dSYMs' UUIDs on your machine, then search for the missing dSYM:

mdfind -name .dSYM | while read -r line; do dwarfdump -u "$line"; done

Once you find the dSYM, upload it to Crashlytics. If the mdfind command doesn’t return any results, you can look in the Products directory where your .app lives (by default, the Products directory is located in Derived Data). If your app is released to production, you can also look for its dSYM in the .xcarchive directory on disk:

1. In Xcode, open the Organizer window and select your app from the list. Xcode displays a list of archives for your project.
2. Control-click an archive to view it in Finder. Then, control-click it again and click Show Package Contents.

Within .xcarchive is a dSYMs directory that contains dSYMs generated as part of Xcode’s archiving process. Recompiled bitcode dSYMs are also downloaded to this folder when you use the Download dSYMs... tool in the Organizer window.

Upload your dSYMs

Note: upload-symbols is in the process of integrating with the rest of the Firebase CLI tools.

As a back-up, Crashlytics includes an upload-symbols script that you can call from anywhere in your build process to manually upload your dSYMs. The script provides more information about the upload process and more robust error messaging (for usage notes and additional instructions, run upload-symbols without any parameters).

To run the upload-symbols script, use one of the following options:

1. Include the following line in your build process:

   find dSYM_directory -name "*.dSYM" | xargs -I \{\} $PODS_ROOT/FirebaseCrashlytics/upload-symbols -gsp /path/to/GoogleService-Info.plist -p platform \{\}

2. Run the script directly from your terminal:

   /path/to/pods/directory/FirebaseCrashlytics/upload-symbols -gsp /path/to/GoogleService-Info.plist -p ios /path/to/dSYMs