3.1.2 Release Candidate of Titanium SDK Now Available

DNA molecules. 3d rendering

We’re pleased to announce the release candidate of 3.1.2, an update to our 3.1.1 version of the Titanium SDK. Version 3.1.2 brings numerous fixes and improvements across both products, as well as preliminary support for iOS 7, Android 4.3, and the GA version of our BlackBerry support. Today, we’re asking you to help test out the release and provide feedback before it becomes generally available in mid-August.

Note: This is a pre-production release, and as such may contain regressions or other issues. Please do not use it in production, and keep backups of all important projects and data. If you find an issue, please report it in JIRA with a reproducible test case. We ask you provide feedback by Wednesday, 8/7.

NPM Packages

Note: You may need to use ‘sudo’ before these terminal commands on OSX and Linux

npm install -g alloy@1.2.0-alpha4
npm install -g titanium@3.1.2-alpha

To revert back to stable versions:

npm remove -g titanium
npm install -g titanium
npm remove -g alloy
npm install -g alloy

Updates in Titanium 3.1.2

Read the complete Release Notes. A full list of updates is available here.

iOS 7 Preliminary support

Official support for iOS 7 will come in version 3.1.3, scheduled to be released in September or October, based on Apple’s timing of the official release of iOS 7. In the meantime, 3.1.2 will allow you to begin developing apps against iOS 7, and to help us find any remaining issues we need to tackle. You can view a list of current outstanding iOS 7 tickets here:

Android 4.3 Support

This release includes preliminary support for Android 4.3. Full certification will come as part of the 3.1.2 GA release with a complete testing pass.

BlackBerry GA

We are pleased and proud to announce the general availability version of our BlackBerry platform in this release. More announcements will come around this particular milestone, so stay tuned!

Google Cloud Messaging Default for Android push updates

By default, a new application will use Google Cloud Messaging (GCM) as the default push notification protocol for Android. If you have an existing application that uses the MQTT protocol, you either need to transition your application to use GCM or set the acs-push-type property in the tiapp.xml file to mqtt.

Corrected behavior when enabling “do not keep activities” developer option

Having heard you loud and clear, we’ve addressed a important issue for Titanium developers. Fixing this required a major rewrite of some of our windowing architecture on Android. Android 4.0 and greater devices have an option called Do not keep activities under the Developer Options menu. When this option is enabled, the Android OS will destroy an activity as soon as it is stopped. It is intended to help developers debug their apps. For example, it can simulate the case that Android will kill an activity in the background due to memory pressure. In normal use, it is not recommended to turn this option on because this may lead to unexpected issues in your apps, such as freezes, force closes and reboots. Enabling this option causes Titanium applications to close immediately when the first activity is launched (TIMOB-12939).

This issue has been fixed in release 3.1.2 and requires that the root window’s exitOnClose property be set totrue to properly close the application when this option is enabled.


    • Can you confirm that the steps to reproduce or identical or provide the new steps that fail for you? I’ll then be happy to reopen the bug.

    • If you try downloading that URL in your browser, does it work for you? It downloads fine for me.

Comments are closed.