apple-crash-symbolication

Automates .NET runtime frame symbolication in Apple platform crash logs using dSYM files and atos.

Updated May 28, 2026
One-click install
npx skills add https://github.com/ojrojas/AgentsInstructions --skill apple-crash-symbolication-ojrojas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apple-crash-symbolication
Source: https://github.com/ojrojas/AgentsInstructions/tree/main/.claude/skills/dotnet-diag/skills/apple-crash-symbolication
Command: npx skills add https://github.com/ojrojas/AgentsInstructions --skill apple-crash-symbolication-ojrojas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires atos, dwarfdump, idevicecrashreport, libimobiledevice, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of symbolication for .NET runtime frames in Apple platform crash logs, making it easier to debug and resolve crashes in .NET MAUI and Mono apps.

Core Features & Use Cases

  • Crash Log Parsing: Automatically parses .ips crash logs from Apple platforms (iOS, tvOS, Mac Catalyst, macOS).
  • Symbol Location: Locates and downloads dSYM debug symbols from the Microsoft symbol server or local build outputs.
  • Symbolication: Uses atos to symbolicate native backtrace frames to function names, source files, and line numbers.
  • Use Case: When a .NET MAUI or Mono app crashes on an Apple platform, this Skill can be used to automatically symbolicate the crash log and provide detailed information about the crash.

Quick Start

Run the 'symbolicate-crash' script with the path to the crash log file: ./scripts/Symbolicate-Crash.ps1 -CrashFile path/to/crash.ips

Frequently Asked Questions about apple-crash-symbolication

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I symbolicate .NET MAUI crash logs from iOS or macOS?

You can symbolicate .NET runtime frames in Apple crash logs by running a script that parses .ips files, locates dSYM debug symbols, and uses atos to map native backtrace frames to source files and line numbers.

What is needed to resolve Mono runtime frames in Apple .ips crash logs?

Resolving Mono runtime frames in Apple .ips crash logs requires the atos and dwarfdump command-line tools, alongside matching dSYM debug symbols obtained from local build outputs or the Microsoft symbol server.

Can I use this crash debugging process for Mac Catalyst and tvOS apps?

Yes, the crash symbolication process supports .NET MAUI and Mono app crashes across iOS, tvOS, Mac Catalyst, and macOS platforms by parsing and resolving the generated .ips crash logs.

Does crash log symbolication work without local dSYM files?

Crash log symbolication can still work without local dSYM files by automatically downloading the required debug symbols from the Microsoft symbol server to resolve the native backtrace frames.

Do I need libimobiledevice to retrieve and symbolicate Apple crash logs?

Yes, libimobiledevice and the idevicecrashreport dependency are required to retrieve crash logs directly from Apple devices before parsing and symbolicate the .ips files.