[TIMOB-13609] CLI: Running titanium from command line reports "titanium: command not found"
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Invalid |
Resolution Date | 2013-04-18T16:03:16.000+0000 |
Affected Version/s | Release 3.1.0 |
Fix Version/s | n/a |
Components | CLI |
Labels | triage |
Reporter | Joe Beuckman |
Assignee | Chris Barber |
Created | 2013-04-17T20:42:05.000+0000 |
Updated | 2017-03-29T17:15:05.000+0000 |
Description
Attachments
File | Date | Size |
---|---|---|
diagnostic.log | 2013-04-17T23:23:34.000+0000 | 1438 |
studio.log | 2013-04-17T23:23:34.000+0000 | 47823 |
Hi Joe, You get error: CLI not found in the console? Are there any other messages? Could you paste the log surrounding the error message? Please go to Help -> Titanium Studio and attach the log file and diagnostic. Also run "titanium status" from the terminal and paste the contents. Thanks.
Attached diagnostic.
Attached Studio log file.
And a status: jpbeuc1$ titanium status -bash: titanium: command not found
Joe--please try one of the following:
From a command line, "sudo npm -g install titanium" or
Install Studio 3.1.0
Joe: By the sounds of it, you updated to SDK 3.1, but not Studio 3.1? I updated to Studio and SDK 3.1 from 3.0.2 on one machine, "titanium status" works fine. On another machine, I updated to SDK 3.1, but left Studio as 3.0.2. "titanium status" still works fine. Please try Ingo's suggestion. In the meantime I'm closing as Needs More Info. Thanks.
I installed globally with npm as Ingo suggested and everything is working. Thank you guys! Part of the problem updating maybe be visible in the log. My internet connection here is tenuous and can be very slow when it works.
Marking it as invalid since w couldn't reproduce, but the workaround helped get Joe past his issue. If we get more reports and can find a pattern, we'll reopen.
Closing ticket as invalid.