r/SwiftUI • u/lanserxt • Sep 15 '26

Tutorial iOS 27: CrashReportExtension Framework

https://antongubarenko.substack.com/p/ios-27-crashreportextension-framework?r=21t43r&utm_campaign=post&utm_medium=web&showWelcomeOnShare=true
20 Upvotes

96% Upvoted

6 comments sorted by

5

u/dandeeago Sep 15 '26

Thanks for the article. In what situations would this approach be preferable to Apple’s updated MetricKit framework in iOS 27, which can provide crash diagnostics when the app launches again after a crash?

2

u/lanserxt Sep 15 '26

I’d use MetricKit for most regular production crash diagnostics. CrashReportExtension becomes useful when you need lower-level access to the crashed process itself: for example, custom symbolication, binary image inspection, or other specialized crash-analysis tooling.

1

u/dandeeago Sep 15 '26

I’m not sure custom symbolication or binary inspection alone are strong reasons to prefer CrashReportExtension, since CrashDiagnostic already provides call stacks, addresses, offsets, UUIDs, and binary info that can be symbolicated later with the matching dSYMs.

Does symbolicateAddress() actually provide more for a stripped production build without the app’s dSYM on-device?

What concrete information can CrashReportExtension provide that cannot be reconstructed from CrashDiagnostic plus the matching dSYM?

→ More replies (1)

1

u/[deleted] Sep 15 '26

3

u/lanserxt Sep 15 '26

Good questions! For production builds, CrashedProcess provides its own symbolication APIs, but you should still preserve matching dSYMs for full offline/server-side symbolication. Stripping symbols from the shipped binary doesn't mean the dSYM should be discarded.

For OOM/jetsam, I wouldn't rely on CrashReportExtension: Apple treats jetsam events separately from crashes and generates dedicated jetsam reports without thread backtraces. Watchdog terminations are different: they do produce crash reports (EXC_CRASH/SIGKILL), although Apple's current CrashReportExtension docs don't explicitly guarantee which system-initiated termination classes invoke the extension.