What problem does it solve? Native backtraces in Apple platform crash logs from .NET MAUI or Mono apps show raw addresses for libcoreclr and libmonosgen frames, making it impossible to identify which .NET runtime function crashed without manual UUID matching and symbol lookup. ## Core Features & Use Cases - Automated .ips Parsing: Parses the two-part JSON .ips format, extracts Mach-O UUIDs, load addresses, and frame offsets from usedImages and thread backtraces. - dSYM Discovery and Download: Locates UUID-matched dSYMs from build output, SDK packs, and NuGet cache, and automatically downloads .dwarf symbols from the Microsoft symbol server. - Batch Symbolication with atos: Resolves frame addresses to function names, source files, and line numbers, stripping CI path prefixes to map to dotnet runtime sources. - Use Case: A .NET MAUI app crashes on a user's iPhone with EXC_BAD_ACCESS in libcoreclr. Pull the .ips log with idevicecrashreport, run the script, and get a symbolicated backtrace pointing to the exact runtime function and source line. ## Quick Start Symbolicate the .NET frames in my iOS crash log MyApp-2026-02-25.ips and show me the faulting thread backtrace.