Appcelerator Blog

The Leading Resource for All Things Mobile

Announcing Titanium 3.1 and Node.ACS Production Releases

0 Flares 0 Flares ×

It’s all about enterprise connectivity, performance and new platforms

We have kept ourselves pretty busy here at Appcelerator over the last couple of months. Today we are excited to announce a major release for both the Titanium and Cloud products: Titanium Studio and SDK 3.1 and Node.ACS GA.

Titanium 3.1

In the 3.1 release we focused on 3 key areas: performance optimization, APIs, and new platform support. Please see the release notes for further details.

Performance Optimization

  • We spent significant time optimizing the core architecture of Titanium, focusing on object creation, window creation, image usage and other key areas with broad applicability. For these integral pieces:
  • iOS apps will run on average 20% faster over our 3.0.0 release
  • Android apps will run on average 36% faster over our 3.0.0 release
  • We have also released the ListView component which functions several times faster than the TableView component.
  • In short you should notice a performance improvement for all of your apps running under 3.1.0.

    Alloy Updates

    We have also been hard at work extending Alloy, our MVC framework. The amount of positive feedback that we have received on Alloy has been outstanding, and It is being adopted at a rate faster than we ever expected. Titanium Studio 3.1.0 now supports the following features for Alloy apps:
    • Content assist
    • Debugging

    APIs

    ListView This release introduces ListView, a new Titanium component to replace the existing TableView. ListView uses a data-oriented approach versus TableView’s view-oriented approach which greatly improves performance. iOS EventKit UI Framework The iOS EventKit framework, allowing access to calendar events and reminders, is now available from within Titanium.

    Modules

    In this release we have also released some new modules. Specifically:
    • Newsstand (iOS): Publish a magazine or periodical with Titanium
    • NFC (Android): Read NFC (Near-Field Communication) tags from inside Titanium applications.
    • Facebook V3 (Android, iOS) API support

    New Platforms

    3.1 contains support for mobile platforms beyond iOS and Android: Tizen Tizen is an open source, standards-based, mobile software platform supported by leading mobile operators and device manufacturers including Samsung and Intel. It is now a full member of the Titanium family, supported in Titanium 3.1.0 Studio and SDK. BlackBerry Our Blackberry 10 support is now in beta. Please begin building apps for the BlackBerry 10 and provide us with feedback. In this beta release we believe there are the majority of features to get you started, including Alloy support, MapView, WebView, Database, Localization Support, and much, much more. To use the BlackBerry beta, you must download a 3.2 version of the Titanium SDK from the continuous integration (CI) server. Note that the 3.2 builds have not received any testing except for the BlackBerry beta. For all other platforms, these builds should be regarded as unstable builds

    Downloading 3.1.0

    For new users, download Titanium 3.1 by clicking here. For existing Titanium Studio users, you will be prompted to update automatically on the next restart. You can also manually check for updates by selecting the “Check for Titanium SDK Updates” from the “Help” menu within Titanium Studio. If you previously installed the Release Candidate versions of the Titanium CLI and Alloy, that is, npm install titanium@3.1.0-cr and npm install alloy@1.1.0-cr, or any -beta or -cr packages, you need to first uninstall these components before installing or updating to 3.1.0.GA. The release notes contain specific instructions on how to do so.

    Node.ACS version 1.0 (GA)

    Node.ACS extends Appcelerator Cloud Services by providing the popular Node.JS development framework on the middle-tier. Using Node.ACS, you can implement and deploy server services using JavaScript on the Appcelerator Cloud. You can develop connectors to enterprise data back-ends like Oracle or Salesforce for your entire mobile app portfolio, extend the functionality of prebuilt services provided by Appcelerator Cloud Services (ACS) or simply use any of the 1000’s Node.JS modules published by the developer community. As a developer, you will immediately realize the benefits of:
    • a single programming language (JavaScript) and development environment (Studio) for both client and server side code.
    • a single location to host your business and application logic
    • easy access to the ACS database and storage
    • an MVC framework for creating scalable Node.ACS apps
    • ability to update your Node.ACS app independently from your mobile app
    • reliable, scalable infrastructure for your backend

    With Node.ACS, Appcelerator Cloud becomes a comprehensive MBaaS (Mobile Backend-as-a-Service) that any enterprise can use for deploying the server code for its mobile apps. Node.ACS will be available as part of the Appcelerator Platform offering. Node.ACS apps can be deployed both on the public Appcelerator Cloud and a Virtual Private Cloud. Getting Started with Node.ACS To start developing Node.ACS apps, use the resources below:

    Note: if you were participating in the Node.ACS developer preview, see the Node.ACS Release Notes for instructions on how to migrate your Node.ACS apps. As always I want to thank our 450,000 strong community of developers for your constant feedback and support.

    0 Flares Twitter 0 Facebook 0 Google+ 0 LinkedIn 0 Email -- 0 Flares ×

    55 Comments

    1. Fred

      Hi all, I have a problem. I have updated my Titanium studio in 3.1.0 GA, the problem is on launch of simulator, is only on iPhone without retina.

      If i change manually the configuration on the simulator app (Xcode) it’s ok but if i run again with titanium , he’s automatically changed by the iphone without retina.

      You have a solution ? Help me please.
      Thank you very much.

      • Ingo Muschenetz

        We’ve added the ability to choose when and where you want to launch in retina mode. See here.

    2. Mutturaj

      Getting below Error after update :

      Titanium Command-Line Interface, CLI version 3.1.0, Titanium SDK version 3.1.0.GA
      Copyright (c) 2012-2013, Appcelerator, Inc. All Rights Reserved.
      Please report bugs to http://jira.appcelerator.org/
      [ERROR] Missing required option “–password”

      • Ingo Muschenetz

        @Mutturaj. Try doing a “titanium login” from the command line.

    3. I’ve upgraded to the latest version of Ti Studio but i dont see the retina option there. What do I need to do to have the Retina option show up like it appears on the above link?

    4. Fred

      Thank you for your fast reply and your link 😉

      In the “Run configuration” (Create, manage and run configurations), i haven’t the check box “retina display”.

      I ‘ve find a other solution. In the file “tiapp.xml” with the mode “overview” click “configure” in the bottom configuration.
      The window “Preferences Filtered” opens. In a plateform IOS change the “Default Display”.

      Thank again 😉

    5. MichaelMichael

      Thanks a lot about the new SDK and the new features that supported .. but I have a quistion about Ti.map module .. when i add the map view in scrollableview .. it’s not work ! .. is that can i do with this module or not?

    6. Mutturaj

      I tried logging in using Terminal, i get below error

      Titanium Command-Line Interface, CLI version 3.1.0, Titanium SDK version 3.1.0.GA
      Copyright (c) 2012-2013, Appcelerator, Inc. All Rights Reserved.

      Please report bugs to http://jira.appcelerator.org/

      Username: (mutturajb@gmail.com)
      Password:

      Login failed: Error: Error communicating with the server: Error: tunneling socket could not be established, cause=connect ECONNREFUSED

      • Ingo Muschenetz

        @Mutturaj: Are you behind a proxy?

    7. Nancy Thomas

      Hi,

      1.- “Initializing Node.ACS” gets stuck at 30%.

      2.- Android emulator launched with Titanium never shows the Desktop. Titanium console shows: [TRACE] adb devices returned 1 devices/emulators, till it crashes:

      [ERROR] error: device offline
      [ERROR] Exception occured while building Android project:
      [ERROR] Traceback (most recent call last):
      [ERROR] File “/home/user/.titanium/mobilesdk/linux/3.0.2.GA/android/builder.py”, line 2392, in

      […]

      3.- Maps don’t work. Google Maps v1 API is completely disabled? v2 will be fully compatible with v1? We need the API key in any case?

      Thanks.

      • Ingo Muschenetz

        @Nancy. Google is not handing out any more v1 maps keys, but you can continue to use old ones. V2 is compatible with V1, but may need small API changes as Google themselves added new features. Yes, you need the key.

    8. Great work on this release. Really glad to see you took the time to work on speed and stability.

      On the second build after a clean I run into a NodeJS error. Any idea how I can fix this?

      http://developer.appcelerator.com/question/151074/sdk-31ga-unable-to-build-ipad-simulator#comment-168728

    9. Sarah

      So happy to see the calendar support for iOS! Looking forward to using this release – keep up the good work guys!

    10. The option for Retina display is available at Preferences > Studio > Platforms > iOS page.

    11. @Nancy: If you double-click on the status that shows “Initialize Node.ACS” to bring up the Progress view, do you see additional message underneath “Initialize Node.ACS” that could indicate what task it is stuck at?

      Thanks.

    12. Thanks for the new releases!

      I wonder if it’s possible the recent releases are impacting a situation on the ACS backend, where I suddenly get an error when trying to create a new custom object: When I search for an existing user, the search dialog does not display any search results, and site displays the following pop up:

      “✖ Error: This regex query is not supported, regex expression should start with ^letter or ^digit

      (tested in production as well as development, with Firefox and Safari)

      Any ideas how I can create custom objects now, when I cannot find existing users to link it to?

      Could latest Node.acs release, or the ACS release from the April 11 have something to do with this? http://cloud.appcelerator.com/docs/releasenotes#

      Many thanks! JB

    13. Daniel

      I’m having the same problem as Nancy. I’m on Mac OS, just installed Titanium Studio and it also hangs on “Initializing Node.ACS” -> “Logging into Node.ACS”.
      Any ideas what could be the problem here?

      • Ingo Muschenetz

        @Daniel, please see the troubleshooting info Michael is asking for.

    14. Christopher Carranza

      Just a quick question. The release notes state this for the global context:

      “As of this release, this behavior works on Android, iOS and Mobile Web. Prior to Release 3.1.0, this behavior only worked on iOS and Mobile Web.

      The usage of the global context in CommonJS modules is unsupported and deprecated, and will be removed in a future Titanium SDK release.”

      A couple things here. First this statement makes it sound like you’ve improved this phenomenon to now include Android, which it wasn’t able to do before, and i have noticed this in my apps. I use this approach for my iPhone version, but i can’t access the variables in my Android version.

      But second, does this mean that soon if i declare a variable in app.js, and i later want to access, or change that variable within a commonJS module, that i will no longer be able to do so? If that’s the case how am i able to access and transfer information?

    15. Hieu Pham

      @Michael, regarding Map module v2 not working in ScrollableView, I believe you’re talking about this: https://jira.appcelerator.org/browse/TIMOB-13611

    16. Danny

      I have a problem to install Node.ASC 1.0.0

      “sh: node: command not found”

      But using Terminal I can see that node is installed (v0.8.22) in /usr/local/bin/node

      BTW: with the update popup this invalid URL is opened with Firefox:
      http://developer.appcelerator.com/landing/index.html

    17. Ingo Muschenetz

      @Danny. Where are you getting the “command not found” error?

    18. Quang Pham

      the 9patch images display wrong on 3.1.0
      3.0.2 is ok

    19. Quang Pham
    20. Danny

      @Ingo: here is the log from Titanium Studio when trying to install Node.ASC

      http://pastie.org/7640973

    21. Dana

      I’m having the same problem as Nancy – “Initializing Node.ACS” gets stuck at 30%. Clicking on it says ‘Logging into Node.acs’. I’m not behind a proxy. Tried connecting through a VPN and it still hangs.

      Also, new projects crash out of the iOS simulator.

      I’m using Mac OSX 10.8.3

    22. Saamy

      Map modul is missing in 3.1.0 GA, its not workig. Please let me know if i should manually install something to get latest Google Map V2

    23. Ingo Muschenetz

      @Saamy. The Map module is actually published on the Marketplace. You can download it here: https://marketplace.appcelerator.com/apps/5005

    24. Ingo Muschenetz

      @Nancy, @Dana, @Danny. We have a tracking issue here: https://jira.appcelerator.org/browse/TISTUD-4322. Can you add your comments there (and try a possible workaround)?

    25. Ingo Muschenetz

      @Dana. For iOS projects crashing, we need more info, please file a ticket and we can investigate.

    26. Nuno

      Thank you all for this amazing product!

      So far the upgrade was a success here in my work-humble-land :)
      @Ingo, nice suporte you have done in the comments in this and others posts.

      – Nuno Costa

    27. Saamy

      Thanks for you quick response.

      Today i downloaded Titanium Studio and SDK (3.1.0GA), Alloy, CLI and other required tools.

      When i try to run the app in Android Simulator i’m getting below error (both Alloy and classic project)

      Could you please help me to resolve this issue?

      Titanium Command-Line Interface, CLI version 3.1.0, Titanium SDK version 3.1.0.GA
      Copyright (c) 2012-2013, Appcelerator, Inc. All Rights Reserved.
      [INFO] : Found Alloy app in C:SaamyTitaniumWorkspaceTestapp
      [INFO] : Executing Alloy compile: alloy.cmd compile C:SaamyTitaniumWorkspaceTestapp –config platform=android,version=0,simtype=none,devicefamily=none,deploytype=development
      [INFO] : —– MVC GENERATION —–
      [INFO] : [index.xml] view processing…
      [INFO] : style: “index.tss”
      [INFO] : view: “index.xml”
      [INFO] : controller: “index.js”
      [INFO] : created: “Resourcesalloycontrollersindex.js”
      [INFO] :
      [INFO] : [app.js] Titanium entry point processing…
      [INFO] : created: “Resourcesapp.js”
      [INFO] :
      [INFO] : —– OPTIMIZING —–
      [INFO] : – alloy.js
      [INFO] : – alloybackbone.js
      [INFO] : – alloyCFG.js
      [INFO] : – alloyunderscore.js
      [INFO] : – alloywidget.js
      [INFO] : – alloycontrollersBaseController.js
      [INFO] : – alloycontrollersindex.js
      [INFO] : – alloysynclocalStorage.js
      [INFO] : – alloysyncproperties.js
      [INFO] : – alloysyncsql.js
      [INFO] : – alloysyncutil.js
      [INFO] :
      [INFO] : Alloy compiled in 1.51764s
      [INFO] : Alloy compiler completed successfully
      [INFO] : Running emulator process: python “C:UserssaamyAppDataRoamingTitaniummobilesdkwin323.1.0.GAandroidbuilder.py” “emulator” “Test” “C:SaamySWadt-bundle-windows-x86-20130219adt-bundle-windows-x86-20130219sdk” “C:SaamyTitaniumWorkspaceTest” “com.test” “3” “HVGA” “armeabi”
      [INFO] : Running build process: python “C:UserssaamyAppDataRoamingTitaniummobilesdkwin323.1.0.GAandroidbuilder.py” “simulator” “Test” “C:SaamySWadt-bundle-windows-x86-20130219adt-bundle-windows-x86-20130219sdk” “C:SaamyTitaniumWorkspaceTest” “com.test” “3” “HVGA”
      [INFO] logfile = C:SaamyTitaniumWorkspaceTestbuild.log

      [ERROR] : Build process exited with code 1
      [ERROR] : Project failed to build after 7s 505ms

    28. Ingo Muschenetz

      @Sammy. You need to file a ticket. I can’t help with errors involving stack traces inside the context of this blog.

    29. Saamy

      Sure, Thank You

    30. @Daniel and @Danny, can you try to install node.acs npm manually in the terminal?

      sudo npm -g install acs

    31. Saamy

      Hi all,

      I had same issue in windows, see below error log(Error: SSL Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE)

      Then I googled and got this command “npm config set strict-ssl false” then tried to install ACS. its working now

      npm http GET https://registry.npmjs.org/underscore/1.3.3
      npm http 304 https://registry.npmjs.org/request/2.14.0
      npm http 304 https://registry.npmjs.org/npm/1.2.1
      npm http 304 https://registry.npmjs.org/wrench/1.3.9
      npm http 304 https://registry.npmjs.org/underscore/1.3.3
      npm http 304 https://registry.npmjs.org/jade/0.28.1
      npm http 304 https://registry.npmjs.org/string/1.1.0
      npm http 304 https://registry.npmjs.org/esprima/0.9.9
      npm http GET https://github.com/appcelerator/cocoafish-node-sdk/tarball/0.1.6
      npm ERR! fetch failed https://github.com/appcelerator/cocoafish-node-sdk/tarball
      /0.1.6
      npm http GET https://github.com/appcelerator/cocoafish-node-sdk/tarball/0.1.6
      npm ERR! fetch failed https://github.com/appcelerator/cocoafish-node-sdk/tarball
      /0.1.6
      npm ERR! Error: SSL Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
      npm ERR! at ClientRequest. (C:Program Filesnodejsnode_modules
      npmnode_modulesrequestmain.js:525:26)
      npm ERR! at ClientRequest.g (events.js:192:14)
      npm ERR! at ClientRequest.EventEmitter.emit (events.js:96:17)
      npm ERR! at HTTPParser.parserOnIncomingClient (http.js:1582:7)
      npm ERR! at HTTPParser.parserOnHeadersComplete [as onHeadersComplete] (http.
      js:111:23)
      npm ERR! at CleartextStream.socketOnData (http.js:1485:20)
      npm ERR! at CleartextStream.CryptoStream._push (tls.js:544:27)
      npm ERR! at SecurePair.cycle (tls.js:898:20)
      npm ERR! at EncryptedStream.CryptoStream.write (tls.js:285:13)
      npm ERR! at Socket.ondata (stream.js:38:26)
      npm ERR! If you need help, you may report this log at:
      npm ERR!
      npm ERR! or email it to:
      npm ERR!

      npm ERR! System Windows_NT 6.1.7601
      npm ERR! command “C:Program Filesnodejs\node.exe” “C:Program Filesnod
      ejsnode_modulesnpmbinnpm-cli.js” “-g” “install” “acs”
      npm ERR! cwd C:Userssaamy
      npm ERR! node -v v0.8.22
      npm ERR! npm -v 1.2.14
      npm ERR!
      npm ERR! Additional logging details can be found in:
      npm ERR! C:Userssaamynpm-debug.log
      npm ERR! not ok code 0

      but have another issue, Simulator is not launching
      https://jira.appcelerator.org/browse/TC-2167

    32. Danny

      @Wei: also does not work for me, see my comment on Jira thread for details

    33. mahesh

      Hi Guys,

      I want to develop blackberry application but I have installed below items successfully.

      1: installer-bbndk-bb10_1_x-macosx-1020-201303191709-201303191501.dmg
      2: BlackBerry10Simulator-Installer-BB10_1_X-1483-Mac-201304131554.dmg
      3: VMware-Fusion-5.0.3-1040386-light.dmg

      installed sdk is 10.1.0.1020

      when i am going to create a new project but it does enable the blackberry option (blackberry is disable).

      Please help me, Thanks in advance

    34. YR

      ListView is supported by Android 3.1 and up. However, Android 2.3 is still very popular.
      It works on my device, but will 2.3 be officially supported?

      • Ingo Muschenetz

        @YR. I am unsure where you got that information. ListView should be supported on Android 2.3, or everywhere that TableView is supported.

    35. holo

      HI

      Managed to install node acs manually on a Windows 8 Pro 64 but “acs login” failed with a [error]undefined error message after entering email and password.

    36. lopezz

      Good work Team Appcelerator. Speed of the listview is definitely a lot faster and the scrolling feels more natural because of this, no lag anymore.

    37. YR

      @Ingo Muschenetz. Thank! It says so on the ListView docs.
      I think it’s very important that we get a a scroll event on ListView, so we can fetch more data and display it when we’re scrolling near the end of the list.

    38. Toni Paris

      The dreaded “ACS Stuck at 30%”

    39. Edgard Zavarezzi

      Can’t update Titanium… what a mess…

      !ENTRY org.eclipse.core.net 1 0 2013-04-29 16:06:05.770
      !MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences

      !ENTRY com.appcelerator.titanium.mobile 4 0 2013-04-29 16:06:17.476
      !MESSAGE (Build 3.0.2.201302191606) [ERROR] com.appcelerator.titanium.mobile/debug/dashboard Unknown SDK tizen

      !ENTRY com.appcelerator.titanium.mobile 4 0 2013-04-29 16:06:17.478
      !MESSAGE (Build 3.0.2.201302191606) [ERROR] com.appcelerator.titanium.mobile/debug/dashboard Unknown SDK mobileweb

      !ENTRY com.appcelerator.titanium.update 4 2 2013-04-29 16:12:04.507
      !MESSAGE Problems occurred when invoking code from plug-in: “com.appcelerator.titanium.update”.
      !STACK 0
      java.lang.NullPointerException
      at com.aptana.core.util.EclipseUtil.showSystemJobs(EclipseUtil.java:368)
      at com.aptana.core.util.EclipseUtil.setSystemForJob(EclipseUtil.java:376)
      at com.aptana.ui.util.UIUtils.showMessageDialogFromBgThread(UIUtils.java:476)
      at com.aptana.ui.util.UIUtils.showMessageDialogFromBgThread(UIUtils.java:396)
      at com.appcelerator.titanium.update.TitaniumSDKUpdater$6.done(TitaniumSDKUpdater.java:908)
      at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:39)
      at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:112)
      at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:152)
      at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:647)
      at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:71)

      !ENTRY org.eclipse.core.jobs 4 2 2013-04-29 16:12:04.510
      !MESSAGE An internal error occurred during: “Installing Titanium Updates…”.
      !STACK 0
      java.lang.NullPointerException
      at com.appcelerator.titanium.nodejs.core.NPMConfigurationComponent.getNodePackageManager(NPMConfigurationComponent.java:175)
      at com.appcelerator.titanium.nodejs.core.NPMConfigurationComponent.install(NPMConfigurationComponent.java:133)
      at com.appcelerator.titanium.update.internal.TitaniumNPMRelease.install(TitaniumNPMRelease.java:47)
      at com.appcelerator.titanium.update.TitaniumSDKUpdater.installTitaniumUpdates(TitaniumSDKUpdater.java:482)
      at com.appcelerator.titanium.update.TitaniumSDKUpdater.access$0(TitaniumSDKUpdater.java:447)
      at com.appcelerator.titanium.update.TitaniumSDKUpdater$5.run(TitaniumSDKUpdater.java:870)
      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
      !SESSION 2013-04-29 16:12:05.247 ———————————————–
      eclipse.buildId=3.1.0.201304151600
      java.version=1.6.0_41
      java.vendor=Apple Inc.
      BootLoader constants: OS=macosx, ARCH=x86, WS=cocoa, NL=en_US
      Framework arguments: -keyring /Users/edgardz/.eclipse_keyring -showlocation
      Command-line arguments: -os macosx -ws cocoa -arch x86 -keyring /Users/edgardz/.eclipse_keyring -consoleLog -showlocation

      !ENTRY org.eclipse.core.net 1 0 2013-04-29 16:12:13.016
      !MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences

      !ENTRY com.appcelerator.titanium.acs.ui 4 0 2013-04-29 16:12:25.299
      !MESSAGE (Build 3.1.0.201304151600) [ERROR] Failed to log into Node.ACS
      !STACK 1
      org.eclipse.core.runtime.CoreException: -2
      at com.aptana.js.internal.core.node.NodePackageManager.list(NodePackageManager.java:394)
      at com.aptana.js.internal.core.node.NodePackageManager.isInstalled(NodePackageManager.java:417)
      at com.appcelerator.titanium.acs.internal.ui.NodeACSStartup$2.run(NodeACSStartup.java:75)
      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
      !SUBENTRY 1 com.aptana.js.core 4 0 2013-04-29 16:12:25.302
      !MESSAGE -2

      !ENTRY com.appcelerator.titanium.mobile 4 0 2013-04-29 16:12:34.260
      !MESSAGE (Build 3.1.0.201304151600) [ERROR] com.appcelerator.titanium.mobile/debug/dashboard Unknown SDK tizen

      !ENTRY com.appcelerator.titanium.mobile 4 0 2013-04-29 16:12:34.265
      !MESSAGE (Build 3.1.0.201304151600) [ERROR] com.appcelerator.titanium.mobile/debug/dashboard Unknown SDK mobileweb

      !ENTRY com.aptana.js.core 4 0 2013-04-29 16:39:57.161
      !MESSAGE (Build 3.1.0.201304151600) [ERROR] Failed to install titanium.

      npm http GET https://registry.npmjs.org/titanium
      npm http GET https://registry.npmjs.org/titanium
      npm http GET https://registry.npmjs.org/titanium
      npm http GET https://registry.npmjs.org/titanium/-/titanium-3.1.0.tgz
      npm ERR! fetch failed https://registry.npmjs.org/titanium/-/titanium-3.1.0.tgz
      npm http GET https://registry.npmjs.org/titanium/-/titanium-3.1.0.tgz
      npm ERR! fetch failed https://registry.npmjs.org/titanium/-/titanium-3.1.0.tgz
      npm http GET https://registry.npmjs.org/titanium/-/titanium-3.1.0.tgz
      npm ERR! fetch failed https://registry.npmjs.org/titanium/-/titanium-3.1.0.tgz
      npm ERR! Error: tunneling socket could not be established, cause=connect ECONNREFUSED
      npm ERR! at ClientRequest.onError (/usr/local/lib/node_modules/npm/node_modules/request/tunnel.js:161:17)
      npm ERR! at ClientRequest.g (events.js:192:14)
      npm ERR! at ClientRequest.EventEmitter.emit (events.js:96:17)
      npm ERR! at Socket.socketErrorListener (http.js:1449:9)
      npm ERR! at Socket.EventEmitter.emit (events.js:96:17)
      npm ERR! at Socket._destroy.self.errorEmitted (net.js:329:14)
      npm ERR! at process.startup.processNextTick.process._tickCallback (node.js:245:9)
      npm ERR! If you need help, you may report this log at:
      npm ERR!
      npm ERR! or email it to:
      npm ERR!

      npm ERR! System Darwin 11.4.2
      npm ERR! command “node” “/usr/local/bin/npm” “-g” “install” “titanium” “–color” “false” “–proxy” “http://127.0.0.1:8888”
      npm ERR! cwd /Applications/Titanium Studio/TitaniumStudio.app/Contents/MacOS
      npm ERR! node -v v0.8.22
      npm ERR! npm -v 1.2.14
      npm ERR! code ECONNRESET
      npm ERR!
      npm ERR! Additional logging details can be found in:
      npm ERR! /Applications/Titanium Studio/TitaniumStudio.app/Contents/MacOS/npm-debug.log
      npm ERR! not ok code 0

      !ENTRY com.aptana.js.core 4 0 2013-04-29 16:42:18.000
      !MESSAGE (Build 3.1.0.201304151600) [ERROR] Failed to install alloy.

      npm http GET https://registry.npmjs.org/alloy
      npm http GET https://registry.npmjs.org/alloy
      npm http GET https://registry.npmjs.org/alloy
      npm http GET https://registry.npmjs.org/alloy/-/alloy-1.1.1.tgz
      npm ERR! fetch failed https://registry.npmjs.org/alloy/-/alloy-1.1.1.tgz
      npm http GET https://registry.npmjs.org/alloy/-/alloy-1.1.1.tgz
      npm ERR! fetch failed https://registry.npmjs.org/alloy/-/alloy-1.1.1.tgz
      npm http GET https://registry.npmjs.org/alloy/-/alloy-1.1.1.tgz
      npm ERR! fetch failed https://registry.npmjs.org/alloy/-/alloy-1.1.1.tgz
      npm ERR! Error: tunneling socket could not be established, cause=connect ECONNREFUSED
      npm ERR! at ClientRequest.onError (/usr/local/lib/node_modules/npm/node_modules/request/tunnel.js:161:17)
      npm ERR! at ClientRequest.g (events.js:192:14)
      npm ERR! at ClientRequest.EventEmitter.emit (events.js:96:17)
      npm ERR! at Socket.socketErrorListener (http.js:1449:9)
      npm ERR! at Socket.EventEmitter.emit (events.js:96:17)
      npm ERR! at Socket._destroy.self.errorEmitted (net.js:329:14)
      npm ERR! at process.startup.processNextTick.process._tickCallback (node.js:245:9)
      npm ERR! If you need help, you may report this log at:
      npm ERR!
      npm ERR! or email it to:
      npm ERR!

      npm ERR! System Darwin 11.4.2
      npm ERR! command “node” “/usr/local/bin/npm” “-g” “install” “alloy” “–color” “false” “–proxy” “http://127.0.0.1:8888”
      npm ERR! cwd /Applications/Titanium Studio/TitaniumStudio.app/Contents/MacOS
      npm ERR! node -v v0.8.22
      npm ERR! npm -v 1.2.14
      npm ERR! code ECONNRESET
      npm ERR!
      npm ERR! Additional logging details can be found in:
      npm ERR! /Applications/Titanium Studio/TitaniumStudio.app/Contents/MacOS/npm-debug.log
      npm ERR! not ok code 0

      !ENTRY com.aptana.js.core 4 0 2013-04-29 16:43:28.718
      !MESSAGE (Build 3.1.0.201304151600) [ERROR] Failed to install acs.

      npm http GET https://registry.npmjs.org/acs
      npm http GET https://registry.npmjs.org/acs
      npm http GET https://registry.npmjs.org/acs
      npm ERR! Error: tunneling socket could not be established, cause=connect ECONNREFUSED
      npm ERR! at ClientRequest.onError (/usr/local/lib/node_modules/npm/node_modules/request/tunnel.js:161:17)
      npm ERR! at ClientRequest.g (events.js:192:14)
      npm ERR! at ClientRequest.EventEmitter.emit (events.js:96:17)
      npm ERR! at Socket.socketErrorListener (http.js:1449:9)
      npm ERR! at Socket.EventEmitter.emit (events.js:96:17)
      npm ERR! at Socket._destroy.self.errorEmitted (net.js:329:14)
      npm ERR! at process.startup.processNextTick.process._tickCallback (node.js:245:9)
      npm ERR! If you need help, you may report this log at:
      npm ERR!
      npm ERR! or email it to:
      npm ERR!

      npm ERR! System Darwin 11.4.2
      npm ERR! command “node” “/usr/local/bin/npm” “-g” “install” “acs” “–color” “false” “–proxy” “http://127.0.0.1:8888”
      npm ERR! cwd /Applications/Titanium Studio/TitaniumStudio.app/Contents/MacOS
      npm ERR! node -v v0.8.22
      npm ERR! npm -v 1.2.14
      npm ERR! code ECONNRESET
      npm ERR!
      npm ERR! Additional logging details can be found in:
      npm ERR! /Applications/Titanium Studio/TitaniumStudio.app/Contents/MacOS/npm-debug.log
      npm ERR! not ok code 0

      !ENTRY com.appcelerator.titanium.update 4 4 2013-04-29 16:43:28.724
      !MESSAGE Error encountered during update
      !SUBENTRY 1 com.aptana.js.core 4 0 2013-04-29 16:43:28.724
      !MESSAGE Failed to install titanium. Please see the Studio log for more information.
      !SUBENTRY 1 com.aptana.js.core 4 0 2013-04-29 16:43:28.724
      !MESSAGE Failed to install alloy. Please see the Studio log for more information.
      !SUBENTRY 1 com.aptana.js.core 4 0 2013-04-29 16:43:28.724
      !MESSAGE Failed to install acs. Please see the Studio log for more information.

      !ENTRY org.eclipse.core.jobs 2 2 2013-04-29 16:43:51.234
      !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: com.aptana.usage.internal.DefaultAnalyticsEventHandler$1

      !ENTRY org.eclipse.core.jobs 2 2 2013-04-29 16:43:51.235
      !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: com.aptana.usage.internal.DefaultAnalyticsEventHandler$1
      !SESSION 2013-04-29 16:44:00.192 ———————————————–
      eclipse.buildId=unknown
      java.version=1.6.0_41
      java.vendor=Apple Inc.
      BootLoader constants: OS=macosx, ARCH=x86, WS=cocoa, NL=en_US
      Framework arguments: -keyring /Users/edgardz/.eclipse_keyring -showlocation
      Command-line arguments: -os macosx -ws cocoa -arch x86 -keyring /Users/edgardz/.eclipse_keyring -consoleLog -showlocation

      !ENTRY org.eclipse.core.resources 2 10035 2013-04-29 16:44:02.671
      !MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

      !ENTRY org.eclipse.core.net 1 0 2013-04-29 16:44:08.380
      !MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences

      !ENTRY com.appcelerator.titanium.acs.ui 4 0 2013-04-29 16:44:20.770
      !MESSAGE (Build 3.1.0.201304151600) [ERROR] Failed to log into Node.ACS
      !STACK 1
      org.eclipse.core.runtime.CoreException: -2
      at com.aptana.js.internal.core.node.NodePackageManager.list(NodePackageManager.java:394)
      at com.aptana.js.internal.core.node.NodePackageManager.isInstalled(NodePackageManager.java:417)
      at com.appcelerator.titanium.acs.internal.ui.NodeACSStartup$2.run(NodeACSStartup.java:75)
      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
      !SUBENTRY 1 com.aptana.js.core 4 0 2013-04-29 16:44:20.774
      !MESSAGE -2

      !ENTRY com.appcelerator.titanium.mobile 4 0 2013-04-29 16:44:27.463
      !MESSAGE (Build 3.1.0.201304151600) [ERROR] com.appcelerator.titanium.mobile/debug/dashboard Unknown SDK tizen

      !ENTRY com.appcelerator.titanium.mobile 4 0 2013-04-29 16:44:27.465
      !MESSAGE (Build 3.1.0.201304151600) [ERROR] com.appcelerator.titanium.mobile/debug/dashboard Unknown SDK mobileweb

      !ENTRY org.eclipse.ui 4 4 2013-04-29 16:45:01.179
      !MESSAGE An internal error has occurred.
      !STACK 0
      org.eclipse.swt.SWTException: Widget is disposed
      at org.eclipse.swt.SWT.error(SWT.java:4282)
      at org.eclipse.swt.SWT.error(SWT.java:4197)
      at org.eclipse.swt.SWT.error(SWT.java:4168)
      at org.eclipse.swt.widgets.Widget.error(Widget.java:774)
      at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:568)
      at org.eclipse.swt.widgets.Control.setEnabled(Control.java:3668)
      at com.appcelerator.titanium.ui.ide.tiappEditor.ModulesTable.updateControlsEnablement(ModulesTable.java:311)
      at com.appcelerator.titanium.ui.ide.tiappEditor.TiAppModulesSection.updateControlsEnablement(TiAppModulesSection.java:158)
      at com.appcelerator.titanium.ui.ide.tiappEditor.ModulesWatcher$1$1.runInUIThread(ModulesWatcher.java:103)
      at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95)
      at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
      at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
      at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938)
      at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3615)
      at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
      at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
      at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
      at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
      at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
      at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
      at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
      at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125)
      at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
      at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
      at org.eclipse.equinox.launcher.Main.run(Main.java:1410)

      !ENTRY org.eclipse.osgi 2 1 2013-04-29 16:45:30.899
      !MESSAGE NLS missing message: NodeTitaniumSDKCommandsHandler_mobileWebBuild in: com.appcelerator.titanium.mobile.cli.messages

      !ENTRY com.appcelerator.titanium.nodejs.core 4 0 2013-04-29 16:45:51.201
      !MESSAGE (Build 3.1.0.201304151600) [ERROR] Could not instantiate a release notes provider
      !STACK 1
      org.eclipse.core.runtime.CoreException: Plug-in “com.appcelerator.titanium.mobile.ui” was unable to instantiate class “com.appcelerator.titanium.mobile.internal.ui.CLIReleaseNotesProvider”.
      at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194)
      at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:186)
      at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
      at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
      at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
      at com.appcelerator.titanium.nodejs.core.NPMConfigurationComponent.getReleaseNotesProvider(NPMConfigurationComponent.java:159)
      at com.appcelerator.titanium.update.internal.TitaniumNPMRelease.getReleaseNotesProvider(TitaniumNPMRelease.java:58)
      at com.appcelerator.titanium.update.TitaniumRelease.getReleaseNotesText(TitaniumRelease.java:72)
      at com.appcelerator.titanium.update.ui.TitaniumUpdatePage.updateDetails(TitaniumUpdatePage.java:441)
      at com.appcelerator.titanium.update.ui.TitaniumUpdatePage.createControl(TitaniumUpdatePage.java:506)
      at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174)
      at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
      at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
      at org.eclipse.jface.window.Window.create(Window.java:431)
      at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
      at com.appcelerator.titanium.update.ui.TitaniumUpdateWizardDialog.open(TitaniumUpdateWizardDialog.java:66)
      at com.appcelerator.titanium.update.TitaniumUpdateStartup$1$1.run(TitaniumUpdateStartup.java:67)
      at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
      at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
      at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938)
      at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3615)
      at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
      at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
      at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
      at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
      at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
      at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
      at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
      at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125)
      at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
      at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
      at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
      Caused by: java.lang.IllegalAccessException: Class org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI can not access a member of class com.appcelerator.titanium.mobile.internal.ui.CLIReleaseNotesProvider with modifiers “”
      at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65)
      at java.lang.Class.newInstance0(Class.java:351)
      at java.lang.Class.newInstance(Class.java:310)
      at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
      … 39 more
      !SUBENTRY 1 org.eclipse.equinox.registry 4 1 2013-04-29 16:45:51.203
      !MESSAGE Plug-in “com.appcelerator.titanium.mobile.ui” was unable to instantiate class “com.appcelerator.titanium.mobile.internal.ui.CLIReleaseNotesProvider”.
      !STACK 0
      java.lang.IllegalAccessException: Class org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI can not access a member of class com.appcelerator.titanium.mobile.internal.ui.CLIReleaseNotesProvider with modifiers “”
      at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65)
      at java.lang.Class.newInstance0(Class.java:351)
      at java.lang.Class.newInstance(Class.java:310)
      at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
      at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
      at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
      at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
      at com.appcelerator.titanium.nodejs.core.NPMConfigurationComponent.getReleaseNotesProvider(NPMConfigurationComponent.java:159)
      at com.appcelerator.titanium.update.internal.TitaniumNPMRelease.getReleaseNotesProvider(TitaniumNPMRelease.java:58)
      at com.appcelerator.titanium.update.TitaniumRelease.getReleaseNotesText(TitaniumRelease.java:72)
      at com.appcelerator.titanium.update.ui.TitaniumUpdatePage.updateDetails(TitaniumUpdatePage.java:441)
      at com.appcelerator.titanium.update.ui.TitaniumUpdatePage.createControl(TitaniumUpdatePage.java:506)
      at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174)
      at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
      at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
      at org.eclipse.jface.window.Window.create(Window.java:431)
      at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
      at com.appcelerator.titanium.update.ui.TitaniumUpdateWizardDialog.open(TitaniumUpdateWizardDialog.java:66)
      at com.appcelerator.titanium.update.TitaniumUpdateStartup$1$1.run(TitaniumUpdateStartup.java:67)
      at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
      at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
      at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938)
      at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3615)
      at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
      at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
      at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
      at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
      at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
      at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
      at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
      at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125)
      at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
      at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
      at org.eclipse.equinox.launcher.Main.run(Main.java:1410)

      !ENTRY com.appcelerator.titanium.acs.ui 4 0 2013-04-29 16:48:24.700
      !MESSAGE (Build 3.1.0.201304151600) [ERROR] Failed to log into Node.ACS
      !STACK 1
      org.eclipse.core.runtime.CoreException: -2
      at com.aptana.js.internal.core.node.NodePackageManager.list(NodePackageManager.java:394)
      at com.aptana.js.internal.core.node.NodePackageManager.isInstalled(NodePackageManager.java:417)
      at com.appcelerator.titanium.acs.internal.ui.NodeACSStartup$2.run(NodeACSStartup.java:75)
      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
      !SUBENTRY 1 com.aptana.js.core 4 0 2013-04-29 16:48:24.700
      !MESSAGE -2

      !ENTRY com.appcelerator.titanium.nodejs.core 4 0 2013-04-29 16:50:28.288
      !MESSAGE (Build 3.1.0.201304151600) [ERROR] Could not instantiate a release notes provider
      !STACK 1
      org.eclipse.core.runtime.CoreException: Plug-in “com.appcelerator.titanium.mobile.ui” was unable to instantiate class “com.appcelerator.titanium.mobile.internal.ui.CLIReleaseNotesProvider”.
      at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194)
      at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:186)
      at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
      at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
      at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
      at com.appcelerator.titanium.nodejs.core.NPMConfigurationComponent.getReleaseNotesProvider(NPMConfigurationComponent.java:159)
      at com.appcelerator.titanium.update.internal.TitaniumNPMRelease.getReleaseNotesProvider(TitaniumNPMRelease.java:58)
      at com.appcelerator.titanium.update.TitaniumRelease.getReleaseNotesText(TitaniumRelease.java:72)
      at com.appcelerator.titanium.update.ui.TitaniumUpdatePage.updateDetails(TitaniumUpdatePage.java:441)
      at com.appcelerator.titanium.update.ui.TitaniumUpdatePage.createControl(TitaniumUpdatePage.java:506)
      at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174)
      at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
      at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
      at org.eclipse.jface.window.Window.create(Window.java:431)
      at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
      at com.appcelerator.titanium.update.ui.TitaniumUpdateWizardDialog.open(TitaniumUpdateWizardDialog.java:66)
      at com.appcelerator.titanium.update.handler.TitaniumUpdateHandler$1$1.run(TitaniumUpdateHandler.java:67)
      at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
      at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
      at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938)
      at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3615)
      at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
      at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
      at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
      at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
      at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
      at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
      at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
      at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125)
      at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
      at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
      at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
      Caused by: java.lang.IllegalAccessException: Class org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI can not access a member of class com.appcelerator.titanium.mobile.internal.ui.CLIReleaseNotesProvider with modifiers “”
      at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65)
      at java.lang.Class.newInstance0(Class.java:351)
      at java.lang.Class.newInstance(Class.java:310)
      at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
      … 39 more
      !SUBENTRY 1 org.eclipse.equinox.registry 4 1 2013-04-29 16:50:28.289
      !MESSAGE Plug-in “com.appcelerator.titanium.mobile.ui” was unable to instantiate class “com.appcelerator.titanium.mobile.internal.ui.CLIReleaseNotesProvider”.
      !STACK 0
      java.lang.IllegalAccessException: Class org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI can not access a member of class com.appcelerator.titanium.mobile.internal.ui.CLIReleaseNotesProvider with modifiers “”
      at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65)
      at java.lang.Class.newInstance0(Class.java:351)
      at java.lang.Class.newInstance(Class.java:310)
      at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
      at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
      at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
      at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
      at com.appcelerator.titanium.nodejs.core.NPMConfigurationComponent.getReleaseNotesProvider(NPMConfigurationComponent.java:159)
      at com.appcelerator.titanium.update.internal.TitaniumNPMRelease.getReleaseNotesProvider(TitaniumNPMRelease.java:58)
      at com.appcelerator.titanium.update.TitaniumRelease.getReleaseNotesText(TitaniumRelease.java:72)
      at com.appcelerator.titanium.update.ui.TitaniumUpdatePage.updateDetails(TitaniumUpdatePage.java:441)
      at com.appcelerator.titanium.update.ui.TitaniumUpdatePage.createControl(TitaniumUpdatePage.java:506)
      at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174)
      at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
      at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
      at org.eclipse.jface.window.Window.create(Window.java:431)
      at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)
      at com.appcelerator.titanium.update.ui.TitaniumUpdateWizardDialog.open(TitaniumUpdateWizardDialog.java:66)
      at com.appcelerator.titanium.update.handler.TitaniumUpdateHandler$1$1.run(TitaniumUpdateHandler.java:67)
      at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
      at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
      at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938)
      at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3615)
      at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
      at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
      at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
      at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
      at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
      at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
      at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
      at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125)
      at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
      at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
      at org.eclipse.equinox.launcher.Main.run(Main.java:1410)

      !ENTRY com.aptana.js.core 4 0 2013-04-29 16:51:48.450
      !MESSAGE (Build 3.1.0.201304151600) [ERROR] Failed to install acs.

      npm http GET https://registry.npmjs.org/acs
      npm http GET https://registry.npmjs.org/acs
      npm http GET https://registry.npmjs.org/acs
      npm ERR! Error: tunneling socket could not be established, cause=connect ECONNREFUSED
      npm ERR! at ClientRequest.onError (/usr/local/lib/node_modules/npm/node_modules/request/tunnel.js:161:17)
      npm ERR! at ClientRequest.g (events.js:192:14)
      npm ERR! at ClientRequest.EventEmitter.emit (events.js:96:17)
      npm ERR! at Socket.socketErrorListener (http.js:1449:9)
      npm ERR! at Socket.EventEmitter.emit (events.js:96:17)
      npm ERR! at Socket._destroy.self.errorEmitted (net.js:329:14)
      npm ERR! at process.startup.processNextTick.process._tickCallback (node.js:245:9)
      npm ERR! If you need help, you may report this log at:
      npm ERR!
      npm ERR! or email it to:
      npm ERR!

      npm ERR! System Darwin 11.4.2
      npm ERR! command “node” “/usr/local/bin/npm” “-g” “install” “acs” “–color” “false” “–proxy” “http://127.0.0.1:8888”
      npm ERR! cwd /Applications/Titanium Studio/TitaniumStudio.app/Contents/MacOS
      npm ERR! node -v v0.8.22
      npm ERR! npm -v 1.2.14
      npm ERR! code ECONNRESET
      npm ERR!
      npm ERR! Additional logging details can be found in:
      npm ERR! /Applications/Titanium Studio/TitaniumStudio.app/Contents/MacOS/npm-debug.log
      npm ERR! not ok code 0

      !ENTRY com.appcelerator.titanium.update 4 4 2013-04-29 16:51:48.455
      !MESSAGE Error encountered during update
      !SUBENTRY 1 com.aptana.js.core 4 0 2013-04-29 16:51:48.455
      !MESSAGE Failed to install acs. Please see the Studio log for more information.

      !ENTRY org.eclipse.ui 4 4 2013-04-29 16:53:14.145
      !MESSAGE Unable to create menu item “com.appcelerator.titanium.mobile.command.install.blackberry”, command “com.appcelerator.titanium.mobile.command.install.blackberry” not defined

      !ENTRY org.eclipse.ui 4 4 2013-04-29 16:53:20.264
      !MESSAGE Unable to create menu item “com.appcelerator.titanium.mobile.command.install.blackberry”, command “com.appcelerator.titanium.mobile.command.install.blackberry” not defined

      !ENTRY org.eclipse.ui 4 4 2013-04-29 16:53:28.778
      !MESSAGE An internal error has occurred.
      !STACK 0
      org.eclipse.swt.SWTException: Widget is disposed
      at org.eclipse.swt.SWT.error(SWT.java:4282)
      at org.eclipse.swt.SWT.error(SWT.java:4197)
      at org.eclipse.swt.SWT.error(SWT.java:4168)
      at org.eclipse.swt.widgets.Widget.error(Widget.java:774)
      at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:568)
      at org.eclipse.swt.widgets.Control.setEnabled(Control.java:3668)
      at com.appcelerator.titanium.ui.ide.tiappEditor.ModulesTable.updateControlsEnablement(ModulesTable.java:311)
      at com.appcelerator.titanium.ui.ide.tiappEditor.TiAppModulesSection.updateControlsEnablement(TiAppModulesSection.java:158)
      at com.appcelerator.titanium.ui.ide.tiappEditor.ModulesWatcher$1$1.runInUIThread(ModulesWatcher.java:103)
      at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95)
      at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
      at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
      at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3938)
      at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3615)
      at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
      at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
      at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
      at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
      at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
      at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
      at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
      at com.appcelerator.titanium.rcp.IDEApplication.start(IDEApplication.java:125)
      at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
      at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
      at org.eclipse.equinox.launcher.Main.run(Main.java:1410)

    40. timmy

      About this 30% Node.ASC thing, the problem i am facing as well due to the 3.1 update.

      i got this message with (sudo npm -g install acs);

      gyp WARN EACCES user “root” does not have permission to access the dev dir “/home/henkie/.node-gyp/0.10.5”
      gyp WARN EACCES attempting to reinstall using temporary dev dir “/usr/lib/node_modules/acs/node_modules/socket.io/node_modules/redis/node_modules/hiredis/.node-gyp”

      could this be the problem?

    41. Rudolf Ziegaus

      I’ve got a problem when I try to import one of the sample projects. I get the follwing error:

      Cloning into ‘D:USERDATAziegauruWorkspacesTitaniumKitchen Sink’…
      fatal: Unable to look up github.com (port 9418) (Der angegebene Host ist unbekannt. )

      This error happens with all sample projects (Geocoder, …).

      And yes, I am behind a proxy, however I have configured the proxy to use my userid and password correctly.

      Any idea?

      Thanx,

      Rudi

    42. Ingo Muschenetz

      @Edgard. I’m sorry to hear you are having issues. it’s impossible to diagnose using a stack trace pasted that way. Can you please attach it to a JIRA ticket with your environment so we can better diagnose?

    43. @Rudolf – Could you open a ticket at https://jira.appcelerator.org/browse/TISTUD? The following steps will help us diagnose the issue as well:

      1. In Titanium Studio, open Preferences > Studio > Troubleshooting page;
      2. Change “Debug Level” to All and make com.aptana.core/debug/shell entry checked;
      3. Hit OK and restart Studio;
      4. Try importing the sample to re-generate the error;
      5. Open the Studio log via Help > Studio > View Log File;
      6. Attach the log content in the JIRA ticket.

      Thanks very much.

    44. Jiae

      I want to know ,last file “Node.ACS(required)” version 1.0.14,when the update progress at 36% ,there is disconnect ,and the message:“Error encountered during update
      Failed to install acs. Please see the Studio log for more information.” please help me.Thank you very much!

    Comments are closed.

    Sign up for updates!

    Become a mobile leader. Take the first step to scale mobile innovation throughout your enterprise.
    Get in touch
    computer and tablet showing Appcelerator software
    Start free, grow from there.
    0 Flares Twitter 0 Facebook 0 Google+ 0 LinkedIn 0 Email -- 0 Flares ×