fabric.io missing dSYM even after upload

Asked 11/12, 2015 at 13:7 Answered 30/8, 2017 at 18:41

I have the error: "It looks like we are missing dSYMs to process crashes for the versions below." - I have downloaded the dSYMs in the Xcode organiser, found the .xarchive and zipped the corresponding dSYMs folder and uploaded with success; but the error does not disappear i.e. does nothing:

How can I symbolicate my crash reports?

dSYM Folder:

Freda answered 11/12, 2015 at 13:7 Comment(13)

are you uploading just the .dSYM zipped up? – Polychasium 11/12, 2015 at 13:15

I've tried zipping the whole folder, all the dysms together and just the dsym for the app target – Freda 11/12, 2015 at 13:22

Thanks @Freda - try running this command to get the exact dSYM that is missing in a terminal: mdfind "com_apple_xcode_dsym_uuids == <UUID>” Then, take the .dSYM, zip it up and upload and that should work. – Polychasium 11/12, 2015 at 14:23

I used mdfind to get the archive, but which .dSYM file should I zip, there are multiple? – Freda 11/12, 2015 at 14:35

added a picture of my dSYM folder @MikeBonnell – Freda 11/12, 2015 at 14:39

Hmm, that should have worked if you uploaded just the xxx.app.dsym, zipped up. Can you send over the zipped dSYM to support(at)fabric(dot)io for me to look into further? – Polychasium 11/12, 2015 at 14:44

thanks, I've sent that over @MikeBonnell – Freda 11/12, 2015 at 14:47

uploaded a new build - exact same problem – Freda 14/12, 2015 at 15:42

Having the same issue. With all the projects. Did you get this resolved? – Florous 2/2, 2016 at 12:7

nope, it sometimes works, sometimes doesn't. – Freda 2/2, 2016 at 12:8

make sure you don't make or use more than 1 build with the same version/build number – Freda 2/2, 2016 at 12:10

@MikeBonnell this is still happening for me – Freda 15/3, 2016 at 11:8

@Freda I'd recommend checking out the improved documentation around this: docs.fabric.io/ios/crashlytics/missing-dsyms.html – Polychasium 15/3, 2016 at 12:34

I just had the same issue and searching for solutions brought me here. Since this is missing an answer and I solved the issue for me, I'll resurrect this question to maybe help others having the same issue in the future.

Below the part shown in your first screenshot, there should be a list "REQUIRED (These are needed before crashes can be processed)" stating which UUIDs are still missing their dSYM and from which Build they are.
Just download the dSYM of the respective Build(s) like stated in the official Docs » Crashlytics » All about Missing dSYMs.
(E.g. log into iTunes, select the respective Build and click on download dSYM at the Build Details screen)

The downloaded dSYM(s) can simply be manually uploaded as you already did the other file(s).

Repugnant answered 20/1, 2017 at 10:30 Comment(0)

I've tried almost all the variants, described here on stack overflow and on Fabric info page, to solve the same issue. But, unfortunately, none of them helped. And I've found a new solution, which I haven't seen here on Stackoverflow and which fitted me.

I've integrated HockeyApp with the project of my app and uploaded the build into HockeyApp (the build is uploaded there with an archive which contains dSYMs). After that the crashes started finally appearing on Crashlytics as symbolicated crashes with details.

Comprehend answered 3/8, 2017 at 14:6 Comment(1)

One thing of note: this will also work with Crashlytics Beta. – Foretoken 3/8, 2017 at 14:40

I just had the same issue. The reason was enabled bitcode. So disable it or download dSYMs from iTC and upload them manually. I didn't find bette solutions yet.

Ibo answered 30/8, 2017 at 18:41 Comment(0)

Recommended topics

Hot tags