使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
Firebase Crashlytics
plat_ios
plat_android
plat_flutter
plat_unity
该崩溃报告解决方案适用于 Apple、Android、Flutter 和 Unity,功能强大,能针对应用问题提供清晰明了、富有实用价值的分析洞见。
Firebase Crashlytics 是一个轻量级的实时崩溃报告解决方案,可帮助您对影响应用质量的稳定性问题进行跟踪、确定优先解决顺序并加以修复。
Crashlytics 会对崩溃进行智能分组并突出显示导致这些崩溃的环境因素,从而为您节省问题排查的时间。
您可以查明某个特定的崩溃是否影响到了很多用户;当某个问题突然变得严重时收到提醒;找出哪些代码行导致了崩溃。
准备好开始了吗?选择您的平台:
iOS+
Android
Flutter
Unity
主要功能
经过整理的崩溃报告 |
Crashlytics 将众多的崩溃综合整理成了一个方便管理的问题列表,同时提供背景信息,突出显示崩溃的严重程度和影响范围,以便您能够更快地查明根本原因。
|
助您轻松解决常见崩溃 |
Crashlytics 具有崩溃数据分析功能,同时会提供实用的提示(会突出显示常见的稳定性问题,并提供相关资源,方便您对问题进行排查、分类和解决)。
|
与 Analytics 集成 |
Crashlytics 可以将您应用中的错误捕获为 Analytics 中的 app_exception 事件。利用这些事件,您可了解有哪些其他事件导致了每次崩溃,从而简化调试。此外,您还可以根据这些事件,针对遇到崩溃的用户生成 Analytics 报告,以开展受众群体分析。
|
实时提醒 |
对于可能需要立即加以关注的新问题、回归问题,以及日益严重的问题,您可以收到实时提醒。
|
实现流程
|
关联您的应用 |
首先在 Firebase 控制台中将 Firebase 添加到您的应用中。 |
|
集成 SDK
|
通过 CocoaPods、Gradle 或 Pub 添加 Crashlytics SDK,然后 Crashlytics 就会开始收集报告。
|
|
在 Firebase 控制台中查看报告 |
访问 Firebase 控制台,以便对应用中的问题进行跟踪、确定优先解决顺序并加以修复。 |
Crashlytics 如何分析崩溃以帮您简化调试?
为了提供应用的相关指标和报告,Crashlytics 会从您的应用收集并分析崩溃、非严重异常和其他事件类型。我们使用应用 build 的映射信息创建人类可读的崩溃报告,帮您了解事件(例如,对于 Apple 平台应用,我们使用调试符号 (dSYM) 文件)。
Crashlytics 收到事件后,它会使用分析引擎将相关事件划分为多种问题。分析引擎会考虑堆栈轨迹中的帧、异常消息、错误代码,以及其他平台或错误类型特征,以便将事件划分为多种问题。一个问题内的所有事件都具有共同的故障点。随着系统收到更多与某个问题匹配的事件,在 Crashlytics 信息中心内您的应用“问题”表格中,此问题的排名会向上移动。这种分组和排名有助于您更快地确定和解决影响最大的问题。
但即便在这样的一个事件组中,导致故障点的堆栈轨迹也可能有所不同。不同的堆栈轨迹可能代表着不同的根本原因。为了体现一个问题内部可能存在的此类差异,Crashlytics 会在问题内创建变体,变体是一个问题中的事件子组,该子组内的事件具有共同的故障点以及相似的堆栈轨迹。借助变体,您可以调试一个问题内最普遍的堆栈轨迹,并确定是否有不同的根本原因会导致这一故障。
后续步骤
开始使用 Firebase Crashlytics - 了解如何将 Firebase Crashlytics 添加到 Apple、Android、Flutter 或 Unity 项目中。
您可以通过添加自选式报告、日志、键以及非严重错误跟踪来自定义崩溃报告设置。
与 Google Play 集成,以便您可以直接在 Crashlytics 信息中心内按 Google Play 轨道过滤 Android 应用的崩溃报告。这样可让 Crashlytics 信息中心更有侧重地显示特定 build 的崩溃信息。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-08。
[null,null,["最后更新时间 (UTC):2025-08-08。"],[],[],null,["Firebase Crashlytics \nplat_ios plat_android plat_flutter plat_unity \nGet clear, actionable insight into app issues with this powerful crash reporting solution for Apple, Android, Flutter, and Unity. \n\nFirebase Crashlytics is a lightweight, realtime crash reporter that helps\nyou track, prioritize, and fix stability issues that erode your app quality.\nCrashlytics saves you troubleshooting time by intelligently grouping crashes\nand highlighting the circumstances that lead up to them.\n\nFind out if a particular crash is impacting a lot of users. Get alerts when an\nissue suddenly increases in severity. Figure out which lines of code are causing\ncrashes.\n\n\u003cbr /\u003e\n\nReady to get started? Choose your platform:\n\n[iOS+](/docs/crashlytics/get-started?platform=ios)\n[Android](/docs/crashlytics/get-started?platform=android)\n[Flutter](/docs/crashlytics/get-started?platform=flutter)\n[Unity](/docs/crashlytics/get-started?platform=unity)\n\nKey capabilities\n\n|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Curated crash reports | Crashlytics 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. |\n| Cures for the common crash | Crashlytics offers Crash Insights, helpful tips that highlight common stability problems and provide resources that make them easier to troubleshoot, triage, and resolve. |\n| Integrated with Analytics | Crashlytics can capture your app's errors as `app_exception` events in Analytics. 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 pull Analytics reports for users with crashes. |\n| Realtime alerts | Get realtime alerts for new issues, regressed issues, and growing issues that might require immediate attention. |\n\nImplementation path\n\n|---|----------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|\n| | Connect your app | Start by adding Firebase to your app in the [Firebase console](//console.firebase.google.com/). |\n| | Integrate the SDK | Add the Crashlytics SDK via CocoaPods, Gradle, or Pub, and Crashlytics starts collecting reports. |\n| | Check reports in the [Firebase console](https://console.firebase.google.com/project/_/crashlytics) | Visit the [Firebase console](https://console.firebase.google.com/project/_/crashlytics) to track, prioritize, and fix issues in your app. |\n\nHow does Crashlytics analyze your crashes for easier debugging?\n\nTo provide metrics and reports about your app, Crashlytics collects and\nanalyzes crashes, non-fatal exceptions, and other event types from your app. We\nuse the mapping information for your app's build to create human-readable crash\nreports to help you understand the events (for example, we use the\n[debug symbol (dSYM) files](https://developer.apple.com/documentation/xcode/building-your-app-to-include-debugging-information)\nfor Apple platform apps).\n\nWhen Crashlytics receives events, it uses an analysis engine to group\nrelated events into ***issues*** . The analysis engine looks at the frames in\nthe stack trace, exception message, error code, and other platform or\nerror type characteristics to group events into issues. In an issue, all events\nhave a common point of failure. As more incoming events match to an issue, the\nissue rises towards the top of your app's *Issues* table in the Crashlytics\ndashboard. This grouping and ranking helps you identify and fix the most\nimpactful problems faster.\n\nYet even within this group of events, the stack traces leading to the\npoint-of-failure might be different. And a different stack trace could mean a\ndifferent root cause. To represent this possible difference within an issue,\nCrashlytics creates ***variants*** within issues --- each variant is a\nsub-group of events in an issue that have the same failure point *and* a\nsimilar stack trace. With variants, you can debug the most common stack traces\nwithin an issue and determine if different root causes are leading to the\nfailure.\n\nNext steps\n\n- [Get started with Firebase Crashlytics](/docs/crashlytics/get-started)\n --- Learn how to add Firebase Crashlytics to an Apple, Android,\n Flutter, or Unity project.\n\n-\n [Customize your crash report setup](/docs/crashlytics/customize-crash-reports)\n by adding opt-in reporting, logs, keys, and tracking of non-fatal errors.\n\n-\n [Integrate with Google Play](/docs/crashlytics/integrate-with-google-play) so that\n you can filter your Android app's crash reports by Google Play track directly in the\n Crashlytics dashboard. This allows you to better focus your dashboard on specific builds."]]