D07
Debugger attached on AndroidPending
Attaching a Java debugger to the app process raises debugger_attached.
How to read this page
A scenario is one test case: prepare the environment, run the steps, then compare the expected result (written before the run) with the observed result (copied from the run, with screenshots).
- D07 · D
- Run on a real phone, used normally.
- Pending
- Not run yet. The expected result is written down; there is no observed result.
Why it matters
The Android check (Debug.isDebuggerConnected / waitingForDebugger) is a separate implementation from iOS and needs its own run.
Environment
- Tools
- Android Studio debugger, or jdb through adb forward jdwp:<pid>
Setup
Prepare the environment.Then run the steps.
- 01Install a debuggable (debug) build — a release build exposes no JDWP port to attach to.
Steps
What to run.What to read.
- 01Attach the debugger to the running app.
- 02Bring the app to the foreground (it re-checks) or tap Re-check.
- 03Detach and re-check.
Expected result · written before the run
Status: compromised1 signal.
Observed result
Not run yet.No observed result.
Limitations
Attempted on 2026-10-06 on the rooted OnePlus, but the installed example build was a release build (not debuggable), so no debugger could attach.
Checks this scenario covers
Every check this test case touches — including ones that aren't expected to fire here. The expected and observed results above say which ones should and did. Each links to how the check works.