-
Notifications
You must be signed in to change notification settings - Fork 24.1k
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
Android emulator is not opening in automatically, but manually it is opening . #43320
Comments
|
I tried to run it in "react-native": "0.73.5" but issue is still same |
Related to react-native-community/cli#1801 This is an issue related to your local setup. Perhaps your Android SDK is not properly installed. I'd suggest you start the emulator from Android Studio and check if it fixes. |
facing the same issue and tried with the latest version react-native@0.73.5 but still the issue persists. |
@Logeshpandij try this solution this is working for me. in both Linux and Windows |
By running yarn start I am also facing the same issue. I came to realize that issue is causing Android Studio after the new version Iguana. Open android studio run emulator from there and start your project. |
@OlekMuzyka Yes,It's working good by opening the emulator manually.But it needs to open automatically while running react-native run-android |
It seems the latest version of the emulator somehow is storing crash data and outputing it in the
So it seems someone on the Android team shipped leaky code. This also affects apps like MiniSim (@okwasniewski): As it seems everybody parses the list and just takes the first line as a valid emulator name. Some people have solved it on Windows by installing an older version of the emulator runtime. Issue. Another solution would be to modify the RN scripts so that they avoid log output lines. |
Spent a few days figuring this out and was finally able to resolve it. Thought I'd post it here to help someone out. You can fix this by following the steps at https://developer.android.com/studio/emulator_archive and downgrating the emulator to version 33.1.24 Stable. It's an Android issue caused by recent emulator versions, not from Expo or React NativeDirect links (v33.1.24 stable) from that page:windows_x64 Steps: |
Downgrading emulator version works |
ok, but where need to install this after download for mac? |
where need to install this after download for mac? (Android Emulator (33.1.24) Stable) maybe in android studio downgrade this?? |
Hii @moroshandmitry , you need to overwrite the emulator folder in |
@moroshandmitry Follow the steps step by step on the Android Studio website. I did it on Mac and Windows and it worked for me |
这个方法很好用,下载这个压缩包之后,把压缩包解压到你的 \android\sdk 目录里,替换掉原来的emulator文件夹,然后重启电脑就可以了。👍👍👍 This method is very easy to use, after downloading this package, extract the package into your \android\sdk directory, replace the original emulator folder, and then restart the computer.👍👍👍 |
good! |
Proper procedure is provided under emulator download section documentation
…On Sat, Mar 30, 2024, 9:34 PM bbf ***@***.***> wrote:
emulator 33.1.24 links
https://redirector.gvt1.com/edgedl/android/repository/emulator-windows_x64-11237101.zip
https://redirector.gvt1.com/edgedl/android/repository/emulator-darwin_x64-11237101.zip
https://redirector.gvt1.com/edgedl/android/repository/emulator-darwin_aarch64-11237101.zip
https://redirector.gvt1.com/edgedl/android/repository/emulator-linux_x64-11237101.zip
ok, but where need to install this after download for mac?
这个方法很好用,下载这个压缩包之后,把压缩包解压到你的 \android\sdk
目录里,替换掉原来的emulator文件夹,然后重启电脑就可以了。👍👍👍
This method is very easy to use, after downloading this package, extract
the package into your \android\sdk directory, replace the original emulator
folder, and then restart the computer.👍👍👍
good!
—
Reply to this email directly, view it on GitHub
<#43320 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATFL3MKAF7JM2UT2TQEC2ULY23PATAVCNFSM6AAAAABEGWFWACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRYGE4DGMRRGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
It looks like this change made it through stable builds and I'm not sure if they plan to revert it. Would it make sense to ignore the "INFO | Storing crashdata line" while parsing stdout in order to get the default emulator device? |
This works for me, thanks!!!! |
Description
Whenever I am running
npx react-native run-android
metro is failing to start the emulator and giving ->error Failed to launch emulator. Reason: The emulator (INFO | Storing crashdata in: C:\Users\arunk\AppData\Local\Temp\AndroidEmulator\emu-crash-34.1.18.db, detection is enabled for process: 404) quit before it finished opening. You can try starting the emulator manually from the terminal with: C:\Users\arunk\AppData\Local\Android\Sdk/emulator/emulator @INFO | Storing crashdata in: C:\Users\arunk\AppData\Local\Temp\AndroidEmulator\emu-crash-34.1.18.db, detection is enabled for process: 404.
and
FAILURE: Build failed with an exception.
Execution failed for task ':app:installDebug'.
I tried to delete emulator and again create and run but still failing ,
I tried to check for emulator
./emulator -list-avds
INFO | Storing crashdata in: C:\Users\arunk\AppData\Local\Temp\AndroidEmulator\emu-crash-34.1.18.db, detection is enabled for process: 12144
Pixel_6_API_34
Steps to reproduce
React Native Version
0.73.4
Affected Platforms
Runtime - Android, Build - Windows, Build - Linux
Output of
npx react-native info
Stacktrace or Logs
Reproducer
https://github.com/codewitharun/reporoduceError
Screenshots and Videos
The text was updated successfully, but these errors were encountered: