search

mobile-dev-inc / maestro

Painless Mobile UI Automation
https://maestro.mobile.dev/
Apache License 2.0
5.88k stars 281 forks source link

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

Open hormesiel opened 1 month ago

hormesiel commented 1 month ago

Is there an existing issue for this?

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

Logs

No response

Maestro version

1.39.0

How did you install Maestro?

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

Anything else?

No response

linear[bot] commented 1 month ago

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

hormesiel commented 1 month ago

In the meantime I rolled back to version 1.38.1 and it works fine.

sealove20 commented 4 weeks ago

Thank you man, it worked for me! rolled back version.

GuQye commented 1 week ago

same here. any solutions if I want to use the latest version of maestro?