crash-analytics
When the user wants to monitor, triage, or reduce their app's crash rate — including setting up Crashlytics, prioritizing which crashes to fix first, interpreting crash data, and understanding how crashes affect App Store ranking. Use when the user mentions "crash", "crashlytics", "crash rate", "ANR", "app not responding", "crash-free sessions", "crash-free users", "symbolication", "stability", "firebase crashes", "app crashing", or "crash report". For overall analytics setup, see app-analytics.
npx skills add Eronred/aso-skills --skill crash-analytics --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Crash Analytics You help triage, prioritize, and reduce app crashes — and understand how crash rate affects App Store discoverability and ratings. ## Why Crash Rate Is an ASO Signal - **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% ## Tools | Tool | What it provides | Setup | |------|-----------------|-------| | **Firebase Crashlytics** | Real-time crashes, ANRs, symbolicated stack traces | Add `FirebaseCrashlytics` pod/SPM package | | **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) ## Crashlytics Setup ### iOS (Swift) ```swift // AppDelegate
- Why Crash Rate Is an ASO Signal
- Tools
- Crashlytics Setup
- iOS (Swift)
- Non-fatal errors (track without crashing)
- Android (Kotlin)
- Triage Framework
- Crashlytics Dashboard Triage
- Reading a Crash Report
- Symbolication
- App Store Connect Crash Data
- Release Strategy to Minimize Blast Radius
- Responding to Crash-Driven 1-Star Reviews
- Output Format
Manually upload dSYMs
What does the crash-analytics skill do?
When the user wants to monitor, triage, or reduce their app's crash rate — including setting up Crashlytics, prioritizing which crashes to fix first, interpreting crash data, and understanding how crashes affect App Store ranking. Use when the user mentions "crash", "crashlytics", "crash rate", "ANR", "app not responding", "crash-free sessions", "crash-free users", "symbolication", "stability", "firebase crashes", "app crashing", or "crash report". For overall analytics setup, see app-analytics.
How do I install it?
Run `npx skills add Eronred/aso-skills --skill crash-analytics --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Eronred/aso-skills, a repository with 1,708 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.