Crashlytics: "We're missing a dSYM to process crashes" [closed]

Solution 1:

I ran into the same problem today. It seems that iTunes Connect is recompiling apps with bitcode so that the UUID changes, and the dSYM inside the .xcarchive can't actually be used to symbolicate the app (this appears to be a new development).

You can download the correct dSYM from iTunes Connect. Login, go to My Apps, select your app, then tap on the Activity tab at the top. Tap on the relevant build, and, assuming the app was submitted with symbols in the first place, you should see the option to "Download dSYM."

The file you get is called dSYMs (without an extension) but it is in fact a zip file. Add the .zip extension, unzip, and you'll find your dSYM(s) inside.

You can upload this .zip file directly to Crashlytics and you should be all set.

The solution was posted here: https://twittercommunity.com/t/not-matching-uuid-bitcode/61000

Solution 2:

There is another way to get to your dSYM.

From the organizer, right click on the archive and select "Show in Finder"
Right click on the .xcarchive shown in Finder and select "Show Package Contents"
Copy the "dSYMs" folder found inside to somewhere else.
Compress the "dSYMs" folder and upload it to Crashlytics.

Solution 3:

If anyone cannot find the dSYM file in the .archive package or on iTunes Connect like me, please check Build Settings -> Debug Information Format -> Release -> DWARF with dSYM File is correctly set.

Solution 4:

@Shawn's answer actually helped me fix this permanently for my instance, with no need to upload dSYMs manually. Basically go to Build Settings and then turn on these parameters:

Debug: DWARF with dSYM File
Release: DWARF with dSYM File
Enable Bitcode: No

This seems to work well when you've NOT gone through the iTunes Connect path yet and just want to test your app with Crashlytics in the "development" mode.

Solution 5:

Check in your Build Settings that your Debug Information Format is “DWARF with dSYM File” for both Debug and Release.

Features