Android CLI fails to launch emulator automatically when running `yarn android` #1801

UNIDY2002 · 2023-01-19T02:14:04Z

Environment

System:
    OS: Linux 5.15 Manjaro Linux
    CPU: (16) x64 AMD Ryzen 7 5800H with Radeon Graphics
    Memory: 2.64 GB / 13.51 GB
    Shell: 3.5.1 - /usr/bin/fish
  Binaries:
    Node: 19.2.0 - /usr/bin/node
    Yarn: 1.22.19 - /usr/bin/yarn
    npm: 8.19.2 - /usr/bin/npm
    Watchman: Not Found
  SDKs:
    Android SDK: Not Found
  IDEs:
    Android Studio: Not Found
  Languages:
    Java: 19.0.1 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.2.0 => 18.2.0 
    react-native: 0.71.0 => 0.71.0 
  npmGlobalPackages:
    *react-native*: Not Found

Additional information:

Android SDK version 33.0.0
Android emulator version 31.2.8.0
CLI version 10.0.0

Description

After I execute yarn android, it prints an error message:

error Failed to launch emulator. Reason: The emulator (Pixel_4_API_30) quit before it finished opening. You can try starting the emulator manually from the terminal with: /home/unidy/.sdk/Android/emulator/emulator @Pixel_4_API_30.

I suspect there is something to do with this line: https://github.com/react-native-community/cli/blob/d351048/packages/cli-platform-android/src/commands/runAndroid/tryLaunchEmulator.ts#L27

When port is undefined, the subprocess parameters fall back to [`@${emulatorName}`, '', ''], and the empty strings may be the cause of the problem.

I think it is a regression, because it worked fine before I upgraded react-native to 0.71.

Reproducible Demo

Suggestion for a fix

Change this line: https://github.com/react-native-community/cli/blob/d351048/packages/cli-platform-android/src/commands/runAndroid/tryLaunchEmulator.ts#L27
into:

port ? [`@${emulatorName}`, '-port', `${port}`] : [`@${emulatorName}`]

The text was updated successfully, but these errors were encountered:

adamTrz · 2023-01-19T08:47:29Z

Hi @UNIDY2002 thanks for reporting! Fix is on the way :)

koralgooll · 2023-11-25T17:08:00Z

In my case the problem was not turned on virtualization in BIOS. So the expo probably was not able to start virtual Pixel device. You can check in Android Virtual Device Manager if you can run it.

LabGecko · 2024-02-23T21:17:21Z

Still seeing this error. Same basic error to the original poster.

