This page provides troubleshooting help and answers to frequently-asked questions about using Crashlytics. If you can't find what you're looking for or need additional help, contact Firebase support.
General troubleshooting/FAQ
If you're not seeing crash-free users, breadcrumb logs, and/or velocity alerts, we recommend checking your app's configuration for Google Analytics.
Make sure that you've enabled Google Analytics in your Firebase project.
Make sure that Data sharing is enabled for Google Analytics in the Integrations > Google Analytics page of the Firebase console. Note that Data sharing settings are displayed in the Firebase console but managed in the Google Analytics console.
In addition to the Firebase Crashlytics SDK, make sure that you've added the Firebase SDK for Google Analytics to your app (iOS | Android).
Make sure that you're using the latest versions for all your Firebase SDKs (iOS | Android).
Especially check that you're using at minimum the following versions of the Firebase SDK for Google Analytics:iOS — v6.3.1 or later |Android — v17.2.3 or later (BoM v24.7.1 or later) .
The crash-free users percentage is an aggregation over time, not an average.
The crash-free value represents the percentage of users who engaged with your app but didn't have a crash over a specific time period. You select this time period from the dropdown menu in the upper-right of the Crashlytics dashboard.
For example, imagine your app has three users; we’ll call them User A, User B, and User C. The following table shows which users engage with your app each day and which of those users had a crash that day:
| Monday | Tuesday | Wednesday | |
|---|---|---|---|
| Users who engaged with your app | A, B, C | A, B, C | A, B |
| User that had a crash | C | B | A |
On Wednesday, your crash-free users percentage is 50% (1 out of 2 users was crash-free).
Two of your users engaged with your app on Wednesday, but only one of them (User B) had no crashes.For the past 2 days, your crash-free users percentage is 33.3% (1 out of 3 users was crash-free).
Three of your users engaged with your app over the past two days, but only one of them (User C) had no crashes.For the past 3 days, your crash-free users percentage is 0% (0 out of 3 users were crash-free).
Three of your users engaged with your app over the past three days, but zero of them had no crashes.
Integrations
If your project uses Crashlytics alongside the Google Mobile Ads SDK,
it's likely that the crash reporters are interfering when
registering exception handlers. To fix the issue, turn off crash reporting in
the Mobile Ads SDK by calling disableSDKCrashReporting.
After you link Crashlytics to BigQuery, new datasets you create are automatically located in the United States, regardless of the location of your Firebase project.
Platform support
You can implement Crashlytics in macOS or tvOS projects but the projects will not have access to metrics collected by Google Analytics (crash-free users, latest release, velocity alerts, and breadcrumbs), which will be excluded from your crash data.
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.