-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Fix adb.push fail to push no extention file (cause minicap installation failure) #1288
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
base: master
Are you sure you want to change the base?
Conversation
修复了no extention file会被当做folder处理的问题 还重写了部分,原本push file和folder的算法混在一起,改成了file和folder大部分逻辑分开讨论
This is happening for me too... it always fall backs to ADBCAP because of push error with the file without extension. In my case, I've used Mac and Linux, failing in both |
Yeah, it actually should fall back to JAVACAP but unfortunately JAVACAP also couldn't work in current version. I successfully fixed that by replace Yosemite.apk with an old version according to #1236. |
Did you try to monkey-patch minicap installation to upload the file using a (dummy?) extension? Did it work? I tried your fix, but it didn't work for me either..
I also saw there is an apk to be used instead https://github.com/openatx/stf-binaries/blob/master/take-screenshot-with-minicap-apk.sh |
Oh, I guess you phone runs the latest Android 15(SDK 35). Unfortunately there is no minicap.so for this Android SDK yet. Yeah, you may have to try that apk instead. Check this btw DeviceFarmer/minicap#70 |
If I do that, it says than |
修复了no extention file会被当做folder处理的问题
还重写了部分,原本push file和folder的算法混在一起,没办法处理no extention file,改成了file和folder大部分逻辑分开讨论
这个bug导致了minicap文件无法adb push进手机-》minicap installation failed