Skip to content
Back to home

Dependable device host discovery

Fixed the two ways a remote simulator or emulator host failed from another machine. Testing a Windows host from a Mac no longer reported npm as missing because the check could not launch it, and a failed check named the real launch or process failure instead. A Mac with only adb was not mistaken for an Android host, so refreshing it kept its iOS Simulators, and a host that could not list its stopped virtual devices kept the devices it had already found and reported why.

PR
…
Status
Superseded

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

Windows desktop

windows-desktop

Windows desktop

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

Windows desktop

windows-desktop

Connection failed

npm is missing from the non-interactive SSH PATH.

Windows desktop

MacBook Pro

macbook-pro

Connection failed

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

Mock hosts: the MacBook Pro testing the Windows desktop, and the Windows desktop testing the MacBook Pro. Test connection runs the check again and lands on the same outcome; collapse or expand a failure to hide or read it. Nothing connects or saves.