Skip to main content
skill CX Codex

ios-android-logs — Claude Code skill: Capacitor app logs

A skill that shows where Capacitor logs and crash reports live on iOS and Android, and how to narrow the output down to your own process.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Cap-go/capgo-skills --skill ios-android-logs -a claude-code
Open on GitHub

What ios-android-logs does

The skill covers the trap most people hit first: on iOS the Capacitor bridge messages and the mirrored console.log lines go to stdout only, so Console.app and log stream never show them. On Android the same lines land in logcat under the Capacitor and Capacitor/Console tags. The agent picks the channel that actually carries your message before you start hunting for a cause.

It ships ready commands per scenario: xcrun simctl launch --console-pty for the simulator, xcrun devicectl device process launch --console for a physical iPhone, log collect --device-udid for a unified log snapshot, and adb logcat --pid or -b crash on Android, along with tombstones, ANRs and adb bugreport. There is a table of failure modes — why --level error keeps printing everything, what to do about unable to find utility "devicectl", why adb logcat --pid= comes back empty. One procedure step is redacting tokens, emails and auth headers before a log leaves the team.

Keep in mind that JS console mirroring follows loggingBehavior, so a Release build on the default debug setting produces no Capacitor logs at all. The skill stops at capture: root-cause work belongs to debugging-capacitor, and production crash reporting through Sentry or Crashlytics is capacitor-native-observability.

What it helps with

  • find where console.log output went on a device
  • filter logcat down to a single app by PID
  • pull an .ips crash report off a connected iPhone
  • save a unified log to a file for a teammate
  • work out why --level error still prints everything

Example prompts for the agent

  • Show me how to stream Capacitor logs on the iOS Simulator
  • My console.log isn't showing on Android — which logcat tags should I watch?
  • Grab the crash log from my connected iPhone and save it to a file

How to install ios-android-logs

1Skills CLI (Vercel)

npx skills add Cap-go/capgo-skills --skill ios-android-logs -a claude-code

2Manually: put the files in place

~/.claude/skills/ios-android-logs/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/ios-android-logs/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about ios-android-logs

How do I install ios-android-logs in Claude?

Run npx skills add Cap-go/capgo-skills --skill ios-android-logs -a claude-code. The skill file lands at ~/.claude/skills/ios-android-logs/SKILL.md.

What does ios-android-logs do?

It helps you get, filter, stream and save logs and crash reports from a Capacitor app on simulators, emulators and physical devices. It also explains which channel carries a given message and how to narrow output to your process.

Why don't Capacitor logs show up in Console.app?

On iOS the bridge messages and mirrored JS console go to stdout, while Console.app and log stream only read the unified log. Use xcrun simctl launch --console-pty or xcrun devicectl device process launch --console instead.

Source text

SKILL.md · MIT
---
name: ios-android-logs
description: 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`; Android tags `Capacitor` and `Capacitor/Console`). Covers `xcrun simctl spawn booted log stream --predicate`, `simctl launch --console-pty`, `xcrun devicectl device process launch --console`, `log collect --device-udid`, Console.app, devicectl `systemCrashLogs`, `adb logcat --pid`, `-b crash`, Android Studio `package:mine`, tombstones, ANRs, `adb bugreport`. Use for "how do I see logs", "console.log not showing on device", "no logs in Console.app", "get the crash log", "logcat too noisy". Do not use for diagnosing the bug once logs are in hand (debugging-capacitor), production crash SDKs (capacitor-native-observability), MCP log tooling (capacitor-mcp), or profiling (capacitor-performance).
---

# iOS and Android Logs for Capacitor Apps

Pick the log channel that actually carries the message you need, filter to the app, capture to a file, hand off to diagnosis.

## When to Use

TRIGGER when:
- User asks how to view, stream, filter, or save device/simulator logs.
- `console.log` output or `⚡️` Capacitor lines are missing on iOS/Android.
- User needs a crash report (`.ips`, tombstone, ANR) from a device or simulator.
- Logcat or the unified log is too noisy; user wants only their app or plugin.
- A log command fails or misbehaves: `--level error` still shows everything, `unable to find utility "devicectl"`, `Error: Unexpected argument 'log'`, `adb: no devices/emulators found`.

Do not use:
- Interpreting the error and fixing the app -> `debugging-capacitor`.
- Production crash/ANR reporting (Sentry, Crashlytics, Datadog) -> `capacitor-native-observability`.
- AI agent log streaming via MCP servers -> `capacitor-mcp`.
- CPU/memory profiling -> `capacitor-performance`.
- UIScene lifecycle migration -> `capacitor-uiscene-migration`.

## Where Capacitor Output Goes (the main trap)

| Source | iOS | Android |
|---|---|---|
| Capacitor bridge messages (`⚡️  Loading app at ...`, `⚡️  To Native ->`, errors) | **stdout only** (`print`) | logcat tag `Capacitor` and `Capacitor/<Sub>` |
| JS `console.log/warn/error` mirrored natively | stdout as `⚡️  [log] - ...` | logcat tag `Capacitor/Console` as `File: ... - Line N - Msg: ...` |
| JS console, full fidelity (objects, stack traces) | Safari Web Inspector | `chrome://inspect` |
| Plugin/app code using `os.Logger` / `NSLog` | unified log (Console.app, `log stream`) | n/a |
| Plugin code using `android.util.Log` / Capacitor `Logger` | n/a | logcat |
| Native crash | `.ips` crash report | `FATAL EXCEPTION` in logcat + crash buffer; tombstone for native code |

Consequences:
- On iOS, Console.app and `log stream` will **not** show Capacitor's `⚡️` lines or mirrored JS console. Use Xcode's console, `xcrun simctl launch --console-pty`, or `xcrun devicectl device process launch --console`.
- Mirroring obeys `loggingBehavior` (`none` | `debug` | `production`, default `debug`): Release builds produce no Capacitor logs unless set to `production`.
- The iOS process name is the executable (`App` in the Capacitor template), not the display name. Filter with `process == "App"`.

## Quick Commands

```bash
# iOS Simulator: Capacitor + JS console (stdout), relaunching the app
xcrun simctl launch --console-pty --terminate-running-process booted com.example.app

# iOS Simulator: unified log for the app (os_log / NSLog / system messages)
xcrun simctl spawn booted log stream --level debug --predicate 'process == "App"'

# iPhone: install + launch with stdout attached (Xcode 15+ devicectl)
xcrun devicectl list devices
xcrun devicectl device process launch --console --terminate-existing --device <id> com.example.app

# iPhone: unified log snapshot of the last 10 minutes
sudo log collect --device-udid <udid> --last 10m --output /tmp/iphone.logarchive
log show /tmp/iphone.logarchive --predicate 'process == "App"' --info --debug

# Android: only this app (re-run after each app restart, PID changes)
adb logcat --pid="$(adb shell pidof -s com.example.app)"

# Android: Capacitor + JS console only
adb logcat -s Capacitor:V Capacitor/Console:V

# Android: crashes only
adb logcat -b crash
```

## Procedure

1. **Identify target**: Simulator/emulator vs physical device; Debug vs Release; which layer emitted the message (table above).
2. **Check connectivity**: `xcrun simctl list devices booted`, `xcrun devicectl list devices` (device must be unlocked, trusted, Developer Mode on), `adb devices -l`.
3. **Clear and reproduce**: `adb logcat -c` on Android; on iOS start the stream before relaunching the app.
4. **Filter early** by process/PID, then by subsystem/tag, then by text. Never paste unfiltered system logs into a conversation.
5. **Save** to a file (`> app.log`, `.logarchive`, `adb bugreport`) when the user needs to share it; redact tokens, emails, and auth headers before sharing outside the team.
6. **Hand off** the relevant lines to `debugging-capacitor` for root-cause work.

## Error Handling

| Message | Fix |
|---|---|
| `--level error` still shows every message | `log stream --level` only understands `default`, `info`, `debug` (it sets the floor, not a ceiling). Filter errors with `--predicate 'messageType == error OR messageType == fault'`. |
| `xcrun: error: unable to find utility "devicectl"` | Active dev dir is Command Line Tools. `sudo xcode-select -s /Applications/Xcode.app/Contents/Developer`. |
| `Error: Unexpected argument 'log'` (devicectl) | `devicectl` has no log streaming subcommand. Use `--console` for stdout, Console.app or `log collect --device-udid` for unified logs. |
| `log collect` fails with a permission error | Run with `sudo`; device must be unlocked and trusted. |
| `No devices are booted.` (simctl) | `xcrun simctl boot "<device name>"` or open Simulator. |
| `adb: no devices/emulators found` / `unauthorized` | Enable USB debugging, accept the RSA prompt, `adb kill-server && adb start-server`. |
| `adb logcat --pid=` prints everything / errors | App not running so `pidof` returned nothing. Launch the app first. |
| No `Capacitor/Console` lines on Android | `loggingBehavior: 'none'`, or Release build with default `debug`. |
| JS logs show but objects print as `[object Object]` | Native mirroring stringifies; use the WebView inspector for structured output. |

## Verification

- iOS sim: launch with `--console-pty`, see `⚡️  Loading app at capacitor://localhost` and a test `console.log('log-check')` as `⚡️  [log] - log-check`.
- iOS device: same via `devicectl device process launch --console`.
- Android: `adb logcat -s Capacitor/Console:V` shows `Msg: log-check`.
- Unified log: a plugin `Logger(subsystem: "com.example.app", category: "test").info("log-check")` appears with `--predicate 'subsystem == "com.example.app"' --level info`.

## References

Only load a reference when its topic is in play.

| File | Load when |
|---|---|
| `references/ios-logs.md` | Unified log predicates, Console.app, `log collect`/`log show`, iOS crash reports via devicectl/Xcode, adding `os.Logger` to a plugin |
| `references/android-logs.md` | logcat buffers/formats/filters, Android Studio Logcat queries, ANRs, tombstones, bugreports, WebView (`chromium`) noise |

## Resources

- https://developer.apple.com/documentation/os/logging
- https://developer.apple.com/documentation/xcode/acquiring-crash-reports-and-diagnostic-logs
- https://developer.android.com/tools/logcat
- https://developer.android.com/studio/debug/logcat
- https://capacitorjs.com/docs/config

© Cap-go · MIT · Cap-go/capgo-skills

Similar skills

Everything for Mobile →

From the same set29

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor