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 ?
Related
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
We have our app in Firebase and in Crashlytics.
Now we have to migrate Crashlytics (Fabric) to Firebase Crashlytics.
In my Firebase account I have around 40 Projects.
At the https://www.fabric.io/firebase_migration/apps Page.
I have in the section.
"FABRIC APPS WITH MATCHING FIREBASE APPS"
26 Android Apps
and in the section.
"ALL OTHER FABRIC APPS"
I have 3 more Android Apps
On the right side of the page I find 23 Firebase Projects but I have **40 Projects ** (some one are missing)
How to add the missing Firebase Project to fabric migration page ?
How to I link my Fabric Crashlytic App to my Firebase Project which is not at the migration page ?
How the Fabric Apps with Matching Firebase Apps work ?
Regards
The problem was :
Only project's where you are the owner are listed at the Fabric mirgration page
https://www.fabric.io/firebase_migration/
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.
I have implemented fabric crashlytics in my app now i try to add firebase push notification.
Now the issue is that I have two google-service.json in a project and at a time only single google-service is working. How to rectify that issue?