Emulator 30.7.4 Crashes on launch with Symbol not found: _preadv [191805460]

Fixed

Bug

Status Update

No update yet.

Description

he...@gmail.com

created issue #1

Jun 22, 2021 10:05PM

Running the emulator from the terminal crashes with the following error:

dyld: lazy symbol binding failed: Symbol not found: _preadv
  Referenced from: /Users/bordersh/Library/Android/sdk/emulator/qemu/darwin-x86_64/qemu-system-x86_64
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _preadv
  Referenced from: /Users/bordersh/Library/Android/sdk/emulator/qemu/darwin-x86_64/qemu-system-x86_64
  Expected in: /usr/lib/libSystem.B.dylib

Running the emulator from the AVD Manager in Android Studio crashes and shows an alert dialog:

AVD Manager

The emulator process for AVD Pixel_3a_API_30 was killed.

Studio Build: Version of Java:

$ java --version
openjdk 11.0.8 2020-07-14
OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
OpenJDK 64-Bit Server VM (build 11.0.8+10-b944.6916264, mixed mode)

OS: macOS 10.15.7 Catalina

Steps to Reproduce:

$ /Users/bordersh/Library/Android/sdk/emulator/emulator -avd Pixel_3a_API_30
emulator: Android emulator version 30.7.4.0 (build_id 7453540) (CL:N/A)
handleCpuAcceleration: feature check for hvf
cannot add library /Users/bordersh/Library/Android/sdk/emulator/qemu/darwin-x86_64/lib64/vulkan/libvulkan.dylib: failed
added library /Users/bordersh/Library/Android/sdk/emulator/lib64/vulkan/libvulkan.dylib
cannot add library /Users/bordersh/Library/Android/sdk/emulator/qemu/darwin-x86_64/lib64/vulkan/libMoltenVK.dylib: failed
added library /Users/bordersh/Library/Android/sdk/emulator/lib64/vulkan/libMoltenVK.dylib
emulator: INFO: GrpcServices.cpp:315: Started GRPC server at 127.0.0.1:8554, security: Local
emulator: INFO: EmulatorAdvertisement.cpp:93: Advertising in: /Users/bordersh/Library/Caches/TemporaryItems/avd/running/pid_74735.ini
dyld: lazy symbol binding failed: Symbol not found: _preadv
  Referenced from: /Users/bordersh/Library/Android/sdk/emulator/qemu/darwin-x86_64/qemu-system-x86_64
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _preadv
  Referenced from: /Users/bordersh/Library/Android/sdk/emulator/qemu/darwin-x86_64/qemu-system-x86_64
  Expected in: /usr/lib/libSystem.B.dylib

Comments

[Deleted User] <[Deleted User]> #2Jun 22, 2021 10:26PM

Connie, do you think we can just remove it? And recommend ModalBottomSheet or BottomSheetScaffold instead?

Message last modified on Jun 22, 2021 10:27PM

pe...@bitrise.io <pe...@bitrise.io> #3Jun 22, 2021 10:38PM

