Crashlytics: "We'Re Missing a Dsym to Process Crashes"

Firebase Crashlytics: Upload missing dSYMs to see crashes from 1 versions.(iOS)

I have been having this same issue for a while and I was finally able to resolve it, thought I would share what worked for me:

For context, I am working on a larger app which uses several Cocoapods.

I found that same red banner on my Firebase Crashlytics page and after following all of their instructions I was still seeing it.

I tried the "archive/find .dSYMs/upload manually via terminal" solution several times to no avail.

Finally, I decided to download the .dSYMs from iTunesConnect.

[Your App] > Activity > [Desired Build Number] > Download dSYM

I then uploaded those .dSYMs manually and within minutes Firebase Crashlytics was happy and showing the crash reports.

UPDATE

Google has added a swanky .dSYM upload feature on the Firebase Crashlytics dashboard, no more uploading from the terminal.

Edit on March 16, 2020.

Google is soon removing the upload feature on the Firebase Dashboard. An uploader script should be used from the terminal to upload dSYMs to Firebase. See Google's instructions here.

Why Crashlytics is asking for missing DSYM file every time?

TL;DR

Everytime you recompile your project after adding a line of code, the dSYM changes because the address of your lines of code in the resulting binary is not the same.

You can look at Fabric docs about uploading dsym to automatically upload your dSYM by adding a build phase or use the Fabric pod instead of just Crashlytics which apparently adds a build phase automatically like @ekscrypto said.

If you still want to do this manually, open your xcarchive where you can find your dSYMs and upload them to crashlytics

More details

dSYM is short for debug SYMbols. This helps crashlytics resolve the crash logs it receives and helps display detailed information about the crashes/bugs that can occur.

When you archive your app, you're left with *.xcarchive "file" which really is a folder that you can browse. Inside this xcarchive, you should have a dSYM folder where your dSYMs are.

To view it, first open organizer window in XCode (Window > Organizer or cmd+shift+6), right click on the last archive and click "Show in Finder". On the Finder window that opens, right click the last xcarchive for your app and click on show contents (sorry the picture is in french)

This takes you inside your xcarchive where you can see the dSYMs for your app

Uploading this to crashlytics should solve your issue

iOS - Crashlytics missing dSYMs to process crashes

Thanks for reaching out on this, Todd from Fabric.

We do not currently support WatchOS crashes. We tested heavily when watchOS 2 came out, but unfortunately there were many changes to the APIs in that version. One of the changes heavily restricted our ability to capture information reliably and also get that information out. Since we couldn't do this reliability without using private APIs, we don't have support for it.

Thanks!

---

Related Topics