I've an IOS app which is using Fabric Crashlytics. As you know:
The Fabric iOS and Android mobile apps will be sunset on November 30, 2018.
So I'm trying to migrate all existing data from Fabric's Crashlytics to Firebase. But I've seen this topic Migrate Fabric's Crashlystic data to Firebase, and Mike from Fabric recommended that we should not yet migrate now.
Here is the question:
At this moment, I'm linking Fabric with Firebase, and the data shows up in both place. What happens if one day Fabric shut down its Crashlytics service, will my crash report continues to show up on Firebase with current configuration?
Could someone give me a solution/answer for this case?
Thanks.
Mike from Firebase & Fabric here. I updated my other answer. That notice is only for the Fabric mobile apps available on the Play and App Stores. It does not affect the Fabric dashboard, Beta, or any other products. Your Crashlytics data in Fabric will continue to be processed until mid-2019 when Fabric is retired.
Once you link between Fabric and Firebase, data will flow into both dashboards. In early 2019, we plan on releasing a new SDK that is streamlined. Once you update to that future SDK, it will have the Fabric parts of the SDK removed which will make it smaller, but will then only send data to Firebase.
Related
I have used Fabric before 2 years.Now I need to migrate to firebase. Here what is the good way to proceed? Shall I remove all fabric related integrations and add firebase as new integration.
Or
Shall I need to add the firebase with the existing fabric account?
Any best practices?
Firebaser here -
If you missed the migration window to move from Fabric to Firebase, the best way forward is to set up a new Firebase project, add your desired apps to your Firebase project, and then follow the Crashlytics onboarding instructions to get Firebase Crashlytics working. The Firebase Crashlytics SDK is now the main supported Crashlytics SDK, and the old Fabric SDK will no longer report crashes past November 15th, as Misha noted.
Once you've been able to verify that a test crash has come through to your dashboard, you should be all set to include it in a live version that goes out to your users.
In Fabric you easily migrate your existing projects to Firebase account. Migration is just a click of a button in Fabrics web page.
Next thing is integration of SDK into project.
You can leave old Fabric SDK for now. It will continue reporting your app's crashes until November 15, 2020.
But after November 15 you will need to remove Fabrics sdk and install Firebase.
I have an app on Google Play Store using Fabric Crashlytics and
Fabric SDK is not currently accepted and will continue to report your application problem until November 15, 2020. On this date, the Fabric SDK and old versions of the Firebase Crashlytics SDK will stop sending crashes for your app.(https://firebase.google.com/docs/crashlytics/get-started)
I do not want to upgrade to Firebase because I do not use this function and keep current app version available on Google Play Store.
If so, does my application have a problem when Fabric shuts down all services, does it crash due to a failure to connect to the Fabric server?
After November 15th, any apps still using the Fabric SDK will stop reporting crashes/non fatals. Any apps still using the Fabric SDK will continue to work, the Fabric SDK will just fail silently in the background, and not report any crash data.
I have an app that was using fabric crashlytics. New version of this app will be using firebase service for crash logging, but I would like to have some visibility of current users (that are still on fabric sdk).
According to https://firebase.google.com/docs/crashlytics/get-started?platform=android :
The Fabric SDK is now deprecated and will continue reporting your app's crashes until November 15, 2020.
Where can I find these reports? I can't sign in to fabric dashboard anymore and they are not showing in firebase console.
firebaser here
Since the Fabric dashboard has been shut down, the crash reports from apps using the legacy SDKs are only visible in the Firebase console.
If you are having a hard time getting this to work, reach out to Firebase support for personalized help in troubleshooting.
This is my problem: I have an android app that links to Fabric Crashlytics. I have followed steps to migrate to Firebase, but I cannot find the migrated App in my current google account, and I am not sure I have migrated to my current google account. I want to do it again, but the status is marked as "migrated".
My question is:
1) is there any ways I can reset the project status, so that I can re-migrate from Fabric Crashlytics
to Google Firebase Project?
2) if not, is there any ways I can locate where is my migrated Google Firebase Project? I have used "View app in Firebase Crashlytics", but it ask me to request access.
You can unlink your app from Firebase by navigating to Project Settings>Integrations>Fabric. Afterwards, you can go through the migration process once more.
I have an app that logs crashes and non-fatals to Fabric Crashlytics and uses Firebase Analytics to log analytics events.
I want to migrate from Fabric Crashlytics to Firebase Crashlytics. In addition I want to save historical data from Fabric during the migration.
When I try to do it with provided mechanism of Firebase Migration (https://fabric.io/firebase_migration/apps) I cannot do it in a way I want to. In particular, I cannot provide existent Firebase project ID for migration. I see error:
So how can I do migrate properly?
I found some statements from Fabric team members (https://stackoverflow.com/a/49734863/4312184) that migration process is not ready for saving historical data. But maybe it is ready now?
What happened when you migrated?
For the apps that you linked, your Crashlytics data now appears in the Firebase Crashlytics dashboard (https://console.firebase.google.com/project/_/crashlytics) (in the Firebase console). The linking process does not involve any changes to the Crashlytics SDK or your Fabric API key.
Note that in the coming months, we'll release Firebase-specific Crashlytics SDKs for iOS and for Android, as well as offer further upgrade instructions. So for now, if you migrated an iOS and Android app:
Do not change how you use the Crashlytics SDK because the iOS and Android SDKs haven't changed.
Do not change or remove your Fabric API key.
Note: For migrating Unity apps to Firebase, follow the Unity migration instructions and review the Unity API changes.
Discover Firebase Crashlytics
Find all your Crashlytics data in the Firebase Crashlytics dashboard (https://console.firebase.google.com/project/_/crashlytics) (in the Firebase console).
Important: To view crash-free users metrics, you need Google Analytics in your app.
Firebase Crashlytics offers several new features:
Customize your velocity alerts.
Use Google Analytics breadcrumbs (requires Google Analytics).
Export your Crashlytics data to BigQuery, then analyze it using BigQuery and the Crashlytics Data Studio template.
New integrations (https://console.firebase.google.com/project/_/settings/integrations), including a Jira integration that enables you to link Crashlytics issues with Jira issues from the Firebase console.
Start using Google Analytics
Google Analytics is Firebase's analytics engine and gives you access to powerful insights into your data.
Install the Google Analytics SDK
Visit the Google Analytics documentation to learn how to install and initialize the SDK in your iOS, Android, or Unity app.
Note: After you initialize the Google Analytics SDK in your app, there can be a delay of a few hours before data appears in the Firebase Crashlytics dashboard.
How Google Analytics helps Crashlytics
Google Analytics unlocks valuable capabilities and features that you were already using in Fabric:
Monitor your Latest Release status.
Use Google Analytics events like you used Fabric's Answers.
Track your app's crash-free users metrics in the Firebase Crashlytics dashboard (https://console.firebase.google.com/project/_/crashlytics).
Set custom alerts for your app's stability with velocity alerts.
Note: Firebase can only use analytics data collected by Google Analytics. So, for your migrated apps, your historical analytics data (from Fabric Answers) cannot migrate to Firebase. This means that, unlike your crash data, your analytics data will start from a blank slate and the Firebase console will only show data collected after installing and initializing the Google Analytics SDK.
Monitor your Latest Release
With Google Analytics initialized in your app, you can monitor the stability and metrics of your current builds in the Latest Release page (https://console.firebase.google.com/project/_/analytics/latestrelease) in the Firebase console.
Access the Latest Release page a couple different ways:
In your Firebase Crashlytics dashboard (https://console.firebase.google.com/project/_/crashlytics), click the link in the Event trends card.
In the Firebase console, go to the Analytics section in the left navigation pane, then click Latest Release.
Use Events rather than Answers
Google Analytics lets you set custom and predefined events, similar to Fabric's Answers.
To learn how to set up events using Firebase, visit the Google Analytics documentation for your platform (iOS, Android, or Unity).
To learn how to convert your existing Answers events to Google Analytics events, visit the Fabric Analytics page.
Important: After you instrument Google Analytics events, we recommend removing Answers events from your app's code.
Configure your notification settings
Now that you've migrated to Firebase, you will start getting emails from both Firebase and Fabric.
You can configure your notifications settings:
For Firebase — Configure your Firebase notifications and integrations in the Firebase console:
For notifications, manage your Firebase alert subscriptions for Crashlytics via Alerts -> Alert Settings (click the bell icon in the top-right corner of the Firebase console).
For integrations, visit Project settings -> Integrations (https://console.firebase.google.com/project/_/settings/integrations) to set up notifications for Jira, Slack, and PagerDuty.
For Fabric — Configure your Fabric notifications in Fabric's settings page (https://fabric.io/settings/notifications):
Note: Firebase Crashlytics will use Fabric per get.fabric.io/roadmap only until March 31, 2020. Migrate your apps to Firebase to take advantage of the latest products and features there.
Modify the settings for your Fabric notifications so that you're not receiving duplicate emails from both Firebase and Fabric.
Invite your team members
Now that you've migrated to Firebase, invite your team so that they can start using Firebase and access your migrated app in the Firebase console.
From the Firebase console — Visit Project settings -> Users & permissions (https://console.firebase.google.com/project/_/settings/iam) to add teammates as members of your Firebase project.
From the Fabric site — Visit the invite page (https://fabric.io/firebase_migration/invite) in the Fabric migration dashboard to invite your teammates to your migrated apps. With just one click, you can add all teammates associated with your app to your Firebase project.
Note: Using the one-click invite button on Fabric's migration dashboard assigns the Editor role to all invited members.
Source: Migration steps after linking from Fabric