-
Notifications
You must be signed in to change notification settings - Fork 491
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 14 Beta 5 stuck in "Preparing" step in STF #692
Comments
@T0n3l You should compile latest STFService.apk from https://github.com/DeviceFarmer/STFService.apk and replace itto your STF in /app/vendor/STFService/ folder. |
@cert-x on device is installed the apk with version 2.4.10. is there any new version of the apk? |
looking up in the logs, I found the following stacktrace:
|
hi, guys. I've updated the apk as you described above, but still get an error. I use container
|
Do you have latest adbd? |
I cannot locate |
@gadgadskiy from the DEPLOYMENT.MD adbd.service |
@cert-x, we don't have it at all because we use a separate container for each device (and stf client container calls adb from them). |
@cert-x I think the app is crashing on the Android device considering the logs I posted yesterday |
@T0n3l Do other devices work properly with Android 14 beta 5? - If yes, do issue mostly connected to this device. |
@cert-x This is the only device I have that accepts Android 14 Beta. Unfortunately, I am not able to test with other device. |
@cert-x, yes, I updated the apk and restarted both containers but still got the same error in all cases. |
@cert-x My problem was fixed after upgrading stf apk to version 12. Thank you! |
Replacing the APK helped. |
Latest dockerhub image that contains the v2.4.12 apk file did not solve the issue with Android 14 QPR2 Beta Program, Pixel 7. Same device works when using latest public android 14 version with latest stf release v3.6.6, but when beta program is opted in, the device gets stuck at preparing phase (reproduced twice) with the following logs:
|
My devices are Pixels running Android 14, I seem to have the same problem, stf was build with npm, install
I see STFService.apk has been mentioned being the problem, is there any way to check what version I'm running?
|
The root reason for my case seems to be DeviceFarmer/STFService.apk#130. Same logcat error seen with pixel 7 after march update, as with pixel 7 beta previously. Tested with STFService.apk 2.5.0 and 2.4.11 by installing release package via adb and running it with |
I am using docker image for devicefarmer/stf:3.6.5 (link here -> https://hub.docker.com/layers/devicefarmer/stf/3.6.5/images/sha256-2101f29fc71c8cf7db6fab805b570a286ba7932cc1fbfe977ec2d42512c1e2fe?context=explore) and after plugging a device with Android 14 Beta 5 (Google Pixel 6) it can be controlled via adb on the machine, but it is stuck in "Preparing" state in STF.
The text was updated successfully, but these errors were encountered: