Skip to content
Skills Library
Programming · Analysis

debug-crash

/debug-crash

Debug iPad/iPhone app crashes by deploying with console capture. Use when user says "app crashed", "debug crash", "why did it crash", "閃退", "當掉", or after a deploy-and-test cycle where the app dies. Uses xcrun devicectl --console to capture stdout/stderr including Swift fatal errors, then analyzes the output.

Licence
MIT
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Debug iPad/iPhone app crashes by deploying with console capture. Use when user says "app crashed", "debug crash", "why did it crash", "閃退", "當掉", or after a deploy-and-test cycle where the app dies. Uses xcrun devicectl --console to capture stdout/stderr including Swift fatal errors, then analyzes the output.

Triggers from the description

app crasheddebug crashwhy did it crash
Original author description

Debug iPad/iPhone app crashes by deploying with console capture. Use when user says "app crashed", "debug crash", "why did it crash", "閃退", "當掉", or after a deploy-and-test cycle where the app dies. Uses xcrun devicectl --console to capture stdout/stderr including Swift fatal errors, then analyzes the output.

How it works

  1. When to Use
  2. Execution Steps
Original SKILL.md headings · 73 lines, 315 words
SKILL.md preview
---
name: debug-crash
description: |
  Debug iPad/iPhone app crashes by deploying with console capture.
  Use when user says "app crashed", "debug crash", "why did it crash",
  "閃退", "當掉", or after a deploy-and-test cycle where the app dies.
  Uses xcrun devicectl --console to capture stdout/stderr including
  Swift fatal errors, then analyzes the output.
allowed-tools:
  - Bash
  - Read
  - Glob
  - Grep
  - AskUserQuestion
---

# Debug Crash

Deploy iOS app with console capture to diagnose crashes.

## When to Use

- App crashes/閃退 on device
- Need to see print() output from device
- Swift fatal errors (misaligned pointer, force unwrap, etc.)
- Need crash backtrace without full Xcode debugger

## Execution Steps

### Step 1: Build Debug

```bash
xcodebuild build -project <proj> -scheme <scheme> -configuration Debug -destination 'generic/platform=iOS' 2>&1 | grep -E '(error:|BUILD)'
```

### Step 2: Install on Device

```bash
xcrun devicectl device install app --device <udid> "<app_path>" 2>&1
```

### Step 3: Launch with Console Capture

This is the key step — `--console` captures all stdout/stderr:

```bash
xcrun devicectl device process launch \
  --device <udid> \
  --terminate-existing \
  --console \
  <bundle_id> 2>&1
```

The command blocks until the app exits. If the app crashes, the output includes:
- `Fatal error: <message>` — Swift runtime errors
- `App terminated due to signal N` — crash signals (6=SIGABRT, 11=SIGSEGV, 15=SIGTERM)
- All `print()` output from the app

### Step 4: Analyze Output

Common crash patterns:

| Output | Cause | Fix |
|--------|-------|-----|
| `load from misaligned raw pointer` | UnsafeRawPointer.load with unaligned offset | Use byte-by-byte read |
| `Thread 1: EXC_BAD_ACCESS` | Use-after-free or null pointer | Check object lifetime |
| `signal 9` (SIGKILL) | OOM — system killed for memory | Reduce allocations, check for leaks |
| `signal 6` (SIGABRT) | Assertion failed | Check guard/precondition |
| No crash output, app just dies | Jetsam (memory) | Check GPU texture allocation |

### Step 5: Check Crash Logs (if console doesn't show enough)

```bash
# Local crash reports
find ~/Library/Logs/DiagnosticReports -name "*<app>*" -type f | xargs ls -t | head -3

# Read latest
head -100 "<latest_crash_log>"
```

### Step 6: Report

Show:
- Crash message (if any)
- Signal number and meaning
- Relevant print() output before crash
- Suggested fix

Versions

The database has no other skills named debug-crash.

Database snapshot: 13.11.2026 · package version 432ac430c5f0 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100ios-android-logs
    Gets, filters, streams, and saves logs and crash reports from Capacitor apps on iOS Simulator, iPhone, Android emulator and devices. Explains where Capacitor output goes (iOS bridge and mirrored JS console lines are stdout-only, so missing from Console.app and `log stream`;…
  • 100run-device
    Build, install, and launch an iOS app on a physical iPhone or iPad entirely from the command line (no Xcode GUI), using xcodebuild + devicectl. Use when the user wants to run, test, or screenshot their app on a real device without opening Xcode.
  • 98ci-crash-dump
    Download and debug crash dumps from CI test failures in dotnet repositories. Use when a CI test crashed (not just failed), when the user wants to debug a crash dump from a PR or build, or when asked "debug dump", "download dump", "crash dump from CI", "test crashed", "analyze…
  • 86herdr-ios-simulator
    Build, run, drive and debug iOS apps on a simulator shared with the user inside herdr. Use whenever the user wants to run, see, test or debug an iOS or iPhone app ("run it on the simulator", "show me on the iPhone", "tap through the sign-in flow", "why does it crash", "check the…
  • 100simctlhouse
    Get an exclusive iOS simulator (iPhone or iPad) for building, testing or running an app, and give it back when done. Use whenever you are about to run `xcodebuild test`/`build` or `xcrun simctl` against a simulator, need a simulator destination or UDID, or choose a simulator, so…
  • 100debug-deep
    Deep debugging using multi-agent analysis and error pattern matching. Use when user reports a bug, error, crash, or unexpected behavior. Triggers on "debug", "fix", "broken", "crash", "error", "bug".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.