Emulator 30.5.3.0 Won't Start on Mac Mojave [183218284]

Obsolete

Bug

Status Update

No update yet.

Description

je...@gmail.com

created issue #1

Mar 20, 2021 08:51PM

IMPORTANT: Please read https://developer.android.com/studio/report-bugs.html carefully and supply all required information.

Studio Build: any Version of Gradle Plugin: Version of Gradle: Version of Java: OS: macOS Mojave 10.14.6

Steps to Reproduce:

Install any version of Android Studio
Install the only emulator available in the SDK manager (30.5.3.0)
Create an AVD using any system image.
Start the AVD. Most likely no warnings will be emitted in the GUI, so attempt to start from the console.

Error Message:

The Android emulator exited with code -6 during startup
Android emulator stderr:
dyld: Library not loaded: 
/System/Library/Frameworks/IOUSBHost.framework/Versions/A/IOUSBHost
  Referenced from: /Volumes/Jeff/Library/Android/sdk/emulator/qemu/darwin-x86_64/qemu- system-x86_64
  Reason: image not found
Address these issues and try again.

Comments

co...@gmail.com <co...@gmail.com> #2Mar 20, 2021 10:27PM

I have updated AS to version 4.1.3 and the android emulator to version 30.5.3.0. Now I can't use the emulator anymore. I have Mojave OS installed and I confirm the same message described in previous post. The file does not exist in the file system.

je...@gmail.com <je...@gmail.com> #3Mar 20, 2021 10:47PM

As a workaround, I was able to successfully downgrade android emulator to 28.

See: https://stackoverflow.com/questions/49120854/how-to-downgrade-android-emulator

I downloaded 28.0.25.0 (build_id 5395263) from here:

https://dl.google.com/android/repository/emulator-darwin-5395263.zip

I deleted everything EXCEPT package.xml from

$HOME/Library/Android/sdk/emulator/

and replaced them with the contents of the extracted zip file.

Finally, make sure your AVD system image is NOT running api 30.

sdkmanager "system-images;android-27;google_apis_playstore;x86"

System images higher than api 29 are using a kernel format that the older emulator cannot understand.

Here's a workaround script you can try:

cd ~
mkdir emulator_downgrade
cd emulator_downgrade
wget https://dl.google.com/android/repository/emulator-darwin-5395263.zip
unzip emulator-darwin-5395263.zip
mv ~/Library/Android/sdk/emulator ~/Library/Android/sdk/previous-emulator
mv emulator ~/Library/Android/sdk/emulator
cp ~/Library/Android/sdk/previous-emulator/package.xml 
~/Library/Android/sdk/emulator/package.xml
cd ~
~/Library/Android/sdk/emulator/emulator -version
~/Library/Android/sdk/emulator/emulator -list-avds

co...@gmail.com <co...@gmail.com> #4Mar 21, 2021 07:53AM

Thank you for the downgrade explanation. If you want to use a more recent emulator 30.1.5 the build number is 6855416. I believe you can use this build with API 30 images without issues.

pe...@gmail.com <pe...@gmail.com> #5Mar 21, 2021 10:58AM

I am facing the same issue. Can't run emulator after upgrading to version 30.5.3. My macOS is Mojave 10.14.6.

ji...@gmail.com <ji...@gmail.com> #6Mar 22, 2021 06:21AM

I am facing the same issue tooooo.
Can't run emulator after upgrading to version 30.5.3.
My macOS is 10.12.6

Message last modified on Mar 22, 2021 06:24AM

pe...@hostelworld.com <pe...@hostelworld.com> #7Mar 22, 2021 10:01AM

I have the same issue after upgrading the emulator to version 30.5.3 on my laptop with macOS Mojave 10.14.6 installed.

m6...@mschmitt.info <m6...@mschmitt.info> #8Mar 22, 2021 03:08PM

For 30.2.6 the build number is 6962233 and that one still works for me on Sierra. Hope this gets fixed/backported. I'm waiting for new MbPros to be released (hopefully without touchbar). Don't want to upgrade my old one to >= Catalina. https://dl.google.com/android/repository/emulator-darwin-6962233.zip

fr...@globant.com <fr...@globant.com> #9Mar 22, 2021 05:51PM

+1 same problem here

da...@google.com <da...@google.com> Mar 23, 2021 12:24AM

Assigned to an...@google.com.

au...@gmail.com <au...@gmail.com> #10Mar 23, 2021 02:12PM

Same problem
30.2.6 (build 6962233) in Mojave works for me

