Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-14387] Studio: Cannot update Alloy or CLI (Ti 3.0.2 -> 3.1.1)

GitHub Issuen/a
TypeBug
PriorityCritical
StatusClosed
ResolutionFixed
Resolution Date2013-08-05T18:03:54.000+0000
Affected Version/sRelease 3.1.1
Fix Version/s2013 Sprint 16, 2013 Sprint 16 Tooling, Release 3.2.0
ComponentsCLI
Labelsqe-3.2.0, qe-testadded
ReporterStephan Schrade
AssigneeChris Barber
Created2013-06-22T19:09:17.000+0000
Updated2014-02-25T18:07:25.000+0000

Description

Steps to Reproduce

Updating Studio via Menu

Actual Result

Studio Update works, but Alloy and CLI update not. Connection to repository.npmjs.org/titanium works but then stops at 2% Manual install with npm install -g titanium has the same result.

Expected Result

normal install

Attachments

FileDateSize
.log2013-06-22T19:09:19.000+000019911
diagnostic7098053241616591283.log2013-06-22T19:09:21.000+00005445

Comments

  1. Daniel Sefton 2013-06-24

    Hi Stephan, Please can you provide your latest diagnostic (Help -> Studio -> Run Diagnostic Test...)? The one you have attached is still showing Studio 3.0.2. The output displayed after you run "npm install -g titanium" would help as well. Thanks!
  2. Stephan Schrade 2013-06-24

    Diagnostic Test: Host OS: Mac OS X OS Arch: x86 JRE Version: 1.6.0_51 JRE Vendor: Apple Inc. JRE Home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Install Directory: file:/Applications/Titanium Studio/ Version: 3.0.2.201302041757 VM Arguments: -Xms40m -Xmx1024m -Declipse.p2.unsignedPolicy=allow -Declipse.log.size.max=10000 -Declipse.log.backup.max=5 -Xdock:icon=../Resources/titanium.icns -XstartOnFirstThread -Dorg.eclipse.swt.internal.carbon.smallFonts -XX:MaxPermSize=256m -Djava.class.path=/Applications/Titanium Studio/TitaniumStudio.app/Contents/MacOS//../../../plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar Workspace Directory: file:/Users/schrade/Projekte/titanium_studio/ Language: de_DE Titanium SDK Version: 1.4.0 Mobile SDK Timestamp: 07/27/10 18:21 Mobile SDK Build Number: d1e8c8 Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/1.4.0 Titanium SDK Version: 1.4.2 Mobile SDK Timestamp: 11/10/10 17:29 Mobile SDK Build Number: bf53f9 Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/1.4.2 Titanium SDK Version: 1.5.0 Mobile SDK Timestamp: 12/13/10 21:20 Mobile SDK Build Number: efb9caa Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/1.5.0 Titanium SDK Version: 1.5.1 Mobile SDK Timestamp: 12/16/10 16:25 Mobile SDK Build Number: 16bbb92 Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/1.5.1 Titanium SDK Version: 1.6.2 Mobile SDK Timestamp: 04/18/11 17:16 Mobile SDK Build Number: 878906d Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/1.6.2 Titanium SDK Version: 1.7.0 Mobile SDK Timestamp: 06/06/11 18:05 Mobile SDK Build Number: 64155ee Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/1.7.0 Titanium SDK Version: 1.7.1 Mobile SDK Timestamp: 06/21/11 14:28 Mobile SDK Build Number: 1293a6d Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/1.7.1 Titanium SDK Version: 1.7.2 Mobile SDK Timestamp: 07/21/11 09:36 Mobile SDK Build Number: 97c3689 Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/1.7.2 Titanium SDK Version: 1.7.5 Mobile SDK Timestamp: 11/02/11 17:00 Mobile SDK Build Number: ab20af7 Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/1.7.5 Titanium SDK Version: 1.8.0.1 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 12/22/11 13:09 Mobile SDK Build Number: fbdc96f Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/1.8.0.1 Titanium SDK Version: 1.8.1 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 01/27/12 17:31 Mobile SDK Build Number: a24502a Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/1.8.1 Titanium SDK Version: 1.8.2 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 02/23/12 17:46 Mobile SDK Build Number: 59b3a90 Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/1.8.2 Titanium SDK Version: 2.0.1 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 04/12/12 16:33 Mobile SDK Build Number: 999c68a Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/2.0.1.GA Titanium SDK Version: 2.0.1 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 04/12/12 16:33 Mobile SDK Build Number: 999c68a Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/2.0.1.GA2 Titanium SDK Version: 2.0.2 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 05/30/12 10:21 Mobile SDK Build Number: 2ff31a3 Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/2.0.2.GA Titanium SDK Version: 2.1.3 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 10/02/12 16:16 Mobile SDK Build Number: 15997d0 Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/2.1.3.GA Titanium SDK Version: 3.0.0 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 12/12/12 18:49 Mobile SDK Build Number: a5894b3 Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/3.0.0.GA Titanium SDK Version: 3.0.1 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 01/14/13 13:32 Mobile SDK Build Number: e37e356 Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/3.0.1.v20130114133207 Titanium SDK Version: 3.0.2 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 02/15/13 19:02 Mobile SDK Build Number: 5a77fe7 Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/3.0.2.GA Titanium SDK Version: 3.0.2 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 01/29/13 17:16 Mobile SDK Build Number: 9207bbe Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/3.0.2.v20130129171611 Titanium SDK Version: 3.0.2 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 02/07/13 16:46 Mobile SDK Build Number: a4def81 Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/3.0.2.v20130207164659 Titanium SDK Version: 3.1.0 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 04/15/13 18:45 Mobile SDK Build Number: 57634ef Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/3.1.0.GA Titanium SDK Version: 3.1.1 Mobile SDK Modules API Version:2 Mobile SDK Timestamp: 06/15/13 16:09 Mobile SDK Build Number: f7592c1 Titanium SDK Location: /Library/Application Support/Titanium/mobilesdk/osx/3.1.1.GA Titanium CLI Version: 3.1.1 Alloy Version: 1.1.2 ---------------------------------------------------------------------------------- stephan-schrades-macbook-pro:~ schrade$ sudo npm install -g titanium Password: npm http GET https://registry.npmjs.org/titanium npm http 304 https://registry.npmjs.org/titanium and then it just stays this way for hours...... after sudo npm cache clean stephan-schrades-macbook-pro:~ schrade$ sudo npm cache clean stephan-schrades-macbook-pro:~ schrade$ sudo npm install -g titanium npm http GET https://registry.npmjs.org/titanium npm http 200 https://registry.npmjs.org/titanium npm http GET https://registry.npmjs.org/titanium/-/titanium-3.1.1.tgz npm http 200 https://registry.npmjs.org/titanium/-/titanium-3.1.1.tgz and then it stays here for hours...... Download the file via the browser is no problem. CU Stephan
  3. Michael Xia 2013-06-24

    This appears to be an issue with the remote npm registry; not sure what we could do here. If you could download the file via browser successfully, you could then install from the command line via "sudo npm install -g titanium-3.1.1.tgz".
  4. Stephan Schrade 2013-06-24

    Unfortunately no success :( stephan-schrades-macbook-pro:~ schrade$ sudo npm cache clean Password: stephan-schrades-macbook-pro:~ schrade$ sudo npm install Downloads/titanium-3.1.1.tar and then nothing happens ......
  5. Daniel Sefton 2013-06-24

    There's a similar log in this report, it might be worth checking the suggestions in the comments: TISTUD-2218
  6. Michael Xia 2013-06-24

    Hi Stephan, try the "sudo npm install -g" command on the original titanium-3.1.1.tgz download instead of the extracted tar file.
  7. Stephan Schrade 2013-06-24

    @Daniel: Does this mean it is a bug when I have to enter my appcelerator username and password every time I want to start the studio? I don't know anything else. I always always had and have to enter my appcelerator credentials. I don't know any other behaviour! @Michael: stephan-schrades-macbook-pro:~ schrade$ sudo npm install Downloads/titanium-3.1.1.tgz Password: and it is still waiting and waiting and waiting.........
  8. Daniel Sefton 2013-06-24

    Yeah you shouldn't have to enter your credentials every time.
  9. Stephan Schrade 2013-06-24

    @Daniel: I tried all three suggested workarounds: 1. Open up Preferences > General > Security > Secure Storage. didn't help 2. Deleting secure storage: I can't find the mentioned files (I know they have a dot at the beginning and are normally not visible) 3. Run Studio as Administrator didn't help So I have no success here :-(
  10. Michael Xia 2013-06-25

    @Stephan: the diagnostic log in fact shows you already have the latest CLI 3.1.1. The alloy version is behind though. Could you try uninstalling them from the command line and then reinstall to see if it helps? 
        sudo npm uninstall -g titanium
    sudo npm uninstall -g alloy
    npm cache clean
    sudo npm install -g titanium
    sduo npm install -g alloy
    Thanks.
  11. Stephan Schrade 2013-06-25

    @Michael: Unfortunately nothing has changed: Stephan-Schrades-MacBook-Pro:~ schrade$ sudo npm uninstall -g titanium Password: Stephan-Schrades-MacBook-Pro:~ schrade$ sudo npm uninstall -g alloy Stephan-Schrades-MacBook-Pro:~ schrade$ sudo npm cache clean Stephan-Schrades-MacBook-Pro:~ schrade$ sudo npm install -g titanium npm http GET https://registry.npmjs.org/titanium npm http 200 https://registry.npmjs.org/titanium npm http GET https://registry.npmjs.org/titanium/-/titanium-3.1.1.tgz npm http 200 https://registry.npmjs.org/titanium/-/titanium-3.1.1.tgz .......... nothing more :( .... CU Stephan
  12. Michael Xia 2013-06-26

    Hmm, I'm running out of ideas. Does "sudo npm install -g titanium@3.1.0" work? Want to see if it's specific to the 3.1.1 version of CLI.
  13. Stephan Schrade 2013-06-26

    Yes, this works without any problems!
  14. Stephan Schrade 2013-06-26

    Is there no possibility to create an extended logfile or something else ? At least there must be some possibility to find out which was the last successfull command.
  15. Michael Xia 2013-06-26

    [~cbarber] Any suggestion to the user on how to diagnose the CLI installation issue? Stephan could "sudo npm install -g titanium@3.1.0" just fine, but getting the latest 3.1.1 tarball is stuck.
  16. Chris Barber 2013-06-26

    What version of npm and node.js are you using? Try this: 
        sudo npm cache clean
    
    sudo npm install -dd -g titanium
    If it doesn't work, please past the complete npm install output.
  17. Stephan Schrade 2013-06-26

    The installation just stops after a couple of commands. Here is the result: localhost:~ schrade$ npm -v 1.2.0 localhost:~ schrade$ node -v v0.8.17 localhost:~ schrade$ sudo npm cache clean Password: localhost:~ schrade$ sudo npm install -dd -g titanium npm info it worked if it ends with ok npm verb cli [ 'node', '/usr/local/bin/npm', 'install', '-dd', '-g', 'titanium' ] npm info using npm@1.2.0 npm info using node@v0.8.17 npm verb read json /usr/local/lib/package.json npm verb read json /usr/local/lib/package.json npm verb cache add [ 'titanium', null ] npm verb parsed url { pathname: 'titanium', path: 'titanium', href: 'titanium' } npm verb lock titanium /Users/schrade/.npm/18c4df8b-titanium.lock npm verb addNamed [ 'titanium', '' ] npm verb addNamed [ null, '' ] npm verb lock titanium@ /Users/schrade/.npm/9f6b1b6d-titanium.lock npm verb url raw titanium npm verb url resolving [ 'https://registry.npmjs.org/', './titanium' ] npm verb url resolved https://registry.npmjs.org/titanium npm info trying registry request attempt 1 at 09:40:17 npm http GET https://registry.npmjs.org/titanium npm http 200 https://registry.npmjs.org/titanium npm verb addNamed [ 'titanium', '3.1.1' ] npm verb addNamed [ '3.1.1', '3.1.1' ] npm verb lock titanium@3.1.1 /Users/schrade/.npm/ca49311c-titanium-3-1-1.lock npm verb lock https://registry.npmjs.org/titanium/-/titanium-3.1.1.tgz /Users/schrade/.npm/eccb1b73--org-titanium-titanium-3-1-1-tgz.lock npm verb addRemoteTarball [ 'https://registry.npmjs.org/titanium/-/titanium-3.1.1.tgz', npm verb addRemoteTarball 'c3494051887c9f7cdd9b06753ee866e816ecaf37' ] npm info retry fetch attempt 1 at 09:40:24 npm verb fetch to= /Users/schrade/tmp/npm-2584/1372232424612-0.5089970887638628/tmp.tgz npm http GET https://registry.npmjs.org/titanium/-/titanium-3.1.1.tgz npm http 200 https://registry.npmjs.org/titanium/-/titanium-3.1.1.tgz npm info shasum c3494051887c9f7cdd9b06753ee866e816ecaf37 npm info shasum /Users/schrade/tmp/npm-2584/1372232424612-0.5089970887638628/tmp.tgz npm verb tar unpack /Users/schrade/tmp/npm-2584/1372232424612-0.5089970887638628/tmp.tgz npm verb lock /Users/schrade/tmp/npm-2584/1372232424612-0.5089970887638628/package /Users/schrade/.npm/471d351a-24612-0-5089970887638628-package.lock npm verb read json /Users/schrade/tmp/npm-2584/1372232424612-0.5089970887638628/package/package.json npm verb from cache /Users/schrade/tmp/npm-2584/1372232424612-0.5089970887638628/package/package.json npm verb tar pack [ '/Users/schrade/.npm/titanium/3.1.1/package.tgz', npm verb tar pack '/Users/schrade/tmp/npm-2584/1372232424612-0.5089970887638628/package' ] npm verb tarball /Users/schrade/.npm/titanium/3.1.1/package.tgz npm verb folder /Users/schrade/tmp/npm-2584/1372232424612-0.5089970887638628/package npm verb lock /Users/schrade/.npm/titanium/3.1.1/package.tgz /Users/schrade/.npm/adc80f7d-e-npm-titanium-3-1-1-package-tgz.lock npm verb lock /Users/schrade/.npm/titanium/3.1.1/package /Users/schrade/.npm/dd954044-hrade-npm-titanium-3-1-1-package.lock npm verb tar unpack /Users/schrade/.npm/titanium/3.1.1/package.tgz npm verb lock /Users/schrade/.npm/titanium/3.1.1/package /Users/schrade/.npm/dd954044-hrade-npm-titanium-3-1-1-package.lock npm verb read json /Users/schrade/.npm/titanium/3.1.1/package/package.json npm info shasum 6272bb806fd229c89676552948c263ec4258ce43 npm info shasum /Users/schrade/.npm/titanium/3.1.1/package.tgz npm verb from cache /Users/schrade/.npm/titanium/3.1.1/package/package.json npm verb chmod /Users/schrade/.npm/titanium/3.1.1/package.tgz 644 npm verb chown /Users/schrade/.npm/titanium/3.1.1/package.tgz [ 0, 20 ] npm info install titanium@3.1.1 into /usr/local/lib npm info installOne titanium@3.1.1 npm verb from cache /Users/schrade/.npm/titanium/3.1.1/package/package.json npm info /usr/local/lib/node_modules/titanium unbuild npm verb read json /usr/local/lib/node_modules/titanium/package.json npm info preuninstall titanium@3.1.1 npm info uninstall titanium@3.1.1 npm verb true,/usr/local/lib/node_modules,/usr/local/lib/node_modules unbuild titanium@3.1.1 npm verb /usr/local/bin,[object Object] binRoot npm info postuninstall titanium@3.1.1 npm verb tar unpack /Users/schrade/.npm/titanium/3.1.1/package.tgz npm verb lock /usr/local/lib/node_modules/titanium /Users/schrade/.npm/b1e37a7e--local-lib-node-modules-titanium.lock npm verb read json /usr/local/lib/node_modules/titanium/package.json npm info preinstall titanium@3.1.1 npm verb from cache /usr/local/lib/node_modules/titanium/package.json npm verb readDependencies using package.json deps npm verb from cache /usr/local/lib/node_modules/titanium/package.json npm verb readDependencies using package.json deps npm verb read json /usr/local/lib/node_modules/titanium/node_modules/node_modules/package.json npm verb read json /usr/local/lib/node_modules/titanium/node_modules/package.json/package.json npm verb read json /usr/local/lib/node_modules/titanium/node_modules/README.md/package.json
  18. Stephan Schrade 2013-06-27

    Can you please help me. I'm stuck. I can't finish my development because I do need the 3.1.1 because of bugs in the older version. What can I do?
  19. Stephan Schrade 2013-06-27

    I've started my virtual machine with OS X. Here I do have npm 1.2.2 and node 0.8.18. Exactly the same behaviour. npm install stops at the same spot.
  20. Chris Barber 2013-06-27

    Hmm, you're using a pretty old version of Node.js. 0.8.18 was released on Jan 24, 2013, so that's 6 months old. Now, things *should* work on 0.8.18, but maybe there's a bug in npm 1.2.2. Can you try upgrading to 0.8.25? http://nodejs.org/dist/v0.8.25/ Remember to uninstall the previous Titanium CLI install and clear the npm cache.
  21. Stephan Schrade 2013-06-28

    I'm sorry but I gave up. I had to move on so I threw the studio into the trash, downloaded the newest studio.dmg and reinstalled it. After that I had to update alloy, cli etc. and that worked without any problems. Also now I don't have to type in my credentials every time I do start the studio. Isn't node.js automatically updated every time through a new version of titanium? So I have to tkae care about that manually? Anything else which has to be updated manually?
  22. Michael Xia 2013-06-28

    The node.js is updated automatically to the working version we tested against for a particular release (for 3.1.1, it would be 0.8.22).
  23. Ingo Muschenetz 2013-08-05

    I believe this is addressed as part of the fix for TIMOB-13178. Basically there was an issue with the NPM version shipped with Node.js. I'm going to mark this as resolved based on this, but please reopen if it's still an issue.
  24. Olga Romero 2013-11-26

    Closing, please reopen if occurs. Tested with 3.2.X studio and node.js 0.10.13 Alloy and CLI update successfully

JSON Source