What problem does it solve? Crash logs from .NET MAUI and Mono apps on iOS, tvOS, Mac Catalyst, and macOS contain raw hexadecimal addresses for native backtrace frames, making it impossible to identify which .NET runtime functions caused the crash without manual symbol resolution. ## Core Features & Use Cases - .ips Crash Log Parsing: Parses the two-part JSON .ips format, extracts UUIDs, load addresses, and frame addresses from usedImages and thread backtraces, and interprets exception data like EXC_CRASH, SIGABRT, and managed exception messages in the asi field. - Automatic Symbol Resolution: Locates UUID-matched dSYM bundles from build outputs, SDK packs, or the NuGet cache, and automatically downloads .dwarf symbols from the Microsoft symbol server using Mach-O UUIDs. - Batch Symbolication with atos: Resolves libcoreclr and libmonosgen-2.0 frames to function names, source files, and line numbers via atos, with an automation script (Symbolicate-Crash.ps1) handling the full workflow. - Use Case: A .NET MAUI app crashes on a user's iPhone with EXC_BAD_ACCESS. Pull the .ips file with idevicecrashreport, run the script, and get a symbolicated backtrace pointing to the exact .NET runtime source lines. ## Quick Start Ask the AI to symbolicate the .NET frames in your .ips crash log file, for example: "Symbolicate the .NET runtime frames in MyApp-2026-02-25.ips and tell me what caused the crash."