maestro icon indicating copy to clipboard operation
maestro copied to clipboard

Maestro systematically fails with "Device requested but not connected" in v1.39.0

Open hormesiel opened this issue 4 months ago • 3 comments

Is there an existing issue for this?

  • [X] I have searched the existing issues and didn't find mine.

Steps to reproduce

  1. I opened PowerShell and ran adb kill-server ; adb -a -P 5037 nodaemon server
  2. I opened WSL Ubuntu and ran:
    • WINDOWS_HOST_IP_ADDRESS=$(ip route show | grep -i default | awk '{ print $3}')
    • export ADB_SERVER_SOCKET=tcp:$WINDOWS_HOST_IP_ADDRESS:5037
    • adb devices and successfully saw my connected physical device
    • maestro --device ae2395da --host "$WINDOWS_HOST_IP_ADDRESS" test /mnt/c/Users/<path-to-flows>/app-launch.yaml

Actual results

No matter what options I throw at him, Maestro won't run my tests anymore:

image

It was working fine before upgrading to 1.39.0 with --device . instead of specifying a specific device id. Now neither work.

Expected results

I expect tests to run.

About app

This is a closed source app and I can't share any binary sorry.

About environment

  • Windows 11

Logs

No response

Maestro version

1.39.0

How did you install Maestro?

install script (https://get.maestro.mobile.dev)

Anything else?

No response

hormesiel avatar Oct 22 '24 08:10 hormesiel