Ios Android Logs

When you need to see what's actually happening on a device, this skill gives you the complete rundown of iOS and Android logging tools. It covers everything from Console.app and Android Studio's Logcat to command-line tools like devicectl and adb logcat, with real filtering examples for finding JavaScript errors, crashes, or network issues in the noise. The predicate examples for iOS and the adb filter patterns are especially handy since those syntaxes are easy to forget. It's comprehensive without being overwhelming, and the side-by-side platform comparison makes it easy to switch contexts when you're debugging across iOS and Android builds of the same app.

skills.sh installs: 1.3K
GitHub stars: 77
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add cap-go/capgo-skills --skill ios-android-logs --agent claude-code

Installs into .claude/skills of the current project.

Files

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.