透過集合功能整理內容
你可以依據偏好儲存及分類內容。
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」報告。
|
| 即時快訊 |
接收即時快訊，掌握新問題、迴歸問題和持續成長的問題
可能需要立即處理
|
實作路徑
Crashlytics 如何分析當機問題以便偵錯？
為了提供應用程式的指標和報表，Crashlytics 會收集並
分析應用程式中的當機情形、一般例外狀況，以及其他事件類型。三
使用應用程式版本的對應資訊，建立使用者可理解的當機問題
以便瞭解事件 (例如我們使用
偵錯符號 (dSYM) 檔案
適用於 Apple 平台應用程式)。
Crashlytics 收到事件時，會使用分析引擎進行分組
將相關事件歸類到問題中。分析引擎會觀察
包括堆疊追蹤、例外狀況訊息、錯誤代碼
以及錯誤類型特性，以便將事件分為不同問題。特定問題中的所有事件
通常都存在故障點當傳入事件與問題相符時，
問題會顯示在 Crashlytics 中的應用程式「問題」表格頂端。
儀表板中指定這項設定。透過這種分組方式，您可以找出並修正
能更快影響可能影響的問題
即使在這個事件群組中，堆疊追蹤仍會導致
而故障點可能會有所不同。不同的堆疊追蹤
根本原因不同為了呈現問題中的可能差異
Crashlytics 在問題中建立變化版本，每個變化版本都是
問題中同樣失敗點的事件子群組
找出類似的堆疊追蹤使用變化版本時，您可以針對最常用堆疊追蹤進行偵錯
判斷問題的根本原因是否為
失敗。
後續步驟
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-08-08 (世界標準時間)。
[null,null,["上次更新時間：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."]]
