crash-analytics
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseCrash Analytics
崩溃分析
You help triage, prioritize, and reduce app crashes — and understand how crash rate affects App Store discoverability and ratings.
你将帮助对应用崩溃进行分诊、确定优先级并降低崩溃率,同时了解崩溃率如何影响 App Store 可发现性和评分。
Why Crash Rate Is an ASO Signal
为什么崩溃率是 ASO 信号
- App Store ranking — Apple's algorithm penalizes apps with high crash rates
- App Store featuring — High crash rate disqualifies editorial consideration
- Ratings — Crashes are the #1 cause of 1-star reviews
- Retention — A crash in the first session destroys Day 1 retention
Target: crash-free sessions > 99.5% | crash-free users > 99%
- App Store 排名——Apple 的算法会降低高崩溃率应用的排名
- App Store 精选——高崩溃率会使应用失去编辑推荐评估资格
- 评分——崩溃是产生 1 星评价的首要原因
- 留存——首次会话中的崩溃会彻底破坏 Day 1 留存率
**目标:**无崩溃会话率 > 99.5% | 无崩溃用户率 > 99%
Tools
工具
| Tool | What it provides | Setup |
|---|---|---|
| Firebase Crashlytics | Real-time crashes, ANRs, symbolicated stack traces | Add |
| App Store Connect | Crash rate trend, crashes per session | Built-in, no code needed |
| Xcode Organizer | Aggregated crash logs from TestFlight + App Store | Xcode → Window → Organizer → Crashes |
| MetricKit | On-device diagnostics, hang rate, launch time | iOS 13+, automatic |
Recommended: Crashlytics (real-time alerts + search) + App Store Connect (trend validation)
| 工具 | 提供内容 | 设置 |
|---|---|---|
| Firebase Crashlytics | 实时崩溃、ANR、已符号化的堆栈跟踪 | 添加 |
| App Store Connect | 崩溃率趋势、每次会话的崩溃数 | 内置,无需编写代码 |
| Xcode Organizer | 汇总来自 TestFlight + App Store 的崩溃日志 | Xcode → Window → Organizer → Crashes |
| MetricKit | 设备端诊断、挂起率、启动时间 | iOS 13+,自动启用 |
**推荐方案:**Crashlytics(实时告警 + 搜索)+ App Store Connect(趋势验证)
Crashlytics Setup
Crashlytics 设置
iOS (Swift)
iOS(Swift)
swift
// AppDelegate or @main App struct
import FirebaseCore
import FirebaseCrashlytics
@main
struct MyApp: App {
init() {
FirebaseApp.configure()
// Crashlytics is auto-initialized
}
}swift
// AppDelegate or @main App struct
import FirebaseCore
import FirebaseCrashlytics
@main
struct MyApp: App {
init() {
FirebaseApp.configure()
// Crashlytics is auto-initialized
}
}Non-fatal errors (track without crashing)
非致命错误(跟踪但不触发崩溃)
swift
// Log a non-fatal error
Crashlytics.crashlytics().record(error: error)
// Log a custom key for debugging context
Crashlytics.crashlytics().setCustomValue(userId, forKey: "user_id")
Crashlytics.crashlytics().setCustomValue(screenName, forKey: "current_screen")swift
// Log a non-fatal error
Crashlytics.crashlytics().record(error: error)
// Log a custom key for debugging context
Crashlytics.crashlytics().setCustomValue(userId, forKey: "user_id")
Crashlytics.crashlytics().setCustomValue(screenName, forKey: "current_screen")Android (Kotlin)
Android(Kotlin)
kotlin
// build.gradle (app)
implementation("com.google.firebase:firebase-crashlytics:18.x.x")
// No additional code needed — auto-captures unhandled exceptions
// For non-fatal:
FirebaseCrashlytics.getInstance().recordException(throwable)kotlin
// build.gradle (app)
implementation("com.google.firebase:firebase-crashlytics:18.x.x")
// No additional code needed — auto-captures unhandled exceptions
// For non-fatal:
FirebaseCrashlytics.getInstance().recordException(throwable)Triage Framework
分诊框架
Not all crashes are equal. Prioritize by impact:
Priority Score = Crash Frequency × Affected Users × User Segment Weight
| Priority | Criteria | Response time |
|---|---|---|
| P0 — Critical | Crashes on launch / checkout / core feature; >1% of sessions | Fix today |
| P1 — High | Crashes in common flows; >0.1% of sessions | Fix this release |
| P2 — Medium | Edge case crashes; <0.1% of sessions | Fix next release |
| P3 — Low | Rare, non-blocking crashes; <0.01% of sessions | Backlog |
并非所有崩溃都同等严重。应按影响程度确定优先级:
优先级评分 = 崩溃频率 × 受影响用户数 × 用户群段权重
| 优先级 | 判定标准 | 响应时间 |
|---|---|---|
| P0——严重 | 启动、结账或核心功能期间崩溃;>1% 的会话 | 今日修复 |
| P1——高 | 常见流程中崩溃;>0.1% 的会话 | 在本次发布中修复 |
| P2——中 | 边缘场景崩溃;<0.1% 的会话 | 在下个版本中修复 |
| P3——低 | 少见、非阻塞性崩溃;<0.01% 的会话 | 纳入待办事项 |
Crashlytics Dashboard Triage
Crashlytics 仪表板分诊
- Sort by "Impact" (unique users affected), not frequency
- Group: ,
onboarding,checkout,core feature,backgroundlaunch - Assign P0/P1 to the top 3–5 issues
- Set a velocity alert in Crashlytics for any issue affecting >0.5% of users
- 按 "Impact"(受影响的唯一用户数)排序,而不是按发生频率排序
- 分组:、
onboarding、checkout、core feature、backgroundlaunch - 为排名前 3–5 的问题分配 P0/P1 优先级
- 在 Crashlytics 中为任何影响 >0.5% 用户的问题设置 velocity alert
Reading a Crash Report
阅读崩溃报告
Fatal Exception: com.example.NullPointerException
at com.example.UserProfileVC.loadData:87
at com.example.HomeVC.viewDidLoad:45
Keys:
user_id: 12345
current_screen: "home"
app_version: "2.3.1"
os_version: "iOS 17.3"Steps to debug:
- Open the file and line in Xcode ()
UserProfileVC.swift:87 - Check what can be nil at that point
- Reproduce with the user context (OS version, device, screen)
- Write a failing test before fixing
Fatal Exception: com.example.NullPointerException
at com.example.UserProfileVC.loadData:87
at com.example.HomeVC.viewDidLoad:45
Keys:
user_id: 12345
current_screen: "home"
app_version: "2.3.1"
os_version: "iOS 17.3"调试步骤:
- 在 Xcode 中打开对应文件及行号()
UserProfileVC.swift:87 - 检查该位置哪些值可能为 nil
- 使用用户上下文(OS version、device、screen)复现问题
- 修复前先编写一个失败的测试
Symbolication
符号化
Crashlytics auto-symbolicates if you upload dSYMs. If you see unsymbolicated traces:
bash
undefined如果上传 dSYMs,Crashlytics 会自动进行符号化。如果看到未符号化的堆栈跟踪:
bash
undefinedManually upload dSYMs
Manually upload dSYMs
./Pods/FirebaseCrashlytics/upload-symbols -gsp GoogleService-Info.plist -p ios MyApp.app.dSYM
For Bitcode-enabled builds, download dSYMs from App Store Connect → Activity → Build → dSYMs../Pods/FirebaseCrashlytics/upload-symbols -gsp GoogleService-Info.plist -p ios MyApp.app.dSYM
对于启用 Bitcode 的构建,请从 App Store Connect → Activity → Build → dSYMs 下载 dSYMs。App Store Connect Crash Data
App Store Connect 崩溃数据
- App Store Connect → App Analytics → Crashes — Crash rate trend per version
- Compare crash rate before and after each release
- A spike on a specific version = regression in that release
Crash rate formula: Crashes / Sessions × 100
- App Store Connect → App Analytics → Crashes——各版本的崩溃率趋势
- 比较每次发布前后的崩溃率
- 某个特定版本出现峰值 = 该版本出现了回归问题
**崩溃率公式:**崩溃数 / 会话数 × 100
Release Strategy to Minimize Blast Radius
将影响范围降至最低的发布策略
Use phased releases to catch crashes before full rollout:
iOS: App Store Connect → Version → Phased Release (7-day rollout: 1% → 2% → 5% → 10% → 20% → 50% → 100%)
Android: Play Console → Production → Managed publishing → Rollout percentage
Rule: Monitor Crashlytics for 24 hours at each phase. If crash rate increases >0.2%, pause rollout.
使用分阶段发布,在全面推出前发现崩溃:
**iOS:**App Store Connect → Version → Phased Release(7 天发布周期:1% → 2% → 5% → 10% → 20% → 50% → 100%)
**Android:**Play Console → Production → Managed publishing → Rollout percentage
**规则:**在每个阶段监控 Crashlytics 24 小时。如果崩溃率上升 >0.2%,暂停发布。
Responding to Crash-Driven 1-Star Reviews
应对由崩溃导致的 1 星评价
- Identify the app version where crash-related 1-stars appeared
- Fix the crash
- Reply to each crash-related review: "Fixed in version X.X — please update"
- After update ships, use to recover rating
rating-prompt-strategy
- 确定出现崩溃相关 1 星评价的应用版本
- 修复崩溃
- 回复每条与崩溃相关的评价:"已在版本 X.X 中修复——请更新"
- 更新版本发布后,使用 恢复评分
rating-prompt-strategy
Output Format
输出格式
Crash Audit Report
崩溃审计报告
Stability Report — [App Name] v[version] ([period])
Crash-free sessions: [X]% (target: >99.5%)
Crash-free users: [X]% (target: >99%)
Top crash issues:
P0 Issues (fix immediately):
#1 [Exception type] — [X] users, [X]% of sessions
File: [filename:line]
Cause: [hypothesis]
Fix: [specific action]
P1 Issues (this release):
#2 [Exception type] — [X] users, [X]% of sessions
...
Action Plan:
Today: Fix P0 issue #1 → release hotfix
This week: Fix P1 issues #2, #3 → include in v[X.X]
Monitoring: Set velocity alert at 0.5% session thresholdStability Report — [App Name] v[version] ([period])
Crash-free sessions: [X]% (target: >99.5%)
Crash-free users: [X]% (target: >99%)
Top crash issues:
P0 Issues (fix immediately):
#1 [Exception type] — [X] users, [X]% of sessions
File: [filename:line]
Cause: [hypothesis]
Fix: [specific action]
P1 Issues (this release):
#2 [Exception type] — [X] users, [X]% of sessions
...
Action Plan:
Today: Fix P0 issue #1 → release hotfix
This week: Fix P1 issues #2, #3 → include in v[X.X]
Monitoring: Set velocity alert at 0.5% session thresholdRelated Skills
相关 Skills
- — Full analytics stack; Crashlytics is one piece
app-analytics - — Recover rating after fixing crash-driven 1-stars
rating-prompt-strategy - — Respond to crash-related reviews
review-management - — Crashes on Day 1 destroy retention metrics
retention-optimization - — Crash rate > 2% disqualifies editorial featuring
app-store-featured
- ——完整的分析技术栈;Crashlytics 是其中的一部分
app-analytics - ——修复由崩溃导致的 1 星评价后恢复评分
rating-prompt-strategy - ——响应与崩溃相关的评价
review-management - ——Day 1 崩溃会破坏留存指标
retention-optimization - ——崩溃率 > 2% 会失去编辑精选资格
app-store-featured