Titanium JIRA Archive
Appcelerator Community (AC)

[AC-1673] Unable to run project on both android emulator and android device.

GitHub Issuen/a
TypeBug
Priorityn/a
StatusClosed
ResolutionNot Our Bug
Resolution Date2014-09-04T07:27:31.000+0000
Affected Version/sn/a
Fix Version/sn/a
ComponentsTitanium SDK & CLI
Labelsandroid
ReporterNaresh Kumar
AssigneeMauro Parra-Miranda
Created2014-07-25T11:11:56.000+0000
Updated2016-03-08T07:38:09.000+0000

Description

I have updated the titanium after that android sdk not get installed so i revert back to old version of titanium sdk. but now i unable to run android project on emulator and device. Getting error message like /usr/local/lib/node_modules/titanium/node_modules/longjohn/dist/longjohn.js:185 throw e; ^ TypeError: Cannot read property '0' of undefined at exports.validate (/Users/sindhyapeter/Library/Application Support/Titanium/mobilesdk/osx/3.1.3.GA/android/cli/commands/_build.js:296:70) at exports.validatePlatformOptions (/Users/sindhyapeter/Library/Application Support/Titanium/mobilesdk/osx/3.1.3.GA/node_modules/titanium-sdk/lib/titanium.js:443:51) at exports.validate (/Users/sindhyapeter/Library/Application Support/Titanium/mobilesdk/osx/3.1.3.GA/cli/commands/build.js:112:9) at callCommandValidate (/usr/local/lib/node_modules/titanium/lib/cli.js:846:19) at /usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:551:21 at /usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:227:13 at iterate (/usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:134:13) at /usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:145:25 at /usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:229:17 at /usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:556:34 --------------------------------------------- at exports.execFile (child_process.js:691:9) at exports.exec (child_process.js:578:18) at async.series.cached (/Users/sindhyapeter/Library/Application Support/Titanium/mobilesdk/osx/3.1.3.GA/node_modules/node-appc/lib/android.js:86:4) at /Users/sindhyapeter/Library/Application Support/Titanium/mobilesdk/osx/3.1.3.GA/node_modules/async/lib/async.js:486:21 at /Users/sindhyapeter/Library/Application Support/Titanium/mobilesdk/osx/3.1.3.GA/node_modules/async/lib/async.js:185:13 at iterate (/Users/sindhyapeter/Library/Application Support/Titanium/mobilesdk/osx/3.1.3.GA/node_modules/async/lib/async.js:108:13) at /Users/sindhyapeter/Library/Application Support/Titanium/mobilesdk/osx/3.1.3.GA/node_modules/async/lib/async.js:119:25 at /Users/sindhyapeter/Library/Application Support/Titanium/mobilesdk/osx/3.1.3.GA/node_modules/async/lib/async.js:187:17 [ERROR] Application Installer abnormal process termination. Process exit value was 8 I have given correct android sdk path. SDK Install Locations: /Library/Application Support/Titanium /Users/sindhyapeter/Library/Application Support/Titanium [default] Installed SDKs: 3.1.3.GA [selected] /Users/sindhyapeter/Library/Application Support/Titanium/mobilesdk/osx/3.1.3.GA node version: v0.10.13 Operating System Name = Mac OS X Version = 10.8.5 Architecture = 64bit # CPUs = 4 Memory = 8.0GB Node.js Node.js Version = 0.10.13 npm Version = 1.3.2 Titanium CLI CLI Version = 3.2.3 node-appc Version = 0.2.1 Titanium SDKs 3.1.3.GA Install Location = /Users/sindhyapeter/Library/Application Support/Titanium/mobilesdk/osx/3.1.3.GA Platforms = iphone, tizen, mobileweb, android, blackberry git Hash = 222f4d1 git Timestamp = 09/18/13 12:00 node-appc Version = 0.1.30 Mac OS X Command Line Tools = installed

Comments

  1. Mauro Parra-Miranda 2014-08-03

    Hello, It's likely that once you updated everything and "went back to the old version", you ended with incompatible alloy versions,. CLI versions, Ti studio versions, etc. Maybe the best way here, would be to reinstall the latest version and make sure that everything (CLI, ALLOY, etc) runs with that Ti studio. Best Regards, Mauro
  2. Mauro Parra-Miranda 2014-08-15

    [~naresh.kumar@mahiti.org]: did you were able to fix this?
  3. Naresh Kumar 2014-08-18

    Yes. I had been resolved the issues.

JSON Source