Ios Android Logs

When you're debugging a Capacitor app and need to see what's happening on the device, this walks you through the fastest ways to stream logs on both iOS and Android. It covers the modern devicectl and simctl commands for iOS, adb logcat variations for Android, and includes predicate filters so you're not drowning in system noise. The real value is in the filtering examples, like isolating JavaScript errors from the WebView or targeting specific Capacitor plugins by tag. If you've been stuck using Console.app or Android Studio's GUI and want faster command-line workflows, the quick reference tables and common filter patterns will save you time every debugging session.

skills.sh installs: 261
GitHub stars: 43
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add cap-go/capacitor-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.