ios-android-logs
Skill75 starsChanged 32 days agoMITView on GitHub
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).
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Aver005/agent-skillstheir own version, first seen Feb 14, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Aver005/agent-skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository56 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- capacitor-accessibilitySkill
- capacitor-app-intentsSkill
- capacitor-apple-review-preflightSkill
- capacitor-app-storeSkill
- capacitor-app-upgradesSkill
- capacitor-app-upgrade-v4-to-v5Skill
- capacitor-app-upgrade-v5-to-v6Skill
- capacitor-app-upgrade-v6-to-v7Skill
- capacitor-app-upgrade-v7-to-v8Skill
- capacitor-app-upgrade-v8-to-v9Skill
- capacitor-best-practicesSkill
- capacitor-ci-cdSkill
- capacitor-deep-linkingSkill
- capacitor-ios-resizabilitySkill
- capacitor-ios-security-hardeningSkill
- capacitor-keyboardSkill
- capacitor-mcpSkill
- capacitor-offline-firstSkill
- capacitor-performanceSkill
- capacitor-plugin-spm-supportSkill
- capacitor-pluginsSkill
- capacitor-plugin-upgradesSkill
- capacitor-plugin-upgrade-v4-to-v5Skill
- capacitor-plugin-upgrade-v5-to-v6Skill
- capacitor-plugin-upgrade-v6-to-v7Skill
- capacitor-plugin-upgrade-v7-to-v8Skill
- capacitor-plugin-upgrade-v8-to-v9Skill
- capacitor-push-notificationsSkill
- capacitor-securitySkill
- capacitor-splash-screenSkill
- capacitor-testingSkill
- capacitor-uiscene-migrationSkill
- capawesome-live-update-migrationSkill
- capgo-cli-usageSkill
- capgo-cloudSkill
- capgo-live-updatesSkill
- capgo-native-buildsSkill
- capgo-organization-managementSkill
- capgo-release-managementSkill
- capgo-release-workflowsSkill
- cocoapods-to-spmSkill
- cordova-to-capacitorSkill
- debugging-capacitorSkill
- framework-to-capacitorSkill
- ionic-appflow-migrationSkill
- ionic-designSkill
- ionic-enterprise-sdk-migrationSkill
- konsta-uiSkill
- safe-area-handlingSkill
- skill-creatorSkill
- sqlite-to-fast-sqlSkill
- subscription-app-revenueSkill
- tailwind-capacitorSkill
- webapp-to-capacitorSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 101
Only load a reference when its topic is in play.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.logoutput 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 errorstill 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 streamwill not show Capacitor's⚡️lines or mirrored JS console. Use Xcode's console,xcrun simctl launch --console-pty, orxcrun devicectl device process launch --console. - Mirroring obeys
loggingBehavior(none|debug|production, defaultdebug): Release builds produce no Capacitor logs unless set toproduction. - The iOS process name is the executable (
Appin the Capacitor template), not the display name. Filter withprocess == "App".
Quick Commands
# 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 crashProcedure
- Identify target: Simulator/emulator vs physical device; Debug vs Release; which layer emitted the message (table above).
- Check connectivity:
xcrun simctl list devices booted,xcrun devicectl list devices(device must be unlocked, trusted, Developer Mode on),adb devices -l. - Clear and reproduce:
adb logcat -con Android; on iOS start the stream before relaunching the app. - Filter early by process/PID, then by subsystem/tag, then by text. Never paste unfiltered system logs into a conversation.
- 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. - Hand off the relevant lines to
debugging-capacitorfor 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://localhostand a testconsole.log('log-check')as⚡️ [log] - log-check. - iOS device: same via
devicectl device process launch --console. - Android:
adb logcat -s Capacitor/Console:VshowsMsg: 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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

