Triage Crashes & Production Errors

Background: Native [iOS / Android / both] app live in production with
[Crashlytics / Sentry / other] (set up in Section 4.5). I'm seeing:
[paste a crash report / stack trace / describe the crash trend].

Use case: Help me triage and fix production crashes systematically rather
than reacting to whichever one is loudest.

Implementation details:
- Prioritize by impact: crash-free-users rate, number of users affected,
  and whether it's growing or tied to a recent release
- Read the (symbolicated) stack trace: confirm dSYMs / mapping files are
  uploaded so traces are readable
- Reproduce from the breadcrumbs/logs leading to the crash; identify
  device/OS/version patterns
- Distinguish a code bug from an OS-version- or device-specific issue
- Decide hotfix-now (kill switch / expedited release) vs next-release

Deliverable: A triage of this crash (impact, likely cause from the
trace), the reproduction approach, the fix, and a recommendation on
hotfix-vs-wait with the reasoning.