[TIMOB-11473] CLI: error caused when tiapp.xml references a non-existent sdk version

GitHub Issue	n/a
Type	Bug
Priority	Critical
Status	Closed
Resolution	Cannot Reproduce
Resolution Date	2012-10-19T21:52:27.000+0000
Affected Version/s	Release 3.0.0
Fix Version/s	2012 Sprint 21 JS, 2012 Sprint 21
Components	Tooling
Labels	qe-cli
Reporter	Natalie Huynh
Assignee	Natalie Huynh
Created	2012-10-13T20:28:54.000+0000
Updated	2013-07-25T02:30:21.000+0000

Description

Steps to Reproduce: 1. Run titanium build on a project that references a sdk that does not exist Actual: [ERROR] Unable to run command "build" TypeError: Cannot read property 'path' of undefined 0 [ 'TypeError: Cannot read property \'path\' of undefined', ' at Object.exports.constructLegacyCommand [as constructLegacyCommand] (/Users/nataliehuynh/Library/Application Support/Titanium/mobilesdk/osx/3.0.0.v20121012174449/node_modules/titanium-sdk/lib/legacy.js:11:68)', Expected: Give user option to change the build or handle the error better

Comments

Chris Barber 2012-10-19

I think I fixed it.
Natalie Huynh 2012-11-15

Tested with Cli 3.0.16 SDK 3.0.0.v20121113170203
Russell Frank 2013-07-24

This still happens when there is no sdk-version in the tiapp.xml
Chris Barber 2013-07-25

@Russell, I just tested building an app with the bleeding edge Titanium CLI, Node.js 0.10.12, a selected SDK of 3.1.1.GA, and without a in the tiapp.xml and it built correctly using 3.1.1.GA. The latest stable CLI should work too. The only tiapp.xml fields that are required are name, id, and guid. The error described above is because they were using an old Titanium SDK (3.0.0 or 3.0.2) and Node.js 0.10.x. This means that if you want to build using Titanium SDK 3.0.0 or 3.0.2, you have to have Node.js 0.8.x installed. If you want to build for 3.1.0 or newer, you can use Node.js 0.8.x or 0.10.x.

JSON Source