-
Notifications
You must be signed in to change notification settings - Fork 77
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
Failed to run shell on marshmallow physical device #50
Comments
This actually makes Maestro test to fail run on Marshmallow devices. |
Hey I believe this is due to a bug in the implementation of the base adb protocol. When I looked into this last, our experimental go implementation works on 6.0 devices while this kotlin implementation does not. I tried to fix a similar issue in this PR: https://github.com/mobile-dev-inc/dadb/pull/38/files but we ended up reverting due to it causing hangs in our cloud infra. We did not look further into this. I would start by looking into AdbStream to see if there are any discrepancies between this implementation and the go version (which I believe does still work on 6.0 devices. |
@Leland-Takamine the link to the go implementation is not accessible, private repo? |
Are there plans to publish the go implementation? I'd like to look into this |
Would also like to look into this, if you can share a snippet of the |
ADB docs say API < 24 don't support the v2 shell protocol which is used by dadb. https://android.googlesource.com/platform/packages/modules/adb/+/refs/heads/main/SERVICES.TXT#164 |
Is this and Maestro still being actively worked on? |
maestro probably yes, this library seems a bit dead :/ |
Running simple shell:
Fails on physical device 6.0 (Marshmallow):
Android Debug Bridge version 1.0.41
Version 33.0.3-8952118
Any ideas why?
The text was updated successfully, but these errors were encountered: