I have migrated Fabric Crashlytics to Firebase Crashlytics in my android project. While using fabric, in activity class I have used below line,
Fabric.with(this, new Crashlytics());
But after migration, what is the exact replacement of this in Firebase Crashlytics.
Thanks in Advance..
You have to follow the Firebase tutorial when activating the Crashlytics. You don't need any code to initialize Crashlytics, it's automatic.
The only thing you need, following the tutorial, is to make an intentional crash, api will detect it and your crashlytics will be connected.
Please, follow the next documentation: https://firebase.google.com/docs/crashlytics/get-started?hl=es&platform=android
Related
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
I recently tried to migrate Fabric crashlytics to Firebase by following steps on https://fabric.io/firebase_migration
Fabric migration dashboard shows the app is linked to Firebase already but when checking our Firebase dashboard neither there is Fabric linking data nor Crashes are being shown on Firebase crashlytics.
I also followed https://fabric.io/remove_firebase_crashlytics?clientId=CLIENT_ID&projectId=PROJECT_ID for explicitly unlinking fabric app so that we can link it through new fabric migration guide but it was throwing error as "This app was not linked".
Any solution for properly linking fabric app to firebase with all the fabric crash data keeping intact ?
I got an android app where Fabric Crashytics is installed. I've followed the official guide to setup Firebase Crashlytics and linked the Fabric and Firebase accounts (AFAIK Firebase acquired Fabric recently).
So in particular I removed the Fabric API key with <meta-data/> tag in manifest.xml.
Then I tried to make a test crash but it didn't appear neither in Firebase not Fabric dashboard, however I got a success log in logcat: Crashlytics report upload complete: <ID>.
When I sniffed the network, it appeared that I'm getting 403 Unathorized from Crashlytics. However when I add the Fabric API key in <meta-data/> tag it works and I see the crash report.
Help me please what is wrong with my configuration, why do I need to use old Fabric API key if I'm using new Firebase Crashlytics and docs don't state that.
For those on iOS that used Fabric, so this is what I finally got from support. I wanted to start fresh.
Visit https://firebase.google.com/docs/crashlytics/get-started?authuser=1#ios.
Revise pods in Podfile accordingly (specify versions of Fabric and Crashlytics as instructed)
Update the build phase run script: "${PODS_ROOT}/Fabric/run" instead of the current one that points to their Fabric API key
Remove API key from Info.plist - In your AppDelegate.swift, remove import Fabric and import Crashlytics and any Fabric.with statement, keep import Firebase and use FirebaseApp.configure() instead
Go to project settings in Firebase console, click the Integrations tab, unlink the appropriate Fabric app from Firebase (if you don't do this, you will get an error looking like: "[Fabric] failed to download settings Error Domain=FABNetworkError Code=-5")
Go to the Crashlytics tab and you should see that you have to onboard Firebase Crashlytics again.
Go through those steps choosing "This app doesn't have Crashlytics installed" and when you get to the final step, build and run the app and wait a few seconds. Then you Crashlytics tab will be setup.
Once I did this, and force crashed, it FINALLY showed up.
Below things are mandatory, if you Migrate from existing Fabric crashlytic application to Firebase crashlytic
<meta-data
android:name="io.fabric.ApiKey"
android:value="xxxxxxxxxxxxxxxxxxxxxxxxxx"
/>
Fabric.with(new Crashlytics()));
But not sure what will happen to these API and KEY, once fabric is down Say mid 2019.
The Firebase Crash Reporting will be superseded by Fabric Crashlytics and not the other way around ...currently there still seems to be some dependency to firebase-crash, which might get removed in future versions.
https://firebase.google.com/docs/crashlytics/upgrade-from-crash-reporting
^ despite it reads "Firebase Crashlytics" there, it might still be "Fabric Crashlytics".
I am working on a project that contains multiple Java modules. Implementing new Firebase Crashlytics went fine with main Application module, and I get crash reports in Firebase console, but I can't get it to work with these other library modules. The only thing similar to the problem I have is in this Fabric docs link, but even dough Google bought them, it doesn't work with Firebase version of Crashlytics.
Like all other Firebase SDKs, Firebase Crashlytics depends on a Firebase configuration that can only be applied to your application module. You can't apply Firebase configuration to a library module. You can put the Crashlytics dependency in a library module, but you still need to configure the app module so the SDK knows where to report the errors it captures. This involves google-services.json and applying the fabric.io plugin, as described in the documentation.
My Android project is currently using Firebase Crashlytics.
I would like to use Fabric Crashlytics.
I have tried following steps from here, but it is not reporting any crash.
I have also removed this line from app gradle:
implementation "com.google.firebase:firebase-crash:x.y.z"
Any solution to this would be much appreciated. Thank you.
In case you want to know the reason behind this migration decision, please refer to this SO question.
Fabric services will cease to exist after March 2020.
It would not help to migrate. If you are missing feature parity, you may want to contact Firebase Support.