Open AngelDev06 opened 9 months ago
Okay, so I went deep, and the problem seemed to be the issue with enough space on the OS. If you clear the caches, it will work.
Hi @AngelDev06 , I've also come across the emulator startup issue recently.
You can check the shell script ./scripts/android-run-tests.sh
. Before checking the property by adb shell getprop sys.boot_completed
, is there a command adb wait-for-device
out there to wait for device state change ?
What cache you cleaned? The GH one? How did you clean it?
I cleared space on GHA with something like this: https://github.com/android/nowinandroid/blob/420076f01aadd61f650b6848cd23643ca59226b8/.github/workflows/Build.yaml#L159-L168
What I get is the following:
I have 0 clue what's going on, I might be missing a package or something? I have initialized the action like this: