Develop Reference

Crashlytics Fabric.io deprecated

Does anyone know what the proper way to implement Crash report using Firebase in Android application?
I have read Firebase crashlytics doc in that mention implement Fabric.io. Fabric.io is deprecate and in there document mention removed fabric.io dependency.
Firebase
https://firebase.google.com/docs/crashlytics/get-started?platform=android
Fabric.io reference
https://docs.fabric.io/android/examples/sampleapp/index.html
Without fabric.io dependency I am getting below error
java.lang.RuntimeException: Unable to get provider com.crashlytics.android.CrashlyticsInitProvider: io.fabric.sdk.android.services.concurrency.UnmetDependencyException: 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.`
Note:
Please compare the steps in both reference, I have go through all the links but didn't find the proper way that's why I am asking here.
I am sure no 1 go through the links, that's why getting down vote great. I have attached the Firebase and Fabric.io document steps screen

Late post
Here is the solution, first of all remove all the fabric.io related reference and code.
In the main gradle.build project level
buildscript {
ext.kotlin_version = '1.4.0'
repositories {
google()
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:4.0.2'
classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
// Add this line
classpath 'com.google.firebase:firebase-crashlytics-gradle:2.3.0'
}
}
Next, in the build.gradle app level
apply plugin: 'com.google.firebase.crashlytics' // add this line at top
and in the dependency area
dependencies {
implementation 'com.google.firebase:firebase-crashlytics:17.2.2' // add this line
}

If you really want to remove the Fabric SDK from your app and use the Firebase SDK, Follow the Upgrade to the Firebase Crashlytics SDK
This guide describes how to upgrade to the new SDK from the Fabric Crashlytics SDK. It describes the changes that come with the new APIs, the reason for the changes, and how to update your code, if required.
docs.fabric.io you can get the following information, So I don't know why you have so many down votes, this is a legit question IMHO. Maybe because you didn't do this research yourself which I just did here.
You can continue using the Fabric Crashlytics SDK in your apps until a deprecation date is announced. Once the Fabric Crashlytics SDK deprecation date is announced you will need to upgrade to the new Firebase Crashlytics SDK. 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.

Are you talking about this?
apply plugin: 'io.fabric'
According to the documentation in here,
Crashlytics has been integrated into Firebase, with new Firebase-only
features. New apps should use Crashlytics in Firebase to get access to
the latest updates and features. Fabric Crashlytics and the Fabric
dashboard will be available until March 31, 2020 for existing users.
My guess is that, it might be - Let's call it grace period ;) up until every other user migrates it and they migrate every other tool from Fabric.
By the end of March 31, 2020 everything related to Fabric might be removed. Hope I answered what you were stating about.

One of the problems is that the Google page omits the android tutorial in languages other than English. (it can happen by bug. It happened to me.)
Ok ... I'm not very experienced with Crashlytics, and looking to make the migration I came across exactly these links that you showed and I was also confused.
But as I understand it, Fabric Crashlytics was acquired and incorporated into Firebase, so the first tutorial is old, when there was a need for the Fabric library to implement Crashlytics in Firebase.
The second tutorial does not seem to want to specify which new libraries will be implemented.
The best tutorial I found is this:
Oficial:
https://firebase.google.cn/docs/crashlytics/upgrade-sdk?platform=android#kotlin+ktx_5
or:
https://medium.com/#onkart10/migrating-from-fabric-to-firebase-crashlytics-e8819933c484
I hope it helps others.

I cannot view crash detail of Firebase Crashlytics for android and got stuck on "Build and run your app"

I try to setup Firebase Crashlytics after done setup Firebase.
The crashes was sent successfully.
Which I can see them in firebase dashboard.
But When I enter crashlytics to see crash detail.
I got stuck on step 3 (Build and run your app , We'll be listening for your app to communicate with our servers.).
I already try uninstall-reinstall , remove fabric or firebase crash report part but not working at all.
Here is firebase,fabric,crashlytics version I use.
classpath 'com.android.tools.build:gradle:3.3.1'
classpath 'com.google.gms:google-services:4.0.2'
classpath 'io.fabric.tools:gradle:1.26.1'
implementation 'com.google.firebase:firebase-core:16.0.7'
implementation('com.crashlytics.sdk.android:crashlytics:2.9.9#aar')
{
transitive = true;
}
Any solution?

Guys I have commented earlier here for solution but fortunately got its solution on my own.
Initialization of app is not mentioned anywhere to get crashlytics report on our console!
Step 1. First follow the official doc's link to include all dependencies as it is given there and setup your firebase app through firebase console.
Step 2. Now do the following initialization in your base application class or base activity class.
FirebaseApp.initializeApp(getApplicationContext());
FirebaseCrashlytics.getInstance().setCrashlyticsCollectionEnabled(true);
Now clean you project and do some force crash for few times, you should be able to see your crashlytics report on your firebase console
Refer this answer also OkHttp timeout issue

I had the same problem.I was working in an old project with the old Fabric Crashlytics and Google Analytics
So, this are the steps I did to see the screen in Firebase of "Installation successful!"
Delete everything related to Fabric from the project-level build.gradle
Delete everything related to Fabric from the app-level build.gradle
Search and delete all calls to Crashlytics within the project
Clean Project
Build Project
and finally, start again following the steps from this link
The first 4 steps were the most important in my case. They cleaned every trace of the Fabric library that I had previously installed.

Firebase Document also tells us to wait 5 minutes https://firebase.google.com/docs/crashlytics/test-implementation?platform=android
This is what is said in document :
To test the implementation, press the button in your app to force the
crash, then reopen your app so that Crashlytics can send the crash
report to Firebase. It may take up to five minutes for the report to
appear in the Firebase console.
I also followed #Shetanks answer https://stackoverflow.com/a/59906454/14784590
And its working after few crashes in two different devices.

Try updating your dependencies according to the Get Started page.
It should be something like:
implementation 'com.google.firebase:firebase-core:16.0.7'
implementation('com.crashlytics.sdk.android:crashlytics:2.9.9')
Remove the line:
transitive = true;

If you have multiple apps in the project then make sure that right app is selected for communication in the Firebase crashlytics console.
I searched everything on the web, at the end I realized that I have selected the wrong app in crashlytics console.

I have the same problem as well and tried out all the possible solutions. I just deleted the project from firebase console and recreate the project. It works for me.
Note: It is not a good approach If you have a lot of data in your firebase project. I would suggest using this approach If you are using firebase only for crashlytics.

my case i selected Crashlytic for android, not ios

How do you create a new fabric crashlytics Instant app?

Fabric app was creating with just fine with my other apps. Wait until I clicked on Instant app when I started my new project. Now I have two packages picked up by Fabric for the same project.
I installed crashlytics on one of the packages but still the app is not created in Fabric from Android studio.
Please help resolve, its been two days now i've build and run the app several times still no fabric App.

First, Add the plugin to your android studio using below steps:
File -> Settings -> Plugins -> Select Fabric for Android Studio -> Install it
Finally, after install plugin, you can see Fabric icon in top toolbar also in right panel with fabric word select and log in,
From the fabric, menu select your project operation which will see in the panel next option(Code setup for fabric).

Repeat 3 times for those important things:
Fabric support for Google Instant Apps is not currently enabled. Contact support#fabric.io if you're interested in trying it!
Fabric support for Google Instant Apps is not currently enabled. Contact support#fabric.io if you're interested in trying it!
Fabric support for Google Instant Apps is not currently enabled. Contact support#fabric.io if you're interested in trying it!
but if you dont belive that , you can follow this 5 steps to validate it.
choose the package without .feature
add dependencies to your project/build.gradle file
add apply plugin: 'io.fabric' to your base/build.gradle file
add dependencies compile('com.crashlytics.sdk.android:crashlytics:2.9.5#aar') {
transitive = true;
} to your base/build.gradle file
add <meta-data
android:name="io.fabric.ApiKey"
android:value="your apikey" />
to your base/AndroidManifest.xml
click your Sync now

How to completely disconnect an Android app from Firebase (in Android studio)

I want to completely disconnect my app from Firebase. This question has been asked several times (e.g here). Most of the answers focus on disconnecting an app from Firebase within the Firebase console and not within Android studio.
After disconnecting my app from the Firebase console. Everytime I try to reconnect the app to another Firebase project, an error balloon pops up stating that the app is already part of a Firebase project. I know this behaviour occurs because some files from the old Firebase project are still present. How do I get rid of them?

Try these steps to remove Fire-base from Android Studio project.
Delete google-services.json file from the Project (Find the file by Project view)
Remove dependencies from Project-level build.gradle (/build.gradle)
buildscript {
dependencies {
// Remove this line
classpath 'com.google.gms:google-services:4.2.0'
}
}
Remove all the Fire-base related dependencies from the project App-level build.gradle (//build.gradle) file
dependencies {
// Remove this line
implementation 'com.google.firebase:firebase-core:17.0.0'
}
Remove the line below from the bottom of the App-level build.gradle (//build.gradle) file
apply plugin: 'com.google.gms.google-services'
Restart Android Studio

Try this, On the project level, delete the google-services.json file
and then sync the project

You should undo all the steps that you are instructed to perform in the manual integration. So, remove all Firebase dependencies from build.gradle, remove the Google Services plugin from the bottom of build.gradle, and remove the google-services.json file.

Try shutting down the Firebase project created with the package name of the connected application; although it doesn't delete at the same time and is scheduled for later. Don't link your android app with any other firebase app till the previous connected app has been deleted completely.

Do the following (If you want to Switch Firebase Data Sources):
In Android Studio, Go to Tools>Firebase, Choose any of the options such as Real time-database
Click Connect to Firebase.
You will get a warning that the App is already connected to Firebase.
Click okay.
Android Studio will open a Firebase console on a browser.
Choose the Firebase App you want to you want to connect to.
Done.

On the main menu, select app ,select ,google-services.json' and then right click then delete

Failed to retrieve settings from https://settings.crashlytics.com/spi/v2/platforms/android/apps/

I am trying out the new Firebase/Crashlytics setup and seem to run into a weird issue.
I have one Android code base with multiple product flavors and each flavor is a separate individual app.
all of these apps are registered in Fabric (from the past)
all of these apps are added in Firebase
All linking between the two seems ok (from Fabric side as well as from Firebase side, it says that it is all linked up)
I removed the Fabric API key from the manifest file and added the appropriate plugins/dependencies etc. to both gradle files
I try to send a test crash report as per Firebase instructions.
I receive it perfectly fine on one of the product flavors, so I assume all works well.
However,
the rest of the product flavors do not send the crash report and I get this error in log:
E/Fabric: Failed to retrieve settings from https://settings.crashlytics.com/spi/v2/platforms/android/apps/package name/settings

Ok, I think I solved the problem, but the solution does not seem to be the way it should work (at least I do not think).
Go to Firebase Console > Project Settings > Account Linking > Fabric > Select the app and Unlink it
Confim in Fabric > App > Firebase - that it is unlinked
Go to Firebase > Project > Crashlytics (select the app you want) and you should now get a dialog to link your app again
Choose to link as a New Crashlytics (not existing one) and follow the directions
After that all should work fine
So basically, from Fabric>Firebase screen - there is no link visible and from Firebase>Account Linking>Fabric screen - there is also no linking visible. So no linking, but your crashes will be visible in Firebase.

This takes me a lot of time than I figured out how to migrate correctly. Actually you have two ways how to do it:
Perform clean migration without keeping crash history from Fabric Crashlytics
This way is described in Firebase Crashlytics developer guide. You have to here remove com.crashlytics.ApiKey meta-data from app manifest file.
With this way you must not link Fabric with Firebase otherwise crashes will not shown in Firebase nor Fabric console.
Link Fabric with Firebase and keep the crash history
This way is probably nowhere documented. Crucial is here to keep com.crashlytics.ApiKey meta-data in your manifest. Then you need to link Fabric Crashlytics with Firebase. You can also enable forwarding Events (formerly Answers) to Firebase Analytics. Both actions are presented in Fabric console, look for Firebase in a side menu.
All new crash reports show up in both Fabric console and Firebase console. Also this linking arrange a copying all Fabric crash report history to Firebase.
I think firebase-core artifact is not necessary here, but I added it. I'm also using Fabric Events, so with firebase-core additional app usage events was appeared in Firebase Analytics.

I had the same issue and it took me a lot of time to figure out.
I solved my problem by going to FireBase Console > [my project] > Crashlytics. In the dropdown you need to select your app. After that a wizard with three steps will show up.
Click whatever option suits you, I chose the first because it's a new app. After that the second step shows up.
Now here comes the important part. Make sure you click the link to go to the documentation! A new browser tab will open up. If you already finished the project setup like me, you can close it. After that you will automatically go to the 3rd option. Most of the time I never clicked the link because I had already completed the installation. And once I did I never noticed that the 3rd option was available because I'm at the other tab. As a result I never got to see the 3rd option.
At this point you should open your app and it will automatically connect to Firebase without any problem.
Edit: After I tried to add some other build variants I noticed that I was still getting some errors while retrieving the settings. It took me a lot of time to figure out how to solve it. The best thing I could come up with is:
switch to build variant
perform an assemble[YOUR_BUILD_VARIANT] on the gradle tab.
build > rebuild project
delete old app from device if present.
install app and open it.
Sometimes this also didn't work and I tried the same steps again one or two times and suddenly it started working...
It also helped me to enable additional debug logging for fabric and crashlytics.
adb shell setprop log.tag.Fabric DEBUG
adb shell setprop log.tag.CrashlyticsCore DEBUG

If there's network connectivity (like in Airplane mode), you will get this error even if everything is setup correctly.
You will also get:
E/Fabric﹕ Failed to retrieve settings from https://settings.crashlytics.com/spi/v2/platforms/android/apps/com.xyz/settings
W/Fabric﹕ Received null settings, skipping initialization!
To prevent Crashlytics from further crashing when logging, I do this:
boolean fabricInitialized = Fabric.isInitialized();
if (fabricInitialized) {
Crashlytics.log(someString);
}

Go to the settings of the project and add SHA-1 key for your android app.
After that redownload google-service.json to your sources.
This causes disappearing of this error
E/Fabric: Failed to retrieve settings from https://settings.crashlytics.com/spi/v2/platforms/android/apps/package name/settings
And after quite a huge delay you'll see crashes in Firebase Console.
By the way this doesn't help me with apps that were registered under one Google account, and after that moved to another account. Wiating for a response of Firebase team about this issue.

You probably forgot to add:
<meta-data
android:name="io.fabric.ApiKey"
android:value="h4132h4k324hjh4l4324h24hk21h4kj2h4" />
To your Manifest file. At least in my case, that was the reason.

In my case, the location of meta-data:io.fabric.ApiKey was wrong.
app/src/main/AndroidManifest.xml
before
<application
...>
<activity
...>
<meta-data
android:name="io.fabric.ApiKey"
android:value="xxxxxx" />
</activity>
</application>
after
<application
...>
<activity
...>
</activity>
<meta-data
android:name="io.fabric.ApiKey"
android:value="xxxxxx" />
</application>
I hope this will be of some help.

I'm finding out that I had to unregister and re-register my existing apps with Firebase after converting over to FirebaseCrashlytics.
Make sure you get your app to the following point before running it for it's initial FirebaseCrashlytics registration (console waits for initial registration), otherwise it won't register:
enter image description here
None of this is obvious!

Upgrade to the Firebase Crashlytics SDK Android & iOS
You can now set up Crashlytics in your app by using the new official Firebase Crashlytics SDK, which offers improved APIs that are more consistent with other Firebase products and more intuitive to use. This guide describes how to upgrade to the new SDK from the Fabric Crashlytics SDK. It describes the changes that come with the new APIs, the reason for the changes, and how to update your code, if required.
Android
Precondition: Migrate your app to AndroidX
1. Add a Firebase configuration file
Open your Project Settings.
Click Download google-services.json to obtain your Firebase Android config file.
Move your config file into the module (app-level) directory of your app.
2. Switch your dependencies
(project-level)/build.gradle
Deprecated From:
buildscript {
// ...
repositories {
// ...
// Remove Fabric's Maven repository.
maven { url 'https://maven.fabric.io/public' }
// Add Google's Maven repository (if it's not there already).
google()
}
dependencies {
// ..
// Add the Google Services Gradle plugin (if it's not there already).
classpath 'com.google.gms:google-services:4.3.3'
// Remove the Fabric Gradle plugin.
classpath 'io.fabric.tools:gradle:1.31.2'
}
}
To:
buildscript {
// ...
repositories {
// ...
// Add Google's Maven repository (if it's not there already).
google()
}
dependencies {
// ..
// Add the Google Services Gradle plugin (if it's not there already).
classpath 'com.google.gms:google-services:4.3.3'
// Add the Firebase Crashlytics Gradle plugin.
classpath 'com.google.firebase:firebase-crashlytics-gradle:2.1.0'
}
}
(app-level)/build.gradle
Finally, add the Firebase Crashlytics SDK. In your app-level build.gradle, replace the legacy Fabric Crashlytics SDK with the new Firebase Crashlytics SDK. For an optimal experience with Firebase Crashlytics, we recommend also adding the Firebase SDK for Google Analytics to your app (make sure to add Version 17.2.3 or later in order to get real time crash-free users and breadcrumbs).
Deprecated From:
apply plugin: 'com.android.application'
// Apply the Google Services plugin (if it's not there already).
apply plugin: 'com.google.gms.google-services'
// Remove the Fabric plugin.
apply plugin: 'io.fabric'
dependencies {
// Remove the Fabric Crashlytics SDK.
implementation 'com.crashlytics.sdk.android:crashlytics:2.10.1'
// Recommended: Add the Google Analytics SDK.
implementation 'com.google.firebase:firebase-analytics:17.4.1'
}
To:
apply plugin: 'com.android.application'
// Apply the Google Services plugin (if it's not there already).
apply plugin: 'com.google.gms.google-services'
// Add the Firebase Crashlytics plugin.
apply plugin: 'com.google.firebase.crashlytics'
dependencies {
// Add the Firebase Crashlytics SDK.
implementation 'com.google.firebase:firebase-crashlytics:17.0.0'
// Recommended: Add the Google Analytics SDK.
implementation 'com.google.firebase:firebase-analytics:17.4.1'
}
Update your code
Crashlytics.log is now an instance method
From Fabric: Crashlytics.log("my message");
To Firebase Crashlytics SDK:
FirebaseCrashlytics crashlytics = FirebaseCrashlytics.getInstance();
// To log a message to a crash report, use the following syntax:
crashlytics.log("E/TAG: my message");
The crash method is removed
From Fabric: Crashlytics.getInstance().crash().
To Firebase Crashlytics SDK:
throw RuntimeException("Test Crash")
Now, FirebaseCrashlytics starts up automatically using a
ContentProvider defined in the new Firebase Crashlytics SDK. Remove
calls to Fabric.with() if they exist. If you're already using Firebase
Crashlytics, your app may already be using automatic startup and may
not contain a call to Fabric.with().
GL

I came across this issue in the new Firebase SDK upgrade to 17.0.0+ version.
The issue was caused when we use multiple flavors. In case you are using a separate flavor - debug and have it linked to firebase as well, instead of adding the google-services.json file to the app root, we have to add the flavor specific json file to the appropriate folder for the flavor - app -> src -> (flavor folder).
This will ensure that the generated code has the correct client id for the flavor.
This is a silly mistake but there are chances for people to miss it.

At First you have to enable the Crashlytics in the Crashlytics tab in your project in the console (before or after adding all the dependencies of crashlytics) or follow these steps present in this
link:
https://firebase.google.com/docs/crashlytics/get-started?authuser=0&platform=android

After checking internet connection, I solved this issue by activate Crashlytics for my app in the Firebase console (then, relaunch app and all should work fine)

I posting this answer for those who want it to get it working without unlinking their app from Firebase Crashlytics.
To Achieve this they have to do following,
Add fabric API key back in AndroidManifest as metadata.
<meta-data
android:name="io.fabric.ApiKey"
android:value="fabric_api_key"
/>
Initialize Fabric.
Fabric.with(this, new Crashlytics());
After doing these two steps Crashlytics starts working again without unlinking your app.