-
-
Notifications
You must be signed in to change notification settings - Fork 197
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
No SDCard or writable storage apparently available on running AVD. Unable to write even from adb. #102
Comments
Thanks for the thorough investigation! I was able to reproduce the issue on API 30 but was able to get it to work on API 23. So I went on to test all API levels from 23 to 30 ( Could you test with API 26-29 with I also found out that with API 29 I'll try to take another look at this next week. |
Annoyingly, I need the |
Adding this here in case someone runs into the same issue. We ran into the same problem for our instrumented tests where we needed to pull some data off external storage after tests complete, but the directory was unreadable on API 30+ devices. Turns out, the solution was that we needed to restart ADB as root before running our tests. See our workflow for a sample of what we did. This could be something that is made a part of the GitHub action runner itself for devices API 30+ instead of us needing to do it in our tests. |
…ndroid-emulator-runner#102 (comment) - also uses emulated directory instead of sdcard
…ndroid-emulator-runner#102 (comment) - also uses emulated directory instead of sdcard
Closing per workaround here -> #102 (comment) |
I've got an issue that seems similar to #56 but with some extra complication. I'm trying to kick off a screenrecord via
adb
before I run a gradle task, and then kill it once the task is done. My workflow is:However, I get an error here:
Unable to open '/storage/emulated/0/capture.mpg': No such file or directory
. Putting someadb
commands in the scrip to find out what the filesystem of the device looks like, I see:So
/sdcard
points at/storage/self/primary
which doesn't exist./storage/emulated/0
exists but is empty, andadb
itself can't write to it.This contrasts with a device created locally with the same
avdmanager
commands (avdmanager create avd --force -n test --abi google_apis/x86 --package system-images;android-30;google_apis;x86 --device pixel_3a
andemulator -avd test -no-window -gpu swiftshader_indirect -no-snapshot -noaudio -no-boot-anim
). In this case/storage/self/primary
exists, is a symlink to/storage/emulated/0
and contains what you'd expect:The text was updated successfully, but these errors were encountered: