ad-detach

To detach the Android debugger without stopping the app, invoke the detach command to call vm.dispose and remove adb port forwards. This cleanly releases resources and allows you to reattach later without restarting the running session.

Detaching the Android debugger can leave ports bound if the session is not cleanly terminated. Properly invoking vm.dispose and resetting the MCP server state removes adb port forwards and prevents stale sessions from holding network resources.

To safely end an Android debug session and reattach later, execute the detach command during your end-of-session workflow. It invokes vm.dispose, removes adb port forwards, and resets server state to ensure the app continues running without port conflicts.

You can remove breakpoints and safely release resources from a running Android app without restarting by detaching the debugger. Invoking vm.dispose cleanly terminates the JDWP session and resets server state, allowing the app to continue uninterrupted.

When you detach the Android debugger by invoking vm.dispose, the session is cleanly terminated to safely release resources. This process removes bound ports and resets the MCP server state to prevent stale breakpoints from persisting in future sessions.