What it does
Firebase Crashlytics is an app stability and crash-reporting service for Android, Apple, Flutter, and Unity applications. Its SDK sends crash and non-fatal event reports to the Firebase console, where similar events are grouped into issues and release stability can be monitored. Developers can attach logs, keys, custom events, and Google Analytics breadcrumbs to give an issue more context. The reports and alerts help a team identify and investigate a regression, but the team must still reproduce the cause and update its app.
Follow a release regression
Imagine that a new mobile release starts producing more crashes or Android application-not-responding errors. Crashlytics groups related reports into issues and supports prioritization by impact, so a team can focus on the problem affecting the most users rather than treating every event as a separate ticket. Release monitoring and alerts can signal a new, regressed, or increasing error. Logs, custom keys, and breadcrumbs add context about what happened before an event; enabling Google Analytics in the Firebase project is recommended for automatic breadcrumb logs. These signals help narrow diagnosis, but they are not a code fix or proof that the cause has been corrected.
Setup requires an app change
For Android, the documented route starts with a Firebase project and app registration, then adds the Firebase configuration file, Crashlytics SDK, and Gradle plugin to the application. The guide asks developers to generate a test crash and restart the app to send the first report, then check the Crashlytics dashboard. It also documents support paths for Apple platforms, Flutter, Unity, and Android NDK applications. Crashlytics cannot report app failures until the relevant SDK is built into the app and deployed. The product page and Firebase pricing table list Crashlytics as no-cost; that does not remove the need to configure Firebase or instrument each app.
Strengths
- Similar crashes are grouped into issues and can be prioritized using their impact on real users.
- The product reports crashes, non-fatal events, and Android ANRs, with release monitoring and alert options.
- Logs, custom keys, and optional Google Analytics breadcrumbs add event context for debugging.
Watch out for
- Each application needs Firebase configuration and the Crashlytics SDK before it can report events.
- Automatic breadcrumb logs require Google Analytics to be enabled in the Firebase project.
Best for
- Finding and prioritizing crashes or ANRs in a shipped Android or Apple mobile app
- Comparing app stability across releases and investigating reports with event context
Sources
- Firebase Crashlytics | Track, prioritize, and fix app crashes faster (Oct 25, 2026)
- Get started with Crashlytics for Android | Firebase Crashlytics (Oct 25, 2026)
- Firebase Pricing (Oct 25, 2026)