What is needed for crashes to show up after Fabric Firebase migration?

Question

There's an application, we performed the migration about a week ago. I receive Daily Summary and the Oct 11th indicates some crashes (more specifically ). When I try to view any crashes either through Fabric Crashlytics UI or Firebase Crashlytics UI I don't see anything although I try to view all versions of the said app.

Although the migration guide ( https://fabric.io/firebase_migration ) says "Continue using the Fabric Crashlytics SDK and API key in your app." and it seems no code change is needed. However I know that the Fabric and Crashlytics pods in our app are more than 2 years old. This SO answer https://stackoverflow.com/a/54575731/292502 mentions versions, just as well https://firebase.google.com/docs/crashlytics/get-started

Also, do I have to add the GoogleService-Info.plist and the Firebase pod as shown in https://medium.com/@niamhpower/the-great-migration-moving-from-fabric-to-firebase-as-an-ios-developer-7b61a8b40008 ? (and I saw that plist in some Firebase 1-2-3 guide - I cannot find now - as well)

Can it be some missing DSYMs? We may have some OOMs (out of memory), but the numbers don't align up, I expect to see some crashes, some users reported it.

Answer 1

As far as i know adding a GoogleInfoPlist is required. If it is added, delete it and move to trash (dont remove referrences) and then add it again.

1.Run your app from Xcode to install it on the simulator or your device

2.Press the Stop button in Xcode to quit it

3.Launch your app from the home screen to run it without the debugger

4.Press the “Crash” button to trigger the crash

5.Run the app again from Xcode so it can deliver the recorded crash to Crashlytics Within a few minutes, you should see the crash appear on your Firebase Crashlytics Console.

Also make sure in your build settings you have set Debug Information Format to DWARF with dSYM . Also if i be honest the fabric migrationn is a little hectic, the best way to go bout it is to select start new crashlytics project instead of migration from fabrics and download the plist and add in your project folder

Answer 2

Looks like adding the dSYM files were the key for crashes to populate in the dashboard statistics. I'm still investigating with my iOS developer why it was missing or was it just in an old format (not the DWARF format the tutorials mention).

I spoke with Firebase Support about this and if there's no dSYM then they cannot symbolicate and unroll the crash call stack and right now this causes them to not contribute to the dashboard numbers. Support filed a ticket in their internal ticketing system to provide raw call stack in such cases - and potentially this would help with the crashes to populate the dashboard.

---

Also, based on this - and in accordance what the migration guide says - the Firebase pod and plist is not required to get going when you migrate from Fabric Crashlytics to Firebase Crashlytics.