Titanium JIRA Archive
Appcelerator Community (AC)

[AC-527] Appcellerator CLI blocked after installing Android Studio

GitHub Issuen/a
TypeBug
Priorityn/a
StatusResolved
ResolutionNot Our Bug
Resolution Date2015-12-08T09:37:23.000+0000
Affected Version/sn/a
Fix Version/sn/a
ComponentsAppcelerator CLI
Labelsn/a
Reportercarlo
AssigneeShak Hossain
Created2015-12-04T09:34:56.000+0000
Updated2015-12-10T07:40:11.000+0000

Description

After installing Android Studio, CLI stop working. Solved renaming: android-sdk-windows\build-tools\build-tools-23.0.1 (downloaded by Android Studio) in android-sdk-windows\build-tools\23.0.1 Here's the errors: {noformat} C:\Users\ccampinoti>appc info Appcelerator Command-Line Interface, version 5.1.0 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. 2015-12-04T09:23:20.171Z | ERROR | titanium exited with exit code 1. re-run with -l trace to get detailed output {noformat} {noformat} C:\Users\ccampinoti>appc ti setup Appcelerator Command-Line Interface, version 5.1.0 Copyright (c) 2014-2015, Appcelerator, Inc. All Rights Reserved. Enter ctrl-c at any time to quit. ──────────────────────┤ Main Menu ├─────────────────────── 1) quick Quick Setup 2) check Check Environment 3) user User Information 4) app New App Defaults 5) network Network Settings 6) cli Titanium CLI Settings 7) sdk Titanium SDK Settings 8) android Android Settings 9) windows Windows Settings 10) exit Exit Where do you want to go? k ──────────────────┤ Check Environment ├─────────────────── | C:\Users\ccampinoti\AppData\Roaming\Titanium\mobilesdk\win32\5.1.1.GA\node_modules\node-appc\node_modules\semver\semver.js:293 throw new TypeError('Invalid Version: ' + version); ^ TypeError: Invalid Version: build.0.0 at new SemVer (C:\Users\ccampinoti\AppData\Roaming\Titanium\mobilesdk\win32\5.1.1.GA\node_modules\node-appc\node_modules\semver\semver.js:293:11) at Range.test (C:\Users\ccampinoti\AppData\Roaming\Titanium\mobilesdk\win32\5.1.1.GA\node_modules\node-appc\node_modules\semver\semver.js:1047:15) at Function.satisfies (C:\Users\ccampinoti\AppData\Roaming\Titanium\mobilesdk\win32\5.1.1.GA\node_modules\node-appc\node_modules\semver\semver.js:1096:16) at C:\Users\ccampinoti\AppData\Roaming\Titanium\mobilesdk\win32\5.1.1.GA\node_modules\node-appc\lib\version.js:156:33 at Array.some (native) at Object.satisfies (C:\Users\ccampinoti\AppData\Roaming\Titanium\mobilesdk\win32\5.1.1.GA\node_modules\node-appc\lib\version.js:152:34) at findSDK (C:\Users\ccampinoti\AppData\Roaming\Titanium\mobilesdk\win32\5.1.1.GA\node_modules\titanium-sdk\lib\android.js:827:44) at C:\Users\ccampinoti\AppData\Roaming\Titanium\mobilesdk\win32\5.1.1.GA\node_modules\titanium-sdk\lib\android.js:95:6 at C:\Users\ccampinoti\AppData\Roaming\Titanium\mobilesdk\win32\5.1.1.GA\node_modules\titanium-sdk\lib\android.js:78:5 at C:\Users\ccampinoti\AppData\Roaming\Titanium\mobilesdk\win32\5.1.1.GA\node_modules\async\lib\async.js:945:13 --------------------------------------------- at Object.setImmediate (C:\Users\ccampinoti\AppData\Roaming\Titanium\mobilesdk\win32\5.1.1.GA\node_modules\async\lib\async.js:200:9) at _insert (C:\Users\ccampinoti\AppData\Roaming\Titanium\mobilesdk\win32\5.1.1.GA\node_modules\async\lib\async.js:861:19) at Object.q.push (C:\Users\ccampinoti\AppData\Roaming\Titanium\mobilesdk\win32\5.1.1.GA\node_modules\async\lib\async.js:888:17) at async.parallel.sdk (C:\Users\ccampinoti\AppData\Roaming\Titanium\mobilesdk\win32\5.1.1.GA\node_modules\titanium-sdk\lib\android.js:92:10) at C:\Users\ccampinoti\AppData\Roaming\Titanium\mobilesdk\win32\5.1.1.GA\node_modules\async\lib\async.js:689:13 at C:\Users\ccampinoti\AppData\Roaming\Titanium\mobilesdk\win32\5.1.1.GA\node_modules\async\lib\async.js:239:13 at C:\Users\ccampinoti\AppData\Roaming\Titanium\mobilesdk\win32\5.1.1.GA\node_modules\async\lib\async.js:119:13 at _arrayEach (C:\Users\ccampinoti\AppData\Roaming\Titanium\mobilesdk\win32\5.1.1.GA\node_modules\async\lib\async.js:91:13) at _forEachOf (C:\Users\ccampinoti\AppData\Roaming\Titanium\mobilesdk\win32\5.1.1.GA\node_modules\async\lib\async.js:118:9) {noformat}

Comments

  1. Sharif AbuDarda 2015-12-07

    Hello [~c3k], Don't keep two Android SDK folder in your PC. If you already have an Android SDK with latest build tools which you used with Appcelerator previously. Try configuring that SDK folder path in your newly installed Android studio. Thanks.
  2. carlo 2015-12-07

    This is what I did, but during first start Android Studio download and create "build-tools-23.0.1" blocking Titanium
  3. Sharif AbuDarda 2015-12-07

    The SDK folder content is same for all cases. Whether it comes with Android studio or you manually downloaded it. Now if the SDK folder path is configured in bith of the studio. then it should be ok with both cases. Thanks.
  4. carlo 2015-12-07

    Folder is the same, problem is subfolder: * Android SDK manager creates build-tools\23.0.1 * Android Studio (don't know why) creates build-tools\build-tools-23.0.1 <- this is detected by Android SDK manager but completly blocks Ti CLI
  5. Mostafizur Rahman 2015-12-08

    This is not our bug. Thanks
  6. carlo 2015-12-10

    Is Titanium CLI script that look at Android SDK and an unexepected content (build-tools-***) completly lock the platform without clues to solve the problem IMHO this *is* a Titanium bug and need just an check on folder name to be solved

JSON Source