We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adb kill-server ; adb -a -P 5037 nodaemon server
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
maestro --device ae2395da --host "$WINDOWS_HOST_IP_ADDRESS" test /mnt/c/Users/<path-to-flows>/app-launch.yaml
No matter what options I throw at him, Maestro won't run my tests anymore:
It was working fine before upgrading to 1.39.0 with --device . instead of specifying a specific device id. Now neither work.
1.39.0
--device .
I expect tests to run.
This is a closed source app and I can't share any binary sorry.
No response
install script (https://get.maestro.mobile.dev)
The text was updated successfully, but these errors were encountered:
MA-2380 Maestro systematically fails with "Device requested but not connected" in v1.39.0
Sorry, something went wrong.
In the meantime I rolled back to version 1.38.1 and it works fine.
Thank you man, it worked for me! rolled back version.
same here. any solutions if I want to use the latest version of maestro?
No branches or pull requests
Is there an existing issue for this?
Steps to reproduce
adb kill-server ; adb -a -P 5037 nodaemon server
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 devicemaestro --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:
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
The text was updated successfully, but these errors were encountered: