Cordova android emulator stopped working
android, cordova, emulation
Solution
Just re run after starting emulator manually.
Create Emulator
- type `android` in cmd and hit enter, a GUI will come.
- Under tools section click “manage AVDs” and follow the further instruction to create a new AVD.
Start Emulator
- `emulator.exe -avd *avdname*` in cmd (wait for few minutes for full start up)
- now re run cordova. it will work.
Problem
I'm building an app for Android using Cordova. The android emulator was working fine but I wasn't using it because I installed the Ripple emulator. I continued on building my app, but somewhere the emulator got corrupted. When I execute the following: ``` cordova create test cordova platform add android cordova build cordova emulate ``` Results in the following error: ``` Error: An error occurred while emulating/deploying the android project. events.js:72 throw er; // Unhandled 'error' event ^ Error: spawn ENOENT at errnoException (child_process.js:980:11) at Process.ChildProcess._handle.onexit (child_process.js:771:34) ] ``` I have Cordova 3.2 installed and the Android 4.3 API aswell as 4.4. I tried to reinstall Cordova with ``` npm uninstall cordova ``` And reinstall it again, but it is still producing the same error. I also reinstalled the Android SDK. This is the log when I run run.bat --emulator: [ 'adb devices', null, 'List of devices attached \r\n\r\n', '' ] exec: android list avds [ 'android list avds', null, 'Available Android Virtual Devices:\n Name: AVD_for_Nexus_S\n Path: C:\\ Users\\Evers\\.android\\avd\\AVD_for_Nexus_S.avd\n Target: Android 4.4 (API lev el 19)\n ABI: armeabi-v7a\n Skin: 480x800\n', '' ] exec: android list avds [ 'android list avds', null, 'Available Android Virtual Devices:\n Name: AVD_for_Nexus_S\n Path: C:\\ Users\\Evers\\.android\\avd\\AVD_for_Nexus_S.avd\n Target: Android 4.4 (API lev el 19)\n ABI: armeabi-v7a\n Skin: 480x800\n', '' ] WARNING : no emulator specified, defaulting to AVD_for_Nexus_S Waiting for emulator... exec: adb devices events.js:72 throw er; // Unhandled 'error' event Any clues?