$ANDROID_HOME/emulator/emulator-headless -no-boot-anim -netdelay none -no-snapshot -wipe-data -verbose -show-kernel -no-audio -gpu swiftshader_indirect -no-snapshot &> /tmp/log.txt & $ANDROID_HOME/tools/bin/sdkmanager -install 'system-images android-29 google_apis x86'Įcho 'no' | $ANDROID_HOME/tools/bin/avdmanager -verbose create avd -force -name 'pixel' -device 'pixel' -package 'system-images android-29 google_apis x86' -tag 'google_apis' -abi 'x86' $ANDROID_HOME/tools/bin/sdkmanager -install 'emulator' Sudo $ANDROID_HOME/tools/bin/sdkmanager -update I am updating this thread to include a script we’ve recently found to be successfully launching emulators: #!/usr/bin/env bash Warning: Failed to find package system-images android-26 google_apis armeabi-v7a Warning: File /Users/vagrant/.android/repositories.cfg could not be loaded. CustomCommandFlags: -no-window -no-audio -debug-initĮnsure sdk packages: įailed to update emulator sdk package, error: exit status 1, output: Loading package information. Sample build that failed: Log: INFO * Step dependency (go) installed, available. In case of x86 emualtors it fails due to HAXM requirements, but in case of ARM it’s unable to download dependencies. It fails both for x86 emulators as well as for ARM. Unfortunately step AVD Manager fails no matter what kind of emulator is chosen. I’m trying to run Android emulator on macOS Stack (Visual Studio for Mac, stable).
