Automation done with remote nodes using winappdriver.exe ipaddressport is not functional for Win UI 3 application if the ipaddress is not a loopback.
If the WinAppDriver is run as admin, then Win UI 3 application would not be able to launch with unable to launch in elevated context error. A future feature on WinAppSdk and a related Github issue
WinAppDriver can't run in non-admin mode for remote ipaddress with the following error: Run as administrator to listen on an hostname other than localhost, or to listen on port 80.
This leaves us unable to use WinAppDriver for Win UI 3 applications that rely on remote connections for testing.
Automation done with remote nodes using winappdriver.exe ipaddress port is not functional for Win UI 3 application if the ipaddress is not a loopback.
This leaves us unable to use WinAppDriver for Win UI 3 applications that rely on remote connections for testing.