apple-crash-symbolication

What problem does it solve?

This Skill resolves raw native backtrace addresses from Apple .ips crash logs into .NET runtime function names with source file and line numbers, so you can quickly understand what failed in a .NET MAUI or Mono app.

Core Features & Use Cases

• .ips crash parsing and validation: Confirms the input is iOS 15+/macOS 12+ .ips JSON (and stops early on unsupported formats like Android tombstones or legacy .crash text).
• .NET runtime frame identification: Detects CoreCLR/Mono-related libraries (e.g., libcoreclr, libmonosgen-2.0, and relevant libSystem.Native components) from usedImages and computes absolute frame addresses.
• UUID-matched dSYM symbolication (with automation): Locates matching dSYM artifacts (local builds, SDK packs, NuGet caches) and downloads missing symbols from the Microsoft symbol server, then runs atos to produce symbolicated backtraces.
• Optional trace narrowing: Can focus symbolication on the crashing thread only and provides a ParseOnly mode when atos or symbols are unavailable.
• Practical scenarios: Use it for triaging EXC_CRASH/EXC_BAD_ACCESS/SIGABRT/SIGSEGV originating in the .NET runtime, especially when you have an .ips file from a connected iOS device or want to confirm whether managed exception paths reached the runtime.

Quick Start

Use the skill to symbolicate the file MyApp-2026-02-25.ips by running the Symbolicate-Crash.ps1 script from this skill directory.