GA Release of Titanium SDK 5.2.2 and CLI 5.2.2 including Alloy 1.8.5

Circuit board and shield icon on blue background with digital code

We are happy to announce the immediate availability of the Titanium SDK 5.2.2 and the Appcelerator CLI 5.2.2, which includes an update from Alloy 1.8.2 to 1.8.5.


  • TIMOB-20627 – Fixes an issue that causes iOS app to be rejected by Apple because of a missing macro.
  • Fixes several parity issues between Alloy model and collection data binding and subsequent issues.

Known Issue

  • ALOY-1480 – Data binding always returns string values. If your model transformer returns objects as properties, please stick with Alloy 1.7.35 (AppC CLI 5.2.0) for now.

More Details

For more details see the following links:

Update from Appcelerator Studio

Make sure you have the update type to Stable Release and check for updates.

Update from the command line

If you haven’t updated the Appcelerator CLI Installer to 4.2.4 yet:

[sudo] npm install -g appcelerator

To update the CLI Core Package and get Titanium SDK 5.2.2:

appc setup

Update stand-alone Alloy CLI

The Appcelerator CLI Core Package 5.2.2 includes Titanium CLI 5.0.6 (2016-01-14) and an update from Alloy 1.8.2 to 1.8.5. If you are using the global stand-alone Titanium and Alloy CLIs you can update to the latest versions with:

[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 (INBOX) (AC) project and include as much relevant information as you can.

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


  1. I had create simple window and open it. When run from latest 5.2.2 sdk it shows runtime error.

    — removed log —

    But same program works in 4.0.0 sdk, please check it

    • Hi Manoj, It’s a one-year-leap from 4.0 to 5.2.2. Did you check the (major) release notes for breaking changes? Please create a JIRA ticket and reproducible test case, steps and environment for any bugs you might run into.

Comments are closed.