Skip to content
Back to home

Honest Android support on SSH hosts

Reports Android on an SSH device host only when it has a complete Android SDK: Platform-Tools, Android Emulator, and the command-line tools. A Mac with just adb on its PATH used to claim Android, and the device refresh that followed failed on the missing emulator and hid its iOS Simulators too. Such a host now keeps iOS and explains what Android needs.

Branch
GitHubfix/ssh-android-sdk-capability
PR
…

Comments

This fork

Devices

Device hosts

Add remote machines with simulator or emulator runtimes installed, and the selected environments will connect over SSH and set up device tools automatically.

MacBook Pro

macbook-pro

Original

Devices

Device hosts

Add remote machines with simulator or emulator runtimes installed, and the selected environments will connect over SSH and set up device tools automatically.

MacBook Pro

macbook-pro

Connection failed

Device list failed: The device command failed (exit code 127)

Mock host: the Windows desktop testing the MacBook Pro, which has Homebrew's adb but no Android Emulator or SDK. This fork keeps the Mac to iOS; the original counted adb as Android support, then failed the whole device list when the emulator was not there. Test connection runs the check again and lands on the same outcome. Nothing connects or saves.