ios-debugging

Diagnose iOS, macOS, watchOS, and visionOS crashes using backtraces and LLDB.

1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/Emasoft/emasoft-complete-ios-app-authoring --skill ios-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ios-debugging
Source: https://github.com/Emasoft/emasoft-complete-ios-app-authoring/tree/main/skills/ios-debugging
Command: npx skills add https://github.com/Emasoft/emasoft-complete-ios-app-authoring --skill ios-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the guesswork and wasted time when debugging iOS, macOS, watchOS, and visionOS apps, providing a systematic, evidence-based workflow to diagnose crashes, hangs, build errors, concurrency violations, memory leaks, and wrong runtime behavior instead of patching symptoms.

Core Features & Use Cases

  • Crash & Hang Triage: Symbolicate and classify crash logs (EXC_BAD_ACCESS, SIGABRT, watchdog 0x8BADF00D, jetsam OOM), capture live backtraces with LLDB, and identify the root cause from the crashing thread's first app frame.
  • Concurrency & Memory Debugging: Fix Swift 6 actor isolation violations, @MainActor/Sendable bugs, retain cycles, and memory leaks using sanitizers, Instruments, and structured inspection workflows.
  • Proactive Bug Detection: Use the 7 assumption lenses to find hidden bugs in code that compiles and passes tests, and maintain a DEBUG_LOG knowledge base to log prevention rules and avoid recurring issues.
  • Use Case: For example, when a user reports a crash after tapping a button on a specific screen, use this Skill to capture the backtrace, rule out the obvious symptom, identify the actual root cause (such as a dynamic UIColor provider crashing on the AsyncRenderer thread), fix it, and log a prevention rule to stop the bug from reappearing.

Quick Start

Use the ios-debugging skill to analyze the provided crash log or backtrace, identify the root cause of the reported iOS app issue, and deliver a step-by-step fix with a preventive rule to avoid recurrence.

Frequently Asked Questions about ios-debugging

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

FAQPage Schema
How do I diagnose an iOS crash from a backtrace using LLDB?

To diagnose an iOS crash using LLDB, capture the live backtrace, symbolicate the crash log, and identify the root cause from the crashing thread's first app frame using an evidence-based workflow.

What is the best way to fix Swift 6 actor isolation violations and concurrency bugs?

Fixing Swift 6 actor isolation violations requires using sanitizers and structured inspection workflows to identify @MainActor or Sendable bugs, enforcing root-cause fixes over symptom patches.

How do I hunt down memory leaks and retain cycles in a SwiftUI app?

Hunting down memory leaks and retain cycles in SwiftUI involves using Instruments and structured inspection workflows to systematically identify and resolve the leaking references.

Can I use this debugging workflow for watchOS and visionOS runtime crashes?

Yes, this debugging workflow applies to watchOS and visionOS runtime crashes, hangs, and build errors, utilizing the same backtrace-first methodology and LLDB tooling.

How do I symbolicate crash logs like EXC_BAD_ACCESS and watchdog timeouts?

To symbolicate crash logs like EXC_BAD_ACCESS and watchdog 0x8BADF00D, classify the crash type and extract the root cause from the crashing thread's first app frame.

How do I find hidden bugs in Swift code that compiles and passes tests?

Finding hidden bugs in passing Swift code involves applying seven assumption lenses to proactively detect issues and logging prevention rules to a DEBUG_LOG knowledge base to avoid recurrence.