System:
OS: Windows 11 Pro
CPU: AMD Ryzen 7 7735HS with Radeon Graphics 3.20 GHz
Memory: 32.0 GB (27.7 GB usable)
Binaries:
Node: 19.2.0 - /usr/bin/node
Yarn: 1.22.19 - /usr/bin/yarn
npm: 8.19.2 - /usr/bin/npm
SDKs: Android SDK: Android 14 (API 34)
IDEs: Android Studio: Hedgehog 2023.1.1 Patch 2 (Build #AI-231.9392.1.2311.11330709)
Languages: Java: 17
npmPackages:
yarn
cli

Note: Starting the emulator in Android Studio gets past this, but just wanted to report that the script to start is still encountering errors.

codewitharun · 2024-03-06T10:43:54Z

Got 2 solutions from here and here it is working.

1st solution

This bug came from the command line emulator -list-avds

Now this command line add a new log at the first line :

INFO    | Storing crashdata in: /tmp/android-xxx/emu-crash-34.1.18.db, detection is enabled for process: 20206
.Pixel_2_API_31
2.7_QVGA_API_31
3.2_QVGA_ADP2_API_31
3.7_WVGA_Nexus_One_API_31
6.7_Horizontal_Fold-in_API_31
Pixel_2_API_29
Pixel_2_API_33
Pixel_XL_API_31

The problem is that react-native take always the first emulator in this list as default emulator to launch. But now it try to open INFO | Storing crashdata in: /tmp/android-matthias/emu-crash-34.1.18.db, detection is enabled for process: 20206 that is not a emulator name, but just a log info.

To launch the emulator, until a fix, you can still use the command line

emulator @name_of_device

then use the common command :

npm run android

** 2nd solution**

Download Android Emulator (version 33.1.24) Stable from Android Emulator Archive.
Overwrite the existing emulator folder in ~/Library/Android/sdk with the downloaded version.
Run emulator -list-avd manually, confirm the macOS permissions in System Preferences, and then run it a second time to see the INFO log line gone.
If for some reason this doesn't work, consider reverting to an older Stable release from the Android Emulator Archive.

This should help in resolving the emulator crashing issue on Android Studio.

Mynameisjohndev · 2024-03-15T10:00:23Z

The download links don't appear, I've already tested it on 4 browsers and nothing. If you can view it, please provide the links to all platforms here.

AYASOFT · 2024-03-25T15:46:19Z

@Mynameisjohndev here are the direct links as shown on page
Zip files
Windows (64-bit): emulator-windows_x64-11237101.zip (361338481 bytes)
Mac (Intel): emulator-darwin_x64-11237101.zip (317369570 bytes)
Mac (Apple Silicon): emulator-darwin_aarch64-11237101.zip (267679962 bytes)
Linux: emulator-linux_x64-11237101.zip (247516525 bytes)

SHA-256 Checksums
4f21ad916568459a4e38d75755a5cf27c658b844673388e2bfe0f407ae3e8bb9 emulator-windows_x64-11237101.zip
c603ec70071d215f0351fc14ede329504af1608091918dd6804353ac9a9e66e3 emulator-darwin_x64-11237101.zip
8322f2a738cc29eaff26e9de856755ed5a1273d770e01d8347f0d84c8a487696 emulator-darwin_aarch64-11237101.zip
cfd54ce620ad5f9f786682ecad88b8b9da7ac48827d57406cc2a31bb8f6e73fe emulator-linux_x64-11237101.zip

kadirmetin · 2024-03-26T12:20:24Z

This error still persists on my computer. Is this the case for all users?

AYASOFT · 2024-03-27T19:49:39Z

@kadirmetin did you try the solution of @codewitharun
try downloading the previous stable version & replace files after a full restart of the machine.

haris-dev-72 · 2024-03-31T11:14:42Z

This error still persists on my computer. Is this the case for all users?

did you found any solution ???

kadirmetin · 2024-03-31T14:23:04Z

This error still persists on my computer. Is this the case for all users?

did you found any solution ???

No. The only solution I found was to run the application in the console after running the emulator. But in the past, when I ran the application through the console, it worked in the emulator.

GNUGradyn · 2024-05-25T15:13:20Z

Couldn't this utility just be fixed to ignore lines that start with INFO when parsing the emulator output..?

LabGecko · 2024-06-03T16:27:05Z

The error is now only appearing occasionally for me using VSCode. No idea what is causing the intermittency.

VSCode Version: 1.89.1 (user setup)
Commit: dc96b837cf6bb4af9cd736aa3af08cf8279f7685
Date: 2024-05-07
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Windows 11 Pro x64 ver 23H2 (misreports as Windows_NT x64 10.0.22631 so not sure what other values might be misreporting)

waohwaohwaoh · 2024-09-27T04:03:17Z

You can fix this by changing the logic of the getEmulators function in the file node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/tryLaunchEmulator.js
you need changed this line:
return emulatorsOutput.split(_os().default.EOL).filter(name => name !== '');
to:
return emulatorsOutput.split(_os().default.EOL).filter(name => !name.startsWith('INFO') && name !== '');

Luiyit · 2024-10-11T12:36:23Z

emulatorsOutput.split(

Is a simple way to solve it. Thanks!

UNIDY2002 added the bug report label Jan 19, 2023

adamTrz mentioned this issue Jan 19, 2023

fix: correctly exec launchEmulator when no port param is passed #1802

Merged

TMisiukiewicz mentioned this issue Jan 19, 2023

fix: launch android emulator when using run-android command #1803

Closed

thymikee closed this as completed in #1802 Jan 19, 2023

cortinico mentioned this issue Mar 5, 2024

Android emulator is not opening in automatically, but manually it is opening . facebook/react-native#43320

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Android CLI fails to launch emulator automatically when running `yarn android` #1801

Android CLI fails to launch emulator automatically when running `yarn android` #1801

UNIDY2002 commented Jan 19, 2023

adamTrz commented Jan 19, 2023

koralgooll commented Nov 25, 2023 •

edited

Loading

LabGecko commented Feb 23, 2024 •

edited

Loading

codewitharun commented Mar 6, 2024 •

edited

Loading

Mynameisjohndev commented Mar 15, 2024

AYASOFT commented Mar 25, 2024

kadirmetin commented Mar 26, 2024

AYASOFT commented Mar 27, 2024

haris-dev-72 commented Mar 31, 2024

kadirmetin commented Mar 31, 2024

GNUGradyn commented May 25, 2024

LabGecko commented Jun 3, 2024

waohwaohwaoh commented Sep 27, 2024

Luiyit commented Oct 11, 2024

Android CLI fails to launch emulator automatically when running yarn android #1801

Android CLI fails to launch emulator automatically when running yarn android #1801

Comments

UNIDY2002 commented Jan 19, 2023

Environment

Description

Reproducible Demo

Suggestion for a fix

adamTrz commented Jan 19, 2023

koralgooll commented Nov 25, 2023 • edited Loading

LabGecko commented Feb 23, 2024 • edited Loading

codewitharun commented Mar 6, 2024 • edited Loading

Mynameisjohndev commented Mar 15, 2024

AYASOFT commented Mar 25, 2024

kadirmetin commented Mar 26, 2024

AYASOFT commented Mar 27, 2024

haris-dev-72 commented Mar 31, 2024

kadirmetin commented Mar 31, 2024

GNUGradyn commented May 25, 2024

LabGecko commented Jun 3, 2024

waohwaohwaoh commented Sep 27, 2024

Luiyit commented Oct 11, 2024

Android CLI fails to launch emulator automatically when running `yarn android` #1801

Android CLI fails to launch emulator automatically when running `yarn android` #1801

koralgooll commented Nov 25, 2023 •

edited

Loading

LabGecko commented Feb 23, 2024 •

edited

Loading

codewitharun commented Mar 6, 2024 •

edited

Loading