[AC-768] After upgrade to Ti 3.2.2.GA I cannot run anything in my Mac with SDK 3.2.2
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | n/a |
| Status | Closed |
| Resolution | Cannot Reproduce |
| Resolution Date | 2014-03-18T05:15:17.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Studio |
| Labels | n/a |
| Reporter | Manuel Conde Vendrell |
| Assignee | Ritu Agrawal |
| Created | 2014-03-13T18:15:53.000+0000 |
| Updated | 2016-03-08T07:37:02.000+0000 |
You have an old CLI installed. Update. [WARN] : Requires version >=3.2.1, currently 3.1.2 [ERROR] : [31m Command "build" incompatible with this version of the Titanium CLI[39m [sudo] npm install -g titanium ti -version (only answering this Q&A type question because I'd much rather have the staff on jira fixing things and adding new features than doing end user support)
Another guy today had similar in the Q&A http://developer.appcelerator.com/question/163469/ios-simulator-will-not-lauch-dyld-library-not-loaded-rpathiphonesimulatorremoteclientframework#comment-205431 Seems he had old binaries or links laying around. 14:20 $ which ti /usr/local/bin/ti 14:38 $ which titanium /usr/local/bin/titanium
Umm, I have both too, but both are the same, even after executing [sudo] npm install -g titanium: MacBook:~ manu$ which titanium /usr/local/bin/titanium MacBook:~ manu$ which ti /usr/local/bin/ti MacBook:~ manu$ titanium -v 3.1.2 MacBook:~ manu$ ti -v 3.1.2
This is strange. May be some sort of caching issue as "npm install -g titanium" should have installed the latest GA version (3.2.1). Can you please try removing this package using "npm uninstall titanium" and then install it using the above command?
Still the same:
Ok, I found the problem. Don't ask me why, but this is what I found in my node_modules folder
*Notice*: 1. I rename titanium to oldtitanium because I supposed the problem was in the permissions (nobody-staff from 19 ago, when I installed Titanium for first time?) 2. After rename, I make the [sudo] npm install -g titanium 3. Then, the Password folder appeared (see datetime) After all this, I supposed that all was inside and... bingo! Just moving it to the right folder and all works now.*But I'm afraid of the other folders with still 19 ago date*. Maybe a problem for future updates to acs or alloy? If I do this I get an old version... MacBook:alloy manu$ alloy -v 1.2.2Alloy is a separate package [sudo] npm install -g alloy
Hi Stephen. With alloy the problem was exactly the same. Impossible for the installer to overwrite the current installation. Solution was the same: change the name, reinstall and move from Password folder to right folder. Now I have alloy 1.3.1 installed.
More information. Seems that the installation in my Elementary OS (Ubuntu) has the same problems!! See this:
manu@manu-XPS-M1330:/usr/lib/node_modules$ ll total 60 drwxr-xr-x 6 root root 4096 nov 30 13:55 ./ drwxr-xr-x 181 root root 36864 mar 12 23:19 ../ drwxr-xr-x 8 nobody manu 4096 nov 30 13:55 acs/ drwxr-xr-x 15 nobody manu 4096 nov 30 13:55 alloy/ drwxr-xr-x 9 root root 4096 feb 23 01:13 npm/ drwxr-xr-x 7 nobody manu 4096 nov 30 13:53 titanium//usr/lib/node_modules/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /usr/bin/ti -> /usr/lib/node_modules/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /home/manu/[sudo] password for manu: /usr/lib/node_modules/titanium/bin/titaniumchangememba-5:node_modules ragrawal$ pwd /usr/local/lib/node_modules changememba-5:node_modules ragrawal$ ls -al total 0 drwxr-xr-x 7 24561 wheel 238 Mar 5 14:25 . drwxrwxr-x 4 root admin 136 Jul 9 2013 .. drwxr-xr-x 12 nobody staff 408 Mar 5 14:25 acs drwxr-xr-x 21 nobody staff 714 Feb 11 10:43 alloy drwxr-xr-x 19 65534 staff 646 Nov 4 11:30 npm drwxr-xr-x 12 nobody staff 408 Feb 11 10:51 titanium drwxr-xr-x 18 nobody staff 612 Jan 27 21:27 titanium-code-processor changememba-5:node_modules ragrawal$Hi Ritu. In Ubuntu I haven't (was installed in usr/lib directly), in Mac I have it. To solve it, I deleted all Titanium related contents manually (usr/lib/node_modules), uninstalled node and start again installing from scratch. In this way I have now the last CLI version, Alloy and all seems to work well in Ubuntu... till the next update, I suppose. Finally, in Windows all works fine and never had any problem (I don't know why some programmers hate Windows, till now is the more stable environment for Titanium I had).
I am glad that you have been able to reproduce this issue. We tried to reproduce this issue in-house but we were not able to. Resolving this ticket as "Cannot reproduce" but we would be happy to reopen it if you run into it again.
Hi Ritu. I found a lot of Linux & Titanium update problems out there ([this](http://stackoverflow.com/questions/18965858/titanium-sdk-will-not-recognize-titanium-cli-node-alloy-or-npm-on-ubuntu-12-0) is where I based to solve my problems). All seems to be with permissions, but the fact that for both, Mac and Ubuntu, appeared the "Password:" folder is really strange (same problem on different sistems?).
StackOverflow post link indicates that the nom version installed on the machine was 0.6 (really old) and upgrading it to 0.10 solved the issue. Makes sense. You may want to check your node version by running "node -v" command.
Not in my case, I used that solution the first time I installed Titanium (and Node) because I didn't know how to install node out of the package manager (Linux is not my speciality). And I used it again now to reinstall all the soft (removing npm and node_modules manually, and Node later, and installing later from Studio, letting it to update automatically, once Node was installed).