After upgrading to Firebase Crashlytics 6.15.0, all crashes are missing dSYMs, and so are not being processed

[Brian Arnold]

I am having a problem with the latest Firebase Crashlytics (6.15.0) upload-scripts running without error, and failing to upload dSYMs.

The context is, I am adding a new build variant (via schemes) to an existing Xcode target that already has three build variants. The existing build variants were grandparented in to Firebase Crashlytics from Fabric, because they were added when the code base was still using Fabric. The existing variant and new variants each appear as separate apps in Firebase Crashlytics, and crash reports are flowing in as normal, except for the new variant. Since the new build variant can't be grandparented in from Fabric, I was forced to upgrade to the latest Crashlytics Firebase, which removes Fabric entirely. I updated the upload-symbols script, and removed all Fabric initialization, keys, etc. Each build variant has its own GoogleServices-Info-{$variant}.plist file, so I am passing in the -gsp parameter; the Firebase Crashlytics script recognizes that, and produces no errors when run.

However, when I force crashes in the app by adding a call to abort(), and try to view the crash reports Firebase Crashlytics, Crashlytics clearly knows about the crashes (it says so with a bright red banner of the number of unprocessed crashes, prompting me to "upload dSYMs") but since there are no dSYMs for any builds of this build variant, it shows no reports. When I then create a build of an existing build variant that was working before, and force that to crash, I can also see that it knows about the new build of the existing build variant, and is also missing its dSYM, under the dSYMs tab for that app.

I'm flummoxed because I am not seeing errors or warnings (even if I set up the upload-symbols script to run in Terminal with --debug), and yet, it's clearly not working. Here is a sample of the output with --debug:

% ${PODS_ROOT}/FirebaseCrashlytics/run -gsp [snipped] ${PODS_ROOT}/FirebaseCrashlytics/upload-symbols [snipped] --debug

upload-symbols 3.1 build 20

Running upload-symbols in Build Phase mode

Validating build environment for Crashlytics...

Arguments:

Debug mode enabled

Google App ID: [snipped]

Platform: ios

DSYM Paths: [snipped]

Validation succeeded. Exiting because upload-symbols was run in validation mode

The Console app is not indicating any specific errors when the background run of upload-symbols is run.

Any guidance with regard to debugging this issue, or resolving it, would be greatly appreciated. 

Thanks in advance, 

Brian

Electronic mail from Wellframe, Inc., 470 Atlantic Ave, 8th FL, Boston, MA 02210. Unless otherwise specified, any contact numbers provided by Wellframe are not secure and should not be used when discussing individual patient data. This communication is intended only for the use of the individual or entity named as the addressee. It may contain information which is privileged and/or confidential under applicable law. If you are not the intended recipient or such recipient's employee or agent, you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender by electronic mail and expunge this communication without making any copies. Thank you for your cooperation.

[Kevin Kokomani]

Hi Brian,

The first thing I want to make sure is that in your "Debug Information Format" in your build settings for each variant is set to "DWARF with dSYM" -- not having this set could result in some of the behavior you've noticed.

Barring that, could you try changing your build phase to just be the following?

${PODS_ROOT}/FirebaseCrashlytics/upload-symbols --build-phase --debug

Running it this way will have the added effect of making it look for the GSP automatically. If that doesn't work for you, make sure you're passing the correct GSP to each variant. Hope this works for you and let me know how it goes.

Cheers,

Kevin