Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-18632] CLI: Node 0.12: If the CLI is updated to 3.4.2 before the SDK is updated then you can't install the new SDK

GitHub Issuen/a
TypeBug
PriorityHigh
StatusClosed
ResolutionFixed
Resolution Date2015-03-04T19:15:30.000+0000
Affected Version/sRelease 3.5.1
Fix Version/sRelease 3.4.2
ComponentsCLI
Labelsmerge-3.5.1, qe-3.5.1
ReporterEwan Harris
AssigneePraveen Innamuri
Created2015-03-03T03:00:23.000+0000
Updated2015-03-05T18:20:18.000+0000

Description

Comments

  1. Feon Sua Xin Miao 2015-03-03

    I doubt Node 0.12 is supported by any of the pre-3.5.1 SDKs.
  2. Eric Merriman 2015-03-03

    [~fmiao] Right. It isn't. But in attempting to message when an SDK doesn't support node 0.12 we encountered this issue. This is expected to be a common workflow.
  3. Praveen Innamuri 2015-03-03

    Once we address TIMOB-18629 with a Warning instead of error, this will be resolved as well.
  4. Chris Barber 2015-03-03

    Hmm, maybe the Node.js version check needs to happen when loading an SDK command and not before any command is loaded/run.
  5. Praveen Innamuri 2015-03-04

    Addressed through Titanium CLI master PR: https://github.com/appcelerator/titanium/pull/199 Titanium CLI 3_5_X PR: https://github.com/appcelerator/titanium/pull/201 Titanium CLI 3_4_X PR: https://github.com/appcelerator/titanium/pull/200
  6. Ewan Harris 2015-03-05

    Verified fix on: Mac OSX 10.10.2 Appcelerator Studio, build: 3.4.2.201502181619 Titanium SDK build: 3.5.0.GA, 3.5.1.v20150302121618 Titanium CLI, build: 3.4.2-rc4 Alloy: 1.5.1 Node 0.12.0 Attempted to install a new SDK with ti sdk select set to 3.5.0.GA, there is now a warning printed out rather than an error and the SDK is installed. Closing ticket.

JSON Source