Missing (or invalid) dSYMs

Hi,

We are using Firebase Crashlytics to collect crashes from our app. Firebase Crashlytics says that the dSYM is missing to process crashes for the recent two versions of our app. We have recently not changed anything in our app distribution process (it is based on CI/CD). For the non-product change, we moved one of our internal frameworks to be managed by SPM (previously Carthage).

In build settings, we have set :

  • Debug information format: DWARF with dSYM Files
  • Enable bitcode: Yes

Because of the latter, we manually download all dSYMs from the AppStoreConnect page and upload them to the Firebase Crashlytics for each new version.

I've double-checked the UUID's and the one mentioned by Firebase is missing in the downloaded (from the AppStoreConnect) zip file. The zip file contains dSYM for our app but with a different UUID.

Is there anything I can do to verify that generated dSYMs have the correct UUID?

Not sure if this is related, but when I try to download crashes via Xcode Organiser, I got an error:

Unable to download crash information.

An error occurred preventing Xcode from downloading updated crash information. The value “2021-07-27T00:00:00Z” is invalid. Please try again later.

Answered by MatKuznik in 686758022

It looks like someone (Apple or Firebase) has fixed the issue. We can see crashes reports for the recent release. Can anyone confirm?

Anyone else running into the problem AGAIN as well?

We also had the problem back then in August, then it started working again, and now it seems to be broken again. I applied the same UUID fix as back then and that does the trick.

Created another bug report FB9735670 @edford

Same issue FB9751225

Apple seems to have fixed it again. Can anyone else confirm? @MatKuznik @dkdd

And it is gone again for me....

Missing (or invalid) dSYMs
 
 
Q