Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Switch from Fabric to Firebase Crashlytics problem: The Crashlytics build ID is missing

After switch from Fabric to Firebase Crashlytics SDK I have a problem. Problem is as in the title: The Crashlytics build ID is missing. This occurs when Crashlytics tooling is absent from your app's build configuration. Please review Crashlytics onboarding instructions and ensure you have a valid Crashlytics account.

I have json file generated from console(double checked these and keys with everything else looks ok). I have libs added in gradle. I'm calling 'throw new RuntimeException("Test Crash");' and getting an error with build ID which I have no idea what it is...

like image 302
P.S. Avatar asked May 04 '20 14:05

P.S.


People also ask

Is Crashlytics deprecated?

Old versions of your app still using the Fabric Crashlytics SDK will not break once it's deprecated, however they will no longer submit crash reports. But it seems like it will just continue to work as per normal after this date until further notice. Just leave it the way it is.

What happened to Crashlytics?

In January 2017, Crashlytics and Fabric were acquired by Google. In September 2018, Google announces that Fabric will be deprecated and developers should use Crashlytics via Firebase.


2 Answers

Seems like instruction could have been missed out

apply plugin: 'com.google.firebase.crashlytics'
like image 156
Vairavan Avatar answered Oct 07 '22 00:10

Vairavan


Be sure to have 2 things below: In the root build.gradle:

buildscript {
    ...
    dependencies {
        ...
        classpath 'com.google.firebase:firebase-crashlytics-gradle:2.5.0'
    }
    ...
}

and under app/build.gradle:

...
apply plugin: 'com.google.firebase.crashlytics'
...
like image 6
Tô Minh Tiến Avatar answered Oct 06 '22 23:10

Tô Minh Tiến