lf...@google.com <lf...@google.com> #11Mar 23, 2021 04:24PM

Reassigned to lf...@google.com.

Hi, thanks for the report. Can you try the emulator from https://ci.android.com/builds/submitted/7229563/sdk_tools_mac/latest/sdk-repo-darwin-emulator-7229563.zip ?

m6...@mschmitt.info <m6...@mschmitt.info> #12Mar 23, 2021 04:33PM

I can confirm that 7229563 works for me

gr...@wavelt.com <gr...@wavelt.com> #13Mar 23, 2021 04:33PM

Hi, thanks for the report. Can you try the emulator from https://ci.android.com/builds/submitted/7229563/sdk_tools_mac/latest/sdk-repo-darwin-emulator-7229563.zip ?

Another mojave user here with the problem. After replacing the emulator folder with the contents of the zip I can run the emulator again. Thanks.

je...@gmail.com <je...@gmail.com> #14Mar 23, 2021 05:05PM

It works-ish, but I still get some library failures on launch...

handleCpuAcceleration: feature check for hvf
cannot add library /Volumes/Jeff/Library/Android/sdk/emulator/qemu/darwin-x86_64/lib64/vulkan/libvulkan.dylib: failed
added library /Volumes/Jeff/Library/Android/sdk/emulator/lib64/vulkan/libvulkan.dylib
cannot add library /Volumes/Jeff/Library/Android/sdk/emulator/qemu/darwin-x86_64/lib64/vulkan/libMoltenVK.dylib: failed
added library /Volumes/Jeff/Library/Android/sdk/emulator/lib64/vulkan/libMoltenVK.dylib
emulator: INFO: GrpcServices.cpp:301: Started GRPC server at 127.0.0.1:8554, security: Local
emulator: emulator window was out of view and was recentered
emulator: INFO: QtLogger.cpp:68: Warning: Failed to get QCocoaScreen for NSObject(0x0) ((null):0, (null))

m6...@mschmitt.info <m6...@mschmitt.info> #15Mar 23, 2021 05:09PM

I remember seeing these warning messages on previous emulator binaries as well. But they seem harmless.

th...@gmail.com <th...@gmail.com> #16Mar 24, 2021 07:25AM

For me it is working again with the same error messages from

comment #14

. But I have to start from terminal, with AVD manager it does not start the emulator.

se...@gmail.com <se...@gmail.com> #17Mar 24, 2021 01:01PM

Had the same problem. It kept telling me that the AVD process was killed. The downgrade method worked for me.

da...@gmail.com <da...@gmail.com> #18Mar 24, 2021 11:11PM

No downgrade needed !!!

For those on Mojave or older OSX who do not want to upgrade OS or downgrade emulator, you can try my solution here: https://stackoverflow.com/questions/66722486/avd-emulator-killed-mac-nothing-works-solved-2021

Good Luck

Message last modified on Apr 8, 2021 01:56PM

vi...@gmail.com <vi...@gmail.com> #19Mar 25, 2021 05:43PM

I am using High Sierra OSx 10.13.6.

When I try to start the emulator using AVD, I get the following message "The emulator process for AVD Pixel_XL_API_30 was killed"

I am getting the following error on the command line since the emulator upgrade to 3.5.3.0

~/Library/Android/sdk/emulator/emulator -avd Pixel_XL_API_30 emulator: Android emulator version 30.5.3.0 (build_id 7196367) (CL:N/A) dyld: Library not loaded: /System/Library/Frameworks/IOUSBHost.framework/Versions/A/IOUSBHost Referenced from: /Users/user/Library/Android/sdk/emulator/qemu/darwin-x86_64/qemu-system-x86_64 Reason: image not found Abort trap: 6

[Deleted User] <[Deleted User]> #20Mar 26, 2021 05:44PM

I had the same issue, Mojave 10.14.4 (18E227), Emulator 30.5.3, and i lost many hours :/
Downgrade worked for me (emulator-darwin-6855416)
Thanks guys

va...@gmail.com <va...@gmail.com> #21Mar 28, 2021 11:35AM

The same problem.

li...@gmail.com <li...@gmail.com> #22Mar 31, 2021 07:48AM

Hi, thanks for the report. Can you try the emulator from https://ci.android.com/builds/submitted/7229563/sdk_tools_mac/latest/sdk-repo-darwin-emulator-7229563.zip ?

Hi. Emulator 30.6.1 (build 7229563) in Mojave works for me.

