android-debugging

Filter logcat by your app's process ID with `adb logcat --pid=$(adb shell pidof -s com.example.app)` or save the full log with `adb logcat -d`. Read the entire stack trace, since the root cause is usually at the bottom of the `Caused by:` chain.

Use the mapping file generated at build time in `app/build/outputs/mapping/<variant>/mapping.txt`. Run `./gradlew :app:retrace --stacktrace-file crash.txt` or the retrace CLI directly to restore original class and method names.

ANRs occur when the main thread is blocked, typically by database or network calls on the main thread, `runBlocking` on main, or deadlocks between coroutine scopes. Pull `/data/anr/traces.txt` and look for the main thread in MONITOR state to find the lock holder.

Yes, the skill explicitly covers KMP issues alongside Android-specific techniques. It supplements a systematic debugging workflow with Android tools like Logcat, ADB, and Gradle diagnostics that apply to shared KMP code running on Android targets.

Common causes include State objects created inside composition without `remember`, missing `equals()` on state data classes, and unstable captured references like mutable collections. Use Layout Inspector's recomposition counts or `android layout --diff` to identify hot paths.

Add LeakCanary as a `debugImplementation` dependency, which surfaces leak traces automatically in notifications. Read the trace top-to-bottom: the first bold line is the leaking object, and the path shows what holds the reference.