3.1.1 Release Candidate of Titanium SDK/Studio Now Available

3d abstract architecture background

We’re pleased to announce the release candidate of an update to our 3.1.0 version of Titanium SDK/Studio. Version 3.1.1 brings hundreds of fixes and improvements across both products. Today, we’re asking you to help test out the release and provide feedback before it becomes generally available in early June.

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, 5/29.

How to Update

To update Studio, please visit https://preview.appcelerator.com and follow the instructions to update to the RC stream, or to download a new install.

NPM Packages

Note: You may need to use ‘sudo’ before these terminal commands on OSX and Linux
npm install -g alloy@1.1.3-alpha
npm install -g titanium@3.1.1-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.1

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

Changes in supported OS versions

3.1.1 now has a minimum supported Android version of 2.3.3 (API level 10). The minimum iOS supported version is 5.x, which requires Xcode 4.3 or later.

API Changes

We’ve updated Titanium.Calendar, and deprecated Titanium.Android.Calendar.

Tooling updates

Support for Android r22 tooling. See Updating to Android r22 Tools for information about supporting older SDKs. Note that this beta still has some issues with r22 tooling on Windows, but this will be addressed in the final release.

Google Maps Support

We added a new userLocationButton property and updated the regionchanged event.

BlackBerry Support

We’ve folded in the latest version of our BlackBerry platform to this release. It’s no longer a separate download.

1 COMMENT

  1. With this release, there seems to be an issue with running on Android.
    ~~~
    Titanium Command-Line Interface, CLI version 3.1.0, Titanium SDK version 3.1.1.v20130523143543
    Copyright (c) 2012-2013, Appcelerator, Inc. All Rights Reserved.
    Please report bugs to http://jira.appcelerator.org/
    [INFO] : Running build process: python “/Users/theUser/Library/Application Support/Titanium/mobilesdk/osx/3.1.1.v20130523143543/android/builder.py” “install” “AppName” “/Users/theUser/android-sdks” “/Users/theUser/Documents/Titanium/AppName” “com.bundle.appname” “5”
    [INFO] logfile = /Users/theUser/Documents/Titanium/AppName/build.log
    [ERROR] : Build process exited with code 1
    [ERROR] : Project failed to build after 2s 111ms
    ~~~

    • @Joe, can you please file a JIRA ticket with the steps to reproduce and the contents of the log file /Users/theUser/Documents/Titanium/AppName/build.log?

  2. How come iOS 5 is now the minimum version supported as Xcode 4.6 supports down to 4.3 iOS and titanium supports Xcode back to 4 3.

    Shouldn’t the default support be iOS 4 3 and higher if Xcode itself supports this, or is there another reason for iOS 5 being the minimum for titanium?

    • @malcolm. We continually update our official support matrix in line with the active percentages of devices with a particular OS out in the wild. The goal is to focus more resources on the most highly-trafficked OS versions. With 4.X devices having now dipped into the single digits, and iOS 7 coming out soon, we determined 3.1.1 was an appropriate time to make this change.

  3. Hi all,
    I have a big problem since the install 3.1.1. I have also instal the SDK android 2.3.3.

    When i create a new simple project, and i install on my device the build is succesfull, my application launches the splash screen and after my application is stopped.
    The configuration for android SDK is 2.3.3 and the SDK titanium is 3.1.1GA , but nothing

    And for all my apps i have this problem.
    For iOS it’s ok …

    Thank you for your help.

    • @Fred. If you can reproduce the issue, please file a JIRA ticket with the build logs and we will take a look.