Titanium JIRA Archive
Appcelerator Community (AC)

[AC-6203] No Android SDKs were found under the specified SDK location - Windows 10

GitHub Issuen/a
TypeBug
Priorityn/a
StatusResolved
ResolutionDone
Resolution Date2019-05-01T22:25:47.000+0000
Affected Version/sAppcelerator Studio 4.4.2
Fix Version/sn/a
ComponentsAppcelerator CLI
Labelsn/a
Reporterjamesjw01
AssigneeShak Hossain
Created2019-04-09T08:11:00.000+0000
Updated2019-05-01T22:25:47.000+0000

Description

I have gone to "Preferences > studio > platforms > android" and I have made sure it's pointing to the correct location but it still gives me the "No Android SDKs found" error. I have also tried installing Android Studio, which subsequently installed Android 9.0 SDK and some Android Tools. After installing Android Studio, I now have the "Run Package" option available - but I still can't run in an emulator. Also, now the Android section of the "prerequisites" says "Update" instead of Download... but if I click update then it goes through the whole process and says it's successful... but I still can't Run. Here is my log after I run appc ti setup check: {{──────────────────┤ Check Environment ├─────────────────── Node.js √ node installed (v8.11.1) √ npm installed (v5.6.0) Titanium CLI * cli new version v5.2.1 available (currently v5.1.1) Titanium CLI Dependencies √ acs up-to-date (v2.0.12) √ alloy up-to-date (v1.13.9) √ appc-cli-titanium up-to-date (v4.4.25) √ appc-inquirer up-to-date (v0.1.10) √ appc-logger up-to-date (v1.1.27) √ appc-platform-sdk up-to-date (v3.1.0) √ appcd up-to-date (v1.1.3) √ arrow up-to-date (v3.2.12) √ async up-to-date (v1.5.2) √ chalk up-to-date (v1.1.3) √ char-spinner up-to-date (v1.0.1) √ columnify up-to-date (v1.5.4) √ commander up-to-date (v2.9.0) √ debug up-to-date (v2.6.9) √ ejs up-to-date (v2.6.1) √ fields up-to-date (v0.1.24) √ fs-extra up-to-date (v0.26.7) √ inquirer up-to-date (v0.11.4) √ ip up-to-date (v1.1.5) √ jwt-simple up-to-date (v0.3.1) √ lodash up-to-date (v3.10.1) √ node-appc up-to-date (v0.2.49) √ node-forge up-to-date (v0.6.49) √ node-ios-device up-to-date (v1.6.3) √ npm-conf up-to-date (v1.1.3) √ pac-proxy-agent up-to-date (v2.0.2) √ plural up-to-date (v0.2.1) √ progress up-to-date (v1.1.8) √ recursive-readdir up-to-date (v2.2.2) √ request up-to-date (v2.88.0) √ retire up-to-date (v1.6.2) √ semver up-to-date (v5.6.0) √ tar up-to-date (v4.4.8) √ tiapp.xml up-to-date (v0.2.2) √ titanium up-to-date (v5.1.1) √ version-bump-prompt up-to-date (v3.1.2) √ which up-to-date (v1.3.1) √ wrench up-to-date (v1.5.9) Titanium SDK √ latest sdk installed (v8.0.0.GA) √ selected sdk up-to-date (v8.0.0.GA) Android Environment ! sdk Android SDK not found ! targets no targets found ! avds no avds found ! ndk Android NDK not found Java Development Kit × jdk JDK not found! Intel® Hardware Accelerated Execution Manager (HAXM) √ compatible ! installed not found; install HAXM to use Android x86 emulator Network √ online - no proxy server configured √ Network connection test √ Java-based connection test Directory Permissions √ home directory √ titanium config directory √ titanium sdk install directory √ temp directory}}

Comments

  1. Sharif AbuDarda 2019-04-09

    Hello, from the log, it looks like you don't have a valid JDK installed in your system. Follow the guide here for the valid JDK installation that supports Appcelerator Titanium. Thanks.
  2. jamesjw01 2019-04-10

    Hi, I have taken a few steps and have made some progress. Let me break it down for you: *Android SDK:*

    I used Android studio to download the SDK version that matched the version I had previously downloaded in Appcelerator

    Now I can select Run > titanium_1_WVGA800

    Unfortunately it fails with the error that I'm missing JDK

    When I run appci setup check it still says "SDK Not found"

    *Java JDK:*

    I have downloaded jdk-8u201-windows-x64.exe and installed it.

    I have set JAVA_HOME to C:\Program Files\Java\jdk1.8.0_201

    If I check Java Runtime Variables it shows me there are 3 versions

    When I run appci setup check it says "JDK Not found"

  3. jamesjw01 2019-04-11

    Hi, I managed to resolve everything in the end. Working fine now.

JSON Source