NativeScript / NativeScript/nativescript-cli
Non-working emulator after NativeScript chocolatey installation
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 204
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 8
Description
Logged from user feedback (t.1162113 )
The other problem was - that after deleting the emulator created by the NativeScript installation chocolatey the emulator stopped working. That is because you declare the HAXM kernel in the installer manually and not coupled to Android studio - so when creating a new AVD under android studio it won't run because there is no kernel installed that runs under windows. Installing the Intel Atom Kernel in Android studio for the device will fix this issue.
With that, i'll mark this issue as resolved. However - you should consider updating the NativeScript chocolatey to include the proper Kernel install for Android Studio on Windows
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the NativeScript Chocolatey installation logic that declares HAXM, then compare it with the Android Studio Intel Atom Kernel installation needed for Windows AVDs. The change is done when a newly created Android Studio emulator runs after the NativeScript Chocolatey installation and deletion of the original emulator.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, javascript
- Domain
- cli, mobile, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100