CODEWITHSUNDEEP
iosfirebasecrashlyticsxcode10firebase-console
Chris L
Chris L

Reputation: 61

Firebase Crashlytics console not showing crashes

After following the instructions to integrate Firebase / Crashlytics into an iOS project in Xcode 10.3, I am using Crashlytics.sharedInstance().crash() to test, but the crashes are not showing up in the Crashlytics console (I've waited up to 24 hours and see nothing).

I see this in the log

[Crashlytics:Crash] report submission successful

But nothing shows up in the console. It does show "I have 50% crash free users", but there is no stack trace and the Crashes show 0 as well.

From my Podfile:

pod 'Firebase/Analytics'
pod 'Fabric', '~> 1.10.2'
pod 'Crashlytics', '~> 3.13.4'

From my logs

[Crashlytics] Version 3.13.4 (143)
2019-08-29 12:13:08.435079-0500 App[58538:12666639]            

[Crashlytics] Running on iPhone11,8, 12.4.0 (16G77)
2019-08-29 12:13:08.443235-0500 App[58538:12766639]      

[Crashlytics:Crash:Reports:Event] Registered Firebase Analytics event listener

[Fabric] Initialized with kit versions: {
    "com.twitter.answers.ios" = "1.4.1";
    "com.twitter.crashlytics.ios" = "3.13.4";
    "io.fabric.sdk.ios" = "1.10.2";
}

In my build phases I have this code:

"${PODS_ROOT}/Fabric/run

and Input Files (I've tried many variations of this path, not sure if it's working correctly):

${BUILT_PRODUCTS_DIR}/GoogleService-Info.plist

also tried the original instructions path, trying to troubleshoot, but nothing changed.

Also, when I enable debug view, when it crashes I see app_exception come across the stream.

Upvotes: 4

Views: 5075

Answers (1)

Oleg Kodysh
Oleg Kodysh

Reputation: 1044

User reached out to Firebase customer support. The issue had to do with illegal characters in the form of whitespace being present in the version name of the app. Removing the white space seemed to restore proper crash reporting on the users Firebase Dashboard.

Upvotes: 1

Related Questions