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.
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.
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).
dSYMs are missing/not uploading
To upload your project's dSYMs and get verbose output, check the following:
Make sure your project's build phase contains the Crashlytics run script, which allows Xcode to upload your project's dSYMs upon crashing (read Initializing Crashlytics for instructions on adding the script). After updating your project, force a crash to see if the script is working.
If you see a "Missing dSYM" alert in the Firebase console, check Xcode to make sure it's properly producing dSYMs for the build. Otherwise, it's likely the run script tool is getting stuck while uploading the dSYMs. In this case:
Make sure you're using the latest version of Crashlytics.
Enable Crashlytics debug logging by running the following command in Xcode:
Try uploading the dSYMs one at a time, using the specific UUIDs.
Iconfiles in the zip archive by running:
cd appDsyms rm -rf $(find . | grep Icon)
# Enumerate all the dSYMs
upload-symbols ... $(ls)
If the upload is still unsuccessful, contact Firebase Support and be sure to include your logs.
App also uses the
Google Mobile Ads SDK but not getting crashes
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
Where is my BigQuery dataset located?
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.
Can I use Crashlytics for macOS or tvOS?
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.
Can I use Crashlytics in a Firebase
project with multiple apps on different Apple platforms?
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.