Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
3.5.0
-
Mac OSX
Description
`cordova run android --emulator` correctly finds a started android emulator and launches the app in it.
`cordova run android --emulator --target=emulatorName` does not find the emulator. Rather, I get the following error:
```
events.js:72
throw er; // Unhandled 'error' event
^
Error: spawn ENOENT
at errnoException (child_process.js:1000:11)
at Process.ChildProcess._handle.onexit (child_process.js:791:34)
Error: /Users/shawnfreyssonnet-inder/Work/vigour-js/test/browser/animation/nativeBuildStuff/platforms/android/cordova/run: Command failed with exit code 8
at ChildProcess.whenDone (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/cordova/superspawn.js:135:23)
at ChildProcess.emit (events.js:98:17)
at maybeClose (child_process.js:755:16)
at Process.ChildProcess._handle.onexit (child_process.js:822:5)
```
The same happens using `cordova emulate android --target=emulatorName`
In both examples, `emulatorName` matches a name found by running `./platforms/android/cordova/lib/list-emulator-images`