Crash triage in production

Where crashes actually show up

Two places surface real-world crashes without asking users to do anything: Xcode Organizer's Crashes tab pulls crash reports Apple collects from devices (opted in to share analytics) and tries to auto-symbolicate them; MetricKit (module 19) delivers the same kind of data straight to your app via MXDiagnosticPayload, roughly once a day, from whatever devices PawWalk is actually installed on.

A raw crash report is nearly useless on its own — it's a list of memory addresses, not function names. Symbolication is the process of turning those addresses back into PawWalkKit/LiveTracker.swift:142 and the function that was running, using a dSYM (debug symbol file) that Xcode produces alongside every Release build. The dSYM has to be the exact one matching the build that crashed — mismatch the version and the addresses point at nothing useful. Xcode Organizer generally symbolicates automatically if it can find the matching dSYM; if not, you attach it by hand.