GA Release of CLI 5.2, Titanium 5.2 and Studio 4.5

Product Release

We are happy to announce the immediate availability of the Appcelerator CLI 5.2.0, Titanium SDK 5.2.0 and Appcelerator Studio 4.5.0.

We’d like to thank the Appcelerator Community members who contributed to this release as well as those who have tested the RC from last week.

New Features

Some of the most noteworthy of all 34 new features are:

Titanium 5.2.0 is also the first GA that supports Hyperloop, although the Hyperloop Module itself remains in beta.

We’ve released a sample app to walk you through all new features.

Release Notes & Fixed Issues

These releases include 213 bug fixes, 67 improvements and 34 new features. For a more detailed overview, known issues and closed tickets see the following links:

Google Security Alert: This release does NOT include a fix for the Google Security Alert because our tests have shown that only Titanium 4 and older are effected.

Update from Appcelerator Studio

If you changed the update type to Release Candidate Build to get last week’s RC, then you can switch back to Stable Release now and check for updates.

Known Issues: The prompt for the CLI update does not display the release notes (TISTUD-7996) which results in an error (TISTUD-7995). Also, if you have a nightly build of a SDK version later than 5.2 installed, you might need to (re)move this for Studio to find 5.2.0.GA. Or update the SDK form the CLI. Finally, be aware that you need to use LiveView once in Studio before you can use it from the CLI again after the update (TISTUD-7746).

Update from Command Line

Studio will update the CLI and SDK for you. To update them from the command line:

[sudo] npm install -g appcelerator
appc setup

Titanium & Alloy CLI

The Appcelerator CLI contains Titanium CLI 5.0.6 (2016-01-14) and Alloy CLI 1.7.33 (2016-01-15). If you are using the stand-alone CLIs and haven’t updated them lately, then you can get these versions from the command line:

[sudo] npm install -g titanium alloy

Reporting Bugs

If you run into any issues that seem related to the updates, please report them on JIRA. First check if it’s a known issue you can watch. If you can’t find an existing ticket, then create one in the Appcelerator Community (AC) project and include as much relevant information as you can.

You can leave general comments as a reply to this blog post.


  1. Hi !

    Thanks for this new update 🙂

    I have some questions :

    – What is the release cycle ? Bimonthly ? Will there be something more “regular” ?
    – Does your build process versioning follow the semantic versioning ? If I’m in 5.0 could I upgrade without any risks to 5.2 for instance ?
    If yes you should add it in your doc I think
    – Do you plan to support es6 feature in any way ? I know that react native does it ! It could be very nice if you add this in the build process (with Babel for instance)
    – With that in mind it could be very nice to “Promise” http request directly (return a promise but still allow to pass callback functions, like mongoose does)
    – Do you also plan to update your dependencies ? Like underscore ?
    – I could be very nice if “require” look into the “node_modules” (with also “lib” of course) without doing some tricks as we could use NPM for ours dependencies !
    – Why a basic “Hello word” app is so big ? Like 20 MB on my Android phone

    Thank you !

    • Hi Jérémy, good to hear you love the new release. And thanks for your questions.

      – We have a release almost every other week, but I assume you mean for minor/major releases of the Titanium SDK. That is about two to three months at the moment. We’re always trying to get that down as much as we can.
      – Yes, we try to follow semantic versioning since Titanium 4. A good point that we should mention that.
      – We are refactoring the Titanium build process for the releases in Q3 and Q4 and ES6 support is one of the things we would like to introduce.
      – The above would also mean we can start supporting promises in our async APIs, although this will probably not happen overnight.
      – Since Alloy 1.6 you can opt-in for Backbone 1.1.2. It’s not the default because it introduced a breaking change. We also have thought about replacing Underscore with Lodash, but now those projects are actually merging. Did you know you can easily override the builtin versions of libraries by adding the versions you want to app/lib/alloy?
      – As part of the refactoring of the build process we’re also looking into better support for dependency management.
      – Almost all of that 20MB is the V8 engine we need for all 3 supported CPU architectures. Unfortunately we cannot rely on the engines that ship with the thousands of Android distributions out there. Also see my answer on the Q&A.

      Great questions Jérémy!

      • Damn !
        Thank you for this very fast answer 😀

        I have learn a lot !
        Very happy to hear that, I will probably the first to test this es6 support :p

    • The Appcelerator CLI consists of two parts. The part you install via NPM which for this release was updated to 4.2.3. And the part that you install can switch between using appc use, which is now at 5.1.0 and what we normally refer to as “the CLI”. If you run appc -v -o json you can see both version numbers.

  2. Thanks for the new SDK!

    I have some questions around MenuPopup.

    Will this work inside a WebView, particularly to position the menu relative to an item inside the WebView?

    Also can the items include other views – so that we could show an image as a menu item for example? Similar to iBooks for example with the highlight color options in the menu…

    • Look at the WebView as a in-app browser. So just like in Safari you can select text and a MenuPopup will appear to cut/copy/etc. Apart from these built-in features of a WebView, you cannot mix and match HTML UI and native UI components.

      ATM the MenuPopup does not support icons and I actually don’t see this documented in the iOS API either so it might not be exposed at all. You could create a feature request JIRA ticket to have us look into it a bit more.

  3. Am I the only one who faces appcelerator Latest version hangs like crazy which is not allowing me to work on anything. Any insight on this issue I have 8 GB Ram and appcelerator studio when ever I open it have a good heap space but hangs like crazy and going on non-responding mode. Is there is any fix on that ?

    • That must be frustrating! Could you check your Studio logs (Help > Studio > View Logs) right after it hung and you managed to get in? Please check if there are helpful messages there to include in a JIRA ticket.

Comments are closed.