Fresh install of NativeScript CLI using the Installer fails due to missing SDK (but claims it is OK) #2735
Description
Using the installer on an absolutely fresh machine with newly installed Windows 10 is failing due to missing SDK. The installer is setting an ANDROID_HOME variable and also is bringing some files in C:\Users\niliev\AppData\Local\Android\sdk but in the same time the SDK is not installed and NativeScript CLI is failing to start.
Steps to reproduce:
- fresh install of Windows 10 with Java JDK installed and JAVA_HOME set. (but no Android SDK installed0
- using the installer to install Nodejs, Android SDK, and NativeScript.
- all is installed according to the installer (very fast install...) but at the end, the Android SDK is missing on the PC. (some files are located in
C:\Users\niliev\AppData\Local\Android\sdkbut still the CLI is not working due to missing SDK)
Activity
dtopuzov commentedon Apr 24, 2017
Same here, Java installed, Android not installed.
When run the installer it creates ANDROID_HOME variable and then it thinks Android is available, but it is not.
nikolavn commentedon Apr 26, 2017
I was not able to reproduce the issue both on a Windows 10 machine with nothing installed and on a Windows 10 with some application (not including the {N} prerequisites). I have downloaded the installer from the web site and also used the one available locally in OfficialReleases. I have performed 4-5 successful installations with this workflow:
It would be nice if you could send us logs from the failed installations (available under %temp% named NativeScript_CLI_Setup*). We have received error metrics from the failed installation of @dtopuzov but they are not very descriptive and also are showing Windows 8.1 as OS.
NickIliev commentedon Apr 26, 2017
@nikolavn I've followed the exact same steps. (using jdk-8u131-windows-x64.exe and setting JAVA_HOME before running the installer)
Here are the logs created by the installed on that day
nativescrtip-cli-log-win10.zip