// Capture quick Android UI evidence with explicit launches, UIAutomator dumps, and adb screenshots for fast visual debugging and reproducible repro notes.
Use ADB to connect devices, install Android debug builds, and troubleshoot deployment failures. Use for device detection errors, install failures, launch failures, package selection across flavors, and first-pass process checks. For deeper runtime investigation, prefer the Argent workflow.
Investigate Android runtime bugs with evidence-first Argent workflows. Use for emulator targeting, runtime console/network inspection, UI hierarchy capture, optional native traffic inspection, and root-cause analysis before changing code.
Instruction-to-skill navigation map. Use when routing tasks to the right instruction and skill files or migrating legacy guidance to the split-doc model.
Step-by-step module creation checklist. Use when adding a new Gradle module and wiring build, DI, and architecture integration correctly.
Android platform/helper layer guide for AniTrend. Use when working in `:android:*` modules or deciding whether to reuse or extend existing Android-side helpers for configuration/theme, context or fragment utilities, notification permission flows, deep links, drawer/app-shell behavior, or other platform APIs.
Diagnose and fix silent empty-UI bugs caused by CacheRequest enum collisions in AniTrend. Use when a new offline-first source variant produces blank UI with no crash, no exception, and the Room tables have zero rows. Covers: cache_log collision diagnosis, ADB Room database forensics, WAL checkpoint, Chucker traffic check, CacheRequest isolation fix, and Koin factory update pattern.
| name | android-ui-automator-preview |
| description | Capture quick Android UI evidence with explicit launches, UIAutomator dumps, and adb screenshots for fast visual debugging and reproducible repro notes. |
| argument-hint | Provide package name, target screen, and whether app data should be cleared first |
pm clear.adb devices -l
adb shell pm clear <package-name>
adb logcat -c
adb shell am start -n <package-name>/co.anitrend.android.deeplink.component.screen.DeepLinkScreen
Why:
monkey randomness.adb shell input swipe 900 1700 200 1700 300
adb shell input swipe 900 1700 200 1700 300
adb shell input swipe 900 1700 200 1700 300
adb shell input swipe 900 1700 200 1700 300
adb shell input tap 540 2280
adb shell input tap 540 1285
adb shell input tap 84 2240
adb shell uiautomator dump /sdcard/window_dump.xml
adb pull /sdcard/window_dump.xml /tmp/window_dump.xml
adb exec-out screencap -p > /tmp/screen.png
grep -E "General|Manage|Catalogs|Support|Home|Discover|News|Forums|Episodes|FAQ" /tmp/window_dump.xml
pid=$(adb shell pidof -s <package-name> | tr -d '\r')
adb logcat -d --pid="$pid" > /tmp/<package-name>-ui-window.log