Crash Analytics

This walks you through the full crash management workflow: setting up Firebase Crashlytics, triaging which crashes to fix first using a priority scoring system (frequency times affected users times segment weight), reading stack traces, and understanding how crash rate directly impacts App Store ranking and editorial featuring. The target metrics are concrete: above 99.5% crash-free sessions and 99% crash-free users. What makes this useful is the triage framework that prevents you from wasting time on rare edge cases when you should be fixing the launch crashes hitting 1% of sessions. It also covers phased release strategies to catch regressions early and the specific crash rate thresholds that will tank your App Store visibility.

skills.sh installs: 1.7K
GitHub stars: 1.7K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add eronred/aso-skills --skill crash-analytics --agent claude-code

Installs into .claude/skills of the current project.

Files

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