-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
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
[Android] Failed to install maestro-app.apk; IOException: Install failed #829
Comments
I am seeing exactly this after upgrading to Mac OS Ventura 13.2.1 |
Workaround: Run against an emulator, this appears to be an issue only with physical devices. Other trace you might see if the APK is already installed:
|
I cannot use an emulator due to project constraints. Is there a workaround when using a physical device as well? |
Same error but I'm still using Mac OS Ventura 13.1. |
I am having the same issue on macOS 13.2 on a M1 Pro chip. |
Anyone know of a workaround? m1 max, macOS 13.2.1 |
Note: I have the same error using a Pixel3a it runs fine with a Samsung Galaxy S8. |
Seems to be a USB issue, works if I connect the device via wireless debugging. |
Thanks! Using wireless debugging does work for me as well. |
This is a strange issue where I was unable to make any progress with the test script when connected via USB Cable. The moment I connected the mobile device with Wireless Debugging, the Test Script got executed successfully. |
stuck at this! (macOS 12.5.1 ) |
Same here i just used adb connect and it's worked ;) |
Strange issue this one. On a Pixel 6A, It would work if connecting to wifi - so when maestro studio is run, you either disconnect the usb cable (so it auto connects to wifi), or choose wifi in the choices it gives you. Interestingly, on a Samsung phone (S21 ultra), I've had none of these difficulties, and it was working fine - even over USB. I'm not sure what the culprit is. |
Below steps work for Pixel 4a. |
@RahulJanagouda This is working for me |
wireless debugging works well and if we are debugging through wired connect physical device it throws error |
I was seeing these errors logged and was unable to run I'm running android x86 in a vm and use adb connect x.x.x.x:5555. This has worked fine across the lan with adb and scrcpy. On Ubuntu 20.04, maestro would exit with lots of errors, but if I ran it a few times it would start with errors and launch a browser window with spinning, no display and still unusable. Ubuntu 22.04 on the other hand, starts cleanly. Currently 1.34.1 I managed to get studio working on Ubuntu 20.04 after copying adb and glibc from Ubuntu 22.04. Ubuntu 20.04.6 LTS:
Ubuntu 22.04.3 LTS
I don't know if it's adb, GLIBC or both but it seems to work now. |
Thank you all for sharing your solutions to this problem. Based on these answers (first, second), and the high number of "👍" reactions on them, I assume that mostly fixes this problem. I think Maestro CLI could try enabling the "File transfer" option itself. I found this on StackOverflow:
Maybe support for this could be added to |
💡 Workaround
One possible workaround for this issue is to connect the device over Wi-Fi, which can help to mitigate the problem.
Document for connecting to a device over Wi-Fi
When I run
maestro studio
ormaestro test
, I encountered error:IOException: Install failed
It works well in an emulator and another new real device.
What I have tried:
dev.mobile.maestro
by command:adb uninstall dev.mobile.maestro
dev.mobile.maestro.test
adb install -r -d maestro-app.apk
Environment
Android device:
Google Pixel 4 (Android 13)
macOS
Ventura 13.2 (Apple M1 Max)
maestro
Error logs
The text was updated successfully, but these errors were encountered: