| name | android-crash |
| description | App crashed or ANR. Pull logcat, find the stack, fix. |
| category | android |
Android crash
Get the stack, then fix the cause. Do not guess the Activity.
When to use
- Crash, ANR, "it died", red screen, process died
- The user pasted a stack or said it failed after install
When not to use
- Build failed before install (android-build)
- Compose preview looks wrong (android-compose)
Procedure
env_status. If the Linux prefix or Shizuku is missing and you need logcat, tell the user once.
shell logcat -d -t 200 *:E (or the package name if you know it). Check: a stack or FATAL EXCEPTION.
grep the top frames in the workspace. read_file the file. Check: the crashing line.
- Fix with
edit_file. Check: the NPE / race / bad cast is actually gone.
- Tell the user how to relaunch. If they can, pull logcat again.
Pitfalls
- Toybox may not have logcat flags you expect. Use
logcat -d.
/data/local/tmp is not evidence of Shizuku. Use env_status.
- Do not invent linker64 workarounds.
Verification
The same launch path no longer throws that stack.