Skip to content

Commit d40fd85

Browse files
committed
docs(android): name WSL interop or Wine as the adb.exe execution path
1 parent 90193ef commit d40fd85

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

‎packages/platform-android/src/doctor.ts‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -213,7 +213,7 @@ function detectWindowsAdb(versionOutput: string): WindowsAdbReport | undefined {
213213
}
214214

215215
/**
216-
* A Windows adb.exe reached from a POSIX host (WSL interop, Wine, a mounted volume) answers
216+
* A Windows adb.exe reached from a POSIX host through WSL interop or Wine answers
217217
* `adb version`, but it resolves every host path it is handed as a Windows path, so pulls, pushes,
218218
* and installs miss the host's files. Older and third-party adb builds omit the `Installed as`
219219
* banner, so the `Running on Windows` line is the fallback signal for them.

‎website/docs/docs/known-limitations.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ An unattended first Android snapshot therefore times out with a helper install f
4646

4747
## Android: WSL needs Linux platform-tools
4848

49-
Under WSL, the Windows `adb.exe` (for example from an `ANDROID_HOME` under `/mnt/c`) answers `adb version` but resolves every host path it is given as a Windows path, so recordings, pulls, and installs fail. Install Linux Android platform-tools inside WSL, put them first on `PATH`, and point `ANDROID_HOME` at a Linux SDK. `agent-device doctor` fails the toolchain check with reason `android_adb_windows_binary_on_posix_host` when `adb` reports a Windows install path or reports that it is running on Windows. The same check catches a Windows `adb.exe` reached from macOS or Linux through Wine or a mounted volume.
49+
Under WSL, the Windows `adb.exe` (for example from an `ANDROID_HOME` under `/mnt/c`) answers `adb version` but resolves every host path it is given as a Windows path, so recordings, pulls, and installs fail. Install Linux Android platform-tools inside WSL, put them first on `PATH`, and point `ANDROID_HOME` at a Linux SDK. `agent-device doctor` fails the toolchain check with reason `android_adb_windows_binary_on_posix_host` when `adb` reports a Windows install path or reports that it is running on Windows. The same check catches a Windows `adb.exe` reached from macOS or Linux through WSL interop or Wine.
5050

5151
## Android: no clipboard access over adb on Android 16
5252

0 commit comments

Comments
 (0)