Firebase Crashlytics

Get clear, actionable insight into app issues with this powerful crash reporting solution for Apple, Android, Flutter, and Unity.

Firebase Crashlytics is a lightweight, realtime crash reporter that helpsyou track, prioritize, and fix stability issues that erode your app quality.Crashlytics saves you troubleshooting time by intelligently grouping crashesand highlighting the circumstances that lead up to them.

Find out if a particular crash is impacting a lot of users. Get alerts when anissue suddenly increases in severity. Figure out which lines of code are causingcrashes.



Ready to get started? Choose your platform:

iOS+AndroidAndroid NDKFlutterUnity

Key capabilities

Curated crash reportsCrashlytics synthesizes an avalanche of crashes into a manageable list of issues, provides contextual information, and highlights the severity and prevalence of crashes so you can pinpoint the root cause faster.
Cures for the common crashCrashlytics offers Crash Insights, helpful tips that highlight common stability problems and provide resources that make them easier to troubleshoot, triage, and resolve.
Integrated withGoogle AnalyticsCrashlytics can capture your app's errors asapp_exception events inAnalytics. The events simplify debugging by giving you access a list of other events leading up to each crash, and provide audience insights by letting you pullAnalytics reports for users with crashes.
Realtime and custom alerts Get realtime alerts for new issues, regressed issues, and growing issues that might require immediate attention. You can alsoset up custom alerts to custom notification channels.

Implementation path

Connect your app Start by adding Firebase to your app using theFirebase console.
Integrate the SDK Add theCrashlytics SDK using Swift Package Manager, Gradle, or Pub.Crashlytics automatically starts collecting reports.
Check reports in theFirebase console Visit theFirebase console to track, prioritize, and fix issues in your app.
Export your data for advanced analysis and featuresExport your data toBigQuery orCloud Logging to query your data, build custom dashboards, and set up custom alerts.

How doesCrashlytics analyze your crashes for easier debugging?

To provide metrics and reports about your app,Crashlytics collects andanalyzes crashes, non-fatal exceptions, and other event types from your app. Weuse the mapping information for your app's build to create human-readable crashreports to help you understand the events (for example, we use thedebug symbol (dSYM) files for Apple platform apps).

WhenCrashlytics receives events, it uses an analysis engine to grouprelated events intoissues. The analysis engine looks at the frames inthe stack trace, exception message, error code, and other platform orerror type characteristics to group events into issues. In an issue, all eventshave a common point of failure. As more incoming events match to an issue, theissue rises towards the top of your app'sIssues table in theCrashlyticsdashboard. This grouping and ranking helps you identify and fix the mostimpactful problems faster.

Yet even within this group of events, the stack traces leading to thepoint-of-failure might be different. And a different stack trace could mean adifferent root cause. To represent this possible difference within an issue,Crashlytics createsvariants within issues — each variant is asub-group of events in an issue that have the same failure pointand asimilar stack trace. With variants, you can debug the most common stack traceswithin an issue and determine if different root causes are leading to thefailure.

Next steps

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-18 UTC.