Triage app crashes by business impact
crash-analyticsskillsetup L2★1,242
Eronred/aso-skills ↗What it does
Triage and prioritize app crashes by impact to reduce crash-free session rate
Best for
Mobile teams seeing >0.5% crash rate affecting App Store ranking and retention who need impact-based triage not frequency ranking.
Inputs
- · Firebase Crashlytics or App Store Connect crash data
- · crash stack trace with symbols
Outputs
- · priority score (P0–P3)
- · triage dashboard (grouped by onboarding/checkout/core feature/background)
- · reproduction steps + user context
Requires
- · Firebase Crashlytics
- · App Store Connect
- · Xcode Organizer
- · MetricKit (iOS 13+, optional)
Preconditions
- · Crashlytics integrated
- · dSYMs uploaded to Apple or Crashlytics
Failure modes
- · optimizes for crash frequency not user impact
- · unsymbolicated traces make debugging hard
- · ignores crash impact on App Store ranking
- · misses ANR (app not responding) crashes
- · doesn't prioritize by user segment (VIP user crash = higher P)
Trust signals
- · P0–P3 priority formula (crash frequency × affected users × user segment weight)
- · crash-free session benchmark (>99.5% target)
- · explanation of App Store ranking penalty for crashes
- · dSYM upload instructions (Bitcode handling)
- · ANR + crash distinction
- · Crashlytics dashboard navigation