Message last modified on Mar 31, 2021 07:54AM

ar...@gmail.com <ar...@gmail.com> #23Mar 31, 2021 01:11PM

Hi,
Am using
mac OS - 10.14.6
Android Studio - 4.1.3
and facing same issue .

va...@gmail.com <va...@gmail.com> #24Apr 1, 2021 09:10PM

I have upgraded to new version of Android Emulator 30.5.4. It's ok, everything is works!
macOS: 10.14.6

ab...@gmail.com <ab...@gmail.com> #25Apr 7, 2021 01:05PM

After update to Android Emulator 30.5.4.0 the framework is no longer required. Google has probably fixed that.

I too faced this issue. After updating my Android Studio to 4.1.3, emulators stopped running.
I did everything possible to fix this. Found that for few people, upgrading their MacOS to big sur fixed it. I downloaded big-sur, but then while installing, it asked to free up 25GB from the device, which was not possible and hence could not install big-sur too.

Ultimately, after updating to Android Emulator 30.5.4.0, it fixed the issue. Did not need to do anything else. It seems google has fixed it in the latest Android Emulator release.

Message last modified on Apr 7, 2021 01:06PM

su...@gtempaccount.com <su...@gtempaccount.com> #26Jun 23, 2021 02:07PM

Thanks for your solution, Really saved my day.

Message last modified on Jun 23, 2021 02:07PM

is...@google.com <is...@google.com> Sep 20, 2022 08:21AM

Status: New

ja...@google.com <ja...@google.com> Mar 8, 2023 01:03AM

Status: Won't Fix (Obsolete)

de...@google.com <de...@google.com> Mar 8, 2023 01:37AM

Status: Won't Fix (Obsolete)

Issue 183218284

Description

Issue summary

Comments

co...@gmail.com <co...@gmail.com> #2Mar 20, 2021 10:27PM

je...@gmail.com <je...@gmail.com> #3Mar 20, 2021 10:47PM

co...@gmail.com <co...@gmail.com> #4Mar 21, 2021 07:53AM

pe...@gmail.com <pe...@gmail.com> #5Mar 21, 2021 10:58AM

ji...@gmail.com <ji...@gmail.com> #6Mar 22, 2021 06:21AM

pe...@hostelworld.com <pe...@hostelworld.com> #7Mar 22, 2021 10:01AM

m6...@mschmitt.info <m6...@mschmitt.info> #8Mar 22, 2021 03:08PM

fr...@globant.com <fr...@globant.com> #9Mar 22, 2021 05:51PM

da...@google.com <da...@google.com> Mar 23, 2021 12:24AM

au...@gmail.com <au...@gmail.com> #10Mar 23, 2021 02:12PM

lf...@google.com <lf...@google.com> #11Mar 23, 2021 04:24PM

m6...@mschmitt.info <m6...@mschmitt.info> #12Mar 23, 2021 04:33PM

gr...@wavelt.com <gr...@wavelt.com> #13Mar 23, 2021 04:33PM

je...@gmail.com <je...@gmail.com> #14Mar 23, 2021 05:05PM

m6...@mschmitt.info <m6...@mschmitt.info> #15Mar 23, 2021 05:09PM

th...@gmail.com <th...@gmail.com> #16Mar 24, 2021 07:25AM

se...@gmail.com <se...@gmail.com> #17Mar 24, 2021 01:01PM

da...@gmail.com <da...@gmail.com> #18Mar 24, 2021 11:11PM

vi...@gmail.com <vi...@gmail.com> #19Mar 25, 2021 05:43PM

[Deleted User] <[Deleted User]> #20Mar 26, 2021 05:44PM

va...@gmail.com <va...@gmail.com> #21Mar 28, 2021 11:35AM

li...@gmail.com <li...@gmail.com> #22Mar 31, 2021 07:48AM

ar...@gmail.com <ar...@gmail.com> #23Mar 31, 2021 01:11PM

va...@gmail.com <va...@gmail.com> #24Apr 1, 2021 09:10PM

ab...@gmail.com <ab...@gmail.com> #25Apr 7, 2021 01:05PM

su...@gtempaccount.com <su...@gtempaccount.com> #26Jun 23, 2021 02:07PM

is...@google.com <is...@google.com> Sep 20, 2022 08:21AM

ja...@google.com <ja...@google.com> Mar 8, 2023 01:03AM

de...@google.com <de...@google.com> Mar 8, 2023 01:37AM

Add comment

Issue metadata