José, is there any functionality in bottom drawer (https://m2.material.io/components/navigation-drawer#modal-drawer) that is not supposed by modalBottomsheet?

an...@gmail.com <an...@gmail.com> #4Jun 23, 2021 02:03AM

I think it's worth noting in M2 that ModalBottomSheet is a layout while bottomdrawer functions more as a truly modal object, even though it does not have perfect dialog-like functionality. For the usecase recommended (bottom app bar menus), BottomDrawer seems like a better fit than ModalBottomSheetLayout. However in M3 it makes sense to explicitly use ModalBottomSheet once implemented.

Wdyt Matvei?

Message last modified on Jun 23, 2021 02:03AM

he...@gmail.com <he...@gmail.com> #5Jun 23, 2021 04:13AM

I think it's worth noting in M2 that ModalBottomSheet is a layout while bottomdrawer functions more as a truly modal object

Could you comment on that? What's the actual difference in the behaviour?

mm...@gmail.com <mm...@gmail.com> #6Jun 23, 2021 09:17AM

Bottom Drawer is an atomic component that can be placed on top of content on the screen while ModalBottomSheet is a layout that wraps around all the screen content and places accordingly. BottomDrawer is much more of a splashable component in M2 and asking users to migrate BottomDrawer uses may be cumbersome.

Message last modified on Jun 23, 2021 09:17AM

go...@gmail.com <go...@gmail.com> #7Jun 23, 2021 09:49AM

Ok, sounds good. I'm happy to keep it if you think it brings value to m2 users.

If we are not removing it, we need to make it stable in this case.

ra...@gmail.com <ra...@gmail.com> #8Jun 23, 2021 12:11PM

Found some outstanding bugs I will look into before deciding to promote, especially the swipeable migrations which will likely update the API

f....@hiconnect.de <f....@hiconnect.de> #9Jun 23, 2021 01:54PM

Given the planned work to migrate the swipeable logic of bottomdrawer, this API should remain experimental. Closing for now.

ab...@gmail.com <ab...@gmail.com> #10Jun 23, 2021 01:56PM

If these are still experimental, please keep this bug open and just target the next release

jp...@spotify.com <jp...@spotify.com> #11Jun 23, 2021 05:49PM

Where can i find the respective hotlist for the next release?

Message last modified on Jun 23, 2021 08:40PM

[Deleted User] <[Deleted User]> #12Jun 23, 2021 06:41PM

Fwiw the major difference between modal sheets and bottom drawer is that the drawer can be opened by swiping on the full container. If we don't intend to introduce a bottom drawer in M3, maybe we can explore how to adapt the ModalBottomSheet API for this feature in the future.

da...@gmail.com <da...@gmail.com> #13Jun 23, 2021 06:50PM

Bumping to P1 as it is been a long while since we need to land this.

[Deleted User] <[Deleted User]> #14Jun 23, 2021 08:53PM

This is an out-of-SLO bug that is assigned to me. Moving to Matvei to ensure that it is looked at.

Message last modified on Jun 23, 2021 08:53PM

pa...@wagwalking.com <pa...@wagwalking.com> #15Jun 23, 2021 11:16PM

Jossi is on it already.

pa...@wagwalking.com <pa...@wagwalking.com> #16Jun 23, 2021 11:17PM

Project: platform/frameworks/support
Branch: androidx-main

commit 63b8ceee3645b3d78a2c372f01390937bf14c8bd
Author: Jossi Wolf <jossiwolf@google.com>
Date: Wed Nov 29 15:17:04 2023

[M2] Stabilize BottomDrawer

Relnote: BottomDrawer has been promoted from experimental to stable. BottomDrawerState now exposes the progress as a function, allowing to query progress between specific targets. BottomDrawerState now allows customizing the animation spec, and confirmStateChange is not a trailing lambda anymore.
Fixes: 261423850
Test: Existing tests, bottomDrawer_progress
Change-Id: I9c029340ea69a755ad0cd8f46b8fcdc76422c41c

M compose/material/material/api/current.txt
M compose/material/material/api/restricted_current.txt
M compose/material/material/src/androidInstrumentedTest/kotlin/androidx/compose/material/DrawerTest.kt
M compose/material/material/src/commonMain/kotlin/androidx/compose/material/Drawer.kt

https://android-review.googlesource.com/2852686

ge...@freddiemac.com <ge...@freddiemac.com> #17Jun 23, 2021 11:23PM

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.compose.material:material:1.7.0-alpha03
androidx.compose.material:material-android:1.7.0-alpha03
androidx.compose.material:material-desktop:1.7.0-alpha03

go...@gmail.com <go...@gmail.com> #18Jun 24, 2021 04:34AM

I solved the issue by this way #10;; thank you very much;

I installed the another emulator version (https://dl.google.com/android/repository/emulator-darwin_x64-7324830.zip); It is works fine for me;

ch...@gmail.com <ch...@gmail.com> #19Jun 24, 2021 07:09AM

Solved by old emulator -

https://dl.google.com/android/repository/emulator-darwin_x64-7140946.zip
Download and replace it

[Deleted User] <[Deleted User]> #20Jun 24, 2021 07:21AM

This is really an annoying problem!!!

ra...@gmail.com <ra...@gmail.com> #21Jun 24, 2021 08:11AM

I cant replace the emulator manually because I don't have admin permission. I hope a fix update a soon as possible

dn...@gmail.com <dn...@gmail.com> #22Jun 24, 2021 08:54AM

Please, suggest, how do I replace the emulator with the old one? I have deleted the emulator folder from SDK folder and replaced it with downloaded one and restarted AS. Studio still detects the emulator version as 30.7.4 and it keeps crashing.

qm...@gmail.com <qm...@gmail.com> #23Jun 24, 2021 09:00AM

#22

Install faulty version properly
Close Android Studio
Download and unzip an older version provided above
Replace files in $ANDROID_HOME/emulator
Launch Android Studio and it will use the new files

dn...@gmail.com <dn...@gmail.com> #24Jun 24, 2021 09:22AM

#23
Appreciate your help. Worked.

Message last modified on Jun 24, 2021 09:22AM

an...@gmail.com <an...@gmail.com> #25Jun 24, 2021 09:23AM

#22 #23
Just making it more clear. Don't remove any files inside the emulator folder. Replace files one by one. Read the link in #10 again.

ab...@gmail.com <ab...@gmail.com> #26Jun 24, 2021 09:24AM

#22
You need to replace the content on /emulator folder instead of deleting that folder.
The important point is that you need to keep 'package.xml' file because that is the file Android Studio uses to run the emulator (and isn't presente in the emulator .zip you downloaded).
Take a look at the article I posted above (

https://medium.com/nerd-for-tech/how-to-downgrade-android-emulator-on-macos-6e611d2d2bcb)

ju...@gmail.com <ju...@gmail.com> #27Jun 24, 2021 11:43AM

After I replaced /emulator folder, I am getting following error while running emulator:

“emulator-check” can’t be opened because Apple cannot check it for malicious software.

ko...@gmail.com <ko...@gmail.com> #28Jun 24, 2021 11:53AM

Hello, ju...@gmail.com! I experienced the same exact thing and found quick workaround. If you have windows pc near (idk if Linux will work, but most likely yes) download the archive there and then copy it to your Mac.

This is to make your Mac think, that those files aren’t downloaded from somewhere and are just usual files found on your drive. That worked for me and omg finally I can go back to work...

So yeah, huge thanks to #10

Also, if it isn’t possible, try not clicking that link to download files, but copy-paste the link to your browser. I hope it will make Mac think that this is a google download and consider it safe (but I’m not sure about that)

ra...@gmail.com <ra...@gmail.com> #29Jun 24, 2021 12:24PM

thank you #28 by the trick of windows, work fine

BTW this is the previous version of emulator 30.7.3 https://dl.google.com/android/repository/emulator-darwin_x64-7425822.zip

ab...@gmail.com <ab...@gmail.com> #30Jun 24, 2021 12:37PM

#27
You have to open 'Security & Privacy' window from System Preferences.
After trying to open a 'not-trusted' app, you will see a message and a button to allow the system execute that app.
Next time you'll open the emulator, you'll get an alert with an 'Open' button as one of its options.
The emulator runs several executables when running, so you'll probably have to repeat this process a number of times.

Fu...@n11.com <Fu...@n11.com> #31Jun 24, 2021 12:54PM

After replace still show 'qemu-system-x86_64 cannot be opened because the developer cannot be verified.' error.

ju...@gmail.com <ju...@gmail.com> #32Jun 24, 2021 01:22PM

Unfortunately, I don't have windows machine to do this workaround, May be I should wait for next update from Google.

al...@gmail.com <al...@gmail.com> #33Jun 24, 2021 01:25PM

#32 try to download it through direct link

https://dl.google.com/android/repository/emulator-darwin_x64-7140946.zip

Or try to download it via mobile phone / tablet and then copy to your Mac

kh...@googlemail.com <kh...@googlemail.com> #34Jun 24, 2021 01:33PM

Same problem here on Catalina. A few points here

Not everybody can upgrade the system to Big Sur (I am sure plenty of us run build nodes or similar purpose Macs on the old 2012 MacMinis)
In my case I just wiped out the emulator directory and replaced it with the contents of the older 30.6.5 version
It's quite difficult to comprehend how an update with a bug like that can be released without checking if it works on the Catalina

kk...@gmail.com <kk...@gmail.com> #35Jun 24, 2021 02:24PM

I solved the issue by this way #10 thank you very much;
thanks a million, managed to solve the issue.
i am on Mojave MAC.

i have tried the options that was suggested in forum none worked for me.. i guess the suggestion as per the comment on #10 is the best solution.

Message last modified on Jun 24, 2021 02:25PM

ju...@gmail.com <ju...@gmail.com> #36Jun 24, 2021 02:37PM

I was also able to solve it , first by downloading zip in mobile and then transferring to my macbook. Thanks #33

Fu...@n11.com <Fu...@n11.com> #37Jun 24, 2021 02:55PM

In which way do you transfer with mobile?

pa...@nearside.com <pa...@nearside.com> #38Jun 24, 2021 02:58PM

Hi can we please keep the discussion on-topic to the actual bug at-hand? If you have ancillary questions please take it to StackOverflow or a similar site.

[Deleted User] <[Deleted User]> #39Jun 24, 2021 04:12PM

FYI this unblocked me for the time being.

Download emulator 30.6.5 from here from your phone or another PC.

https://dl.google.com/android/repository/emulator-darwin_x64-7324830.zip
Copy it to your Mac with 'adb pull /sdcard/Download/emulator-darwin_x64-7324830.zip .'
Unzip
Run your emulator

da...@zup.com.br <da...@zup.com.br> #40Jun 24, 2021 07:11PM

#27 to avoid security checks, please run this command in emulator folder, to remove from quarantine list.

xattr -r -d com.apple.quarantine <emulator folder>

Thanks to https://apple.stackexchange.com/questions/337268/how-can-i-remove-the-downloaded-from-the-internet-security-from-all-files-in-a

lf...@google.com <lf...@google.com> #41Jun 24, 2021 10:36PM

Assigned to lf...@google.com.

Hi, sorry for the breakage. Fix is incoming.

va...@gmail.com <va...@gmail.com> #42Jun 25, 2021 04:05AM

Temp solution: Downgrade to 30.7.2
my instruction:

https://gist.github.com/0x0a0d/d3ce82f72e8f5681649b129d8a84e46b

co...@gmail.com <co...@gmail.com> #43Jun 25, 2021 07:15AM

Just to inform that the SDK Tools has been updated today : if you delete the emulator using the SDK Tools, then open it again and you will see it has been replaced with the old 30.6.5 version.
The emulator is now working fine.

ar...@google.com <ar...@google.com> Jun 25, 2021 09:56PM

Reassigned to an...@google.com.

sh...@gmail.com <sh...@gmail.com> #44Jun 27, 2021 08:07AM

I can confirm new emulator (30.6.5) works on Mac Catalina

ya...@42gears.com <ya...@42gears.com> #45Jun 28, 2021 08:55AM

Is there any way to still use Android 12 without Emulator 30.7.4?

be...@troii.com <be...@troii.com> #46Jun 28, 2021 09:01AM

#45 as mentioned in

https://issuetracker.google.com/issues/191805460#comment43 you can uninstall the Emulator in SDK Manager, restart Android Studio and when installing Emulator again the old 30.6.5 is installed instead. Works for me on Catalina again.

ma...@gmail.com <ma...@gmail.com> #47Jun 28, 2021 03:31PM

#46 works. Thank you.

lf...@google.com <lf...@google.com> #48Jun 28, 2021 04:44PM

Reassigned to lf...@google.com.

Hi, thanks for the report; we're working on a fix. In the meantime, try uninstalling and reinstalling the emulator, which should restore an older or working version.

ar...@gmail.com <ar...@gmail.com> #49Jun 28, 2021 05:56PM

Thanks for the heads up. Uninstalled and reinstalled. The version installed is 30.6.5 and verified that it's working again.

Message last modified on Jun 28, 2021 05:58PM

cw...@gmail.com <cw...@gmail.com> #50Jun 29, 2021 09:52PM

For anyone else wondering, no the Android 12 Emulator doesn't work with the emulator version 30.6.5 and Mac OS Catalina as you run into this issue:

https://issuetracker.google.com/issues/190923231

qm...@gmail.com <qm...@gmail.com> #51Jul 2, 2021 06:50AM

New release 30.7.5 fixes all our issues. You can get the latest version now.

ma...@gmail.com <ma...@gmail.com> #52Jul 6, 2021 04:59PM

Verified 30.7.5 working. Thank you Google for fixing this.

tr...@redfin.com <tr...@redfin.com> #53Jul 9, 2021 04:25PM

This fixes the problem we previously had on macOS Catalina with Android S beta 3 (including network connectivity).

sp...@google.com <sp...@google.com> #54Feb 4, 2022 04:30AM

Marked as fixed.

Is the problem still reproducible with emulator 31.2.7?