Closed
Description
Summary
On Windows 10, Expo tries to pick up Android Emulator Info as an AVD device.
This is what happens when I try to run:android
PS C:\Users\Atif\Desktop\voyago\infra\client> npx expo run:android
env: load .env
env: export API_URL
› Opening emulator INFO | Storing crashdata in: C:\Users\Atif\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.18.db, detection is enabled for process: 2512
Error: The emulator (INFO | Storing crashdata in: C:\Users\Atif\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.18.db, detection is enabled for process: 2512) quit before it finished opening. You can try starting the emulator manually from the terminal with: C:\Users\Atif\AppData\Local\Android\Sdk/emulator/emulator @INFO | Storing crashdata
in: C:\Users\Atif\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.18.db, detection is enabled for process: 2512
Error: The emulator (INFO | Storing crashdata in: C:\Users\Atif\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.18.db, detection is enabled for process: 2512) quit before it finished opening. You can try starting the emulator manually from the terminal with: C:\Users\Atif\AppData\Local\Android\Sdk/emulator/emulator @INFO | Storing crashdata
in: C:\Users\Atif\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.18.db, detection is enabled for process: 2512
at stopWaitingAndReject (C:\Users\Atif\Desktop\voyago\infra\client\node_modules\@expo\cli\build\src\start\platforms\android\emulator.js:110:20)
at ChildProcess.<anonymous> (C:\Users\Atif\Desktop\voyago\infra\client\node_modules\@expo\cli\build\src\start\platforms\android\emulator.js:121:13)
at ChildProcess.emit (node:events:518:28)
at ChildProcess._handle.onexit (node:internal/child_process:294:12)
This is what happens when I try to pick an android device
PS C:\Users\Atif\Desktop\voyago\infra\client> npx expo run:android -d
env: load .env
env: export API_URL
? Select a device/emulator »
> INFO | Storing crashdata in: C:\Users\Atif\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.18.db, detection is enabled for process: 6428 (emulator)
Medium_Phone_API_33 (emulator)
Here is the output from my list avd command
C:\Users\Atif\AppData\Local\Android\Sdk\emulator>emulator.exe -list-avds
INFO | Storing crashdata in: C:\Users\Atif\AppData\Local\Temp\\AndroidEmulator\emu-crash-34.1.18.db, detection is enabled for process: 18092
Medium_Phone_API_33
It looks like expo is picking up an INFO message as a valid device. This error only started 2 days ago, so I'm not sure if that INFO message showed up previously or did it only start appearing in a new version of Android Emulator
What platform(s) does this occur on?
Android
SDK Version
50
Environment
expo-env-info 1.2.0 environment info:
System:
OS: Windows 10 10.0.19045
Binaries:
Node: 20.11.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 10.3.0 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: AI-232.10227.8.2321.11479570
npmPackages:
@expo/webpack-config: ^19.0.0 => 19.0.1
expo: ~50.0.8 => 50.0.8
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.73.4 => 0.73.4
react-native-web: ~0.19.6 => 0.19.10
Expo Workflow: bare
Minimal reproducible example
Hard to reproduce because it could be related to my own PC with a simple npx run:android command. I shared all the details in the summary above.