This page provides troubleshooting help and answers to frequently-asked questions about using Crashlytics, including getting crash reports and upgrading from the legacy Fabric SDK. If you can't find what you're looking for or need additional help, contact Firebase support.
Migrate from Fabric
If your app contains the legacy Fabric SDK after November 15, it will continue working normally but will no longer be able to report crashes.
To continue getting crashes reports, your app should be using the Firebase Crashlytics SDK minimum version 17.0.0 for Android, 4.0.0 for iOS, and 6.15.0 for Unity (note that v17.0.0-beta and v4.0.0-beta are not supported for Android and iOS, respectively). However, we recommend using these latest versions for access to all Crashlytics features and integrations:
17.3.0 for Android. Note that the latest version of Crashlytics is automatically specified when you import the Firebase BoM.
v7.1.0 for iOS.
6.16.0 for Unity.
See the Upgrade guide for instructions on how to replace the legacy Fabric SDK with the Firebase Crashlytics SDK. Refer to Release notes for information on current and previous SDK versions.
In order to continue getting crash reports in the Firebase console, you must upgrade to the Firebase Crashlytics SDK before November 15, 2020. The SDK allows you to integrate your crash data with Google Analytics so you can continue getting metrics you had in Fabric, such as crash-free users and breadcrumbs. See the Upgrade guide to find out how to update your app's code.
In Firebase, ensure that all apps within a project are platform variants of the same application from an end-user perspective. It's advisable to connect the Android and iOS versions of the same app or game to the same Firebase project. All the apps in a project generally share the same Firebase resources (database, storage buckets, etc.).
Visit Understand Firebase projects to learn more about best practices and considerations for adding apps to a Firebase project.
Your crash-free user graph in the Firebase console will remain but your data will drop to zero, as your app will no longer report crashes.
To view crash-free users metrics, you need Google Analytics in your app.
If you haven't yet, upgrade your app so that it uses the Firebase Crashlytics SDK.
As a part of Step 2 (Add the Crashlytics SDK), make sure to install v17.2.3+ for Android, 6.15.0 for Unity, or v6.3.1+ for iOS. These versions are required for enabling Google Analytics to view crash metrics. Refer to Release notes for more information about Crashlytics SDK versions.
Install and initialize the Google Analytics SDK in your app.
Check your Firebase Crashlytics dashboard for your metrics.
To view the Latest Release page, you need Google Analytics in your app.
If you haven't yet, upgrade your app so that it uses the Firebase Crashlytics SDK.
As a part of Step 2 (Add the Crashlytics SDK), make sure to install v17.2.3+ for Android, 6.15.0 for Unity, or v6.3.1+ for iOS. These versions are required for enabling Google Analytics to view crash metrics. Refer to Release notes for more information about Crashlytics SDK versions.
Install and initialize the Google Analytics SDK in your app.
Access the Latest Release page a couple different ways:
In your Firebase Crashlytics dashboard, 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.
After working to bring Fabric Beta into Firebase, we now offer you a new product called Firebase App Distribution. Learn how to use App Distribution to start distributing builds for your specific platform.
General FAQ
You can now report crashes for multiple apps in a single Firebase project, even when the apps are built for different Apple platforms (e.g., iOS, tvOS, and Mac Catalyst). Previously, you needed to separate the apps into individual Firebase projects if they contained the same bundle ID.