3.2.0 Beta of SDK/Studio Now Available

Blog images

We’re pleased to announce the beta version of 3.2.0, a major update to our 3.1.0 version of the Titanium SDK and Titanium Studio. Version 3.2.0 brings numerous fixes and improvements across both products, as well as preliminary support for iOS 7.1 and Android 4.4. Today, we’re asking you to help test out the release and provide feedback before it becomes generally available in mid-December.

This is a pre-production release, and as such may contain regressions or other issues. Beta software may contain blockers and other regressions. 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, 12/4.

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.

Version 3.2.0 is special in that you need to update the SDK, the CLI and Studio. Studio and the CLI are both backwards compatible with previous versions of the SDK.

NPM Packages

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

npm install -g alloy@1.3.0-beta
npm install -g titanium@3.2.0-beta

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.2.0

Read the complete Release Notes. A full list of updates is available here. 3.2.0 brings many new items:

  • Android 4.4 support
  • Animation improvements
  • Cookie management
  • Android build command now rewritten in JavaScript with many, many bug fixes and improvements
  • ListView Phase 2 (Custom list and section headers and footers, custom row selection, dynamic item loading, search support)
  • xxhdpi support
  • In response to community feedback, we have changed the default behavior of application restarts (also known as Android bug 2373). We previously exposed a property named ‘ti.android.bug2373.finishfalseroot’ to correct this behavior, but you needed to opt-in by setting a property in tiapp.xml. The setting is now on by default. See here for more information. This should be transparent (or better than before) to you and your users, but if you experience weird issues around app launching, please let us know.
  • Note: Android now builds with the latest Android API unless you have specified otherwise in your tiapp.xml
  • Attributed strings
  • Build directly to device (in Studio and CLI. For CLI, use ti build -p ios -T device -C <DEVICE_UDID> [-V “<DEVELOPER_CERTIFICATE_NAME>” -P <PROVISIONING_PROFILE_UUID>])
  • iOS 7.1 support (currently there is a blocker on simulator support: TIMOB-15741)
  • Dynamic animations
  • iOS 7 Animated transitions
  • iOS7 Background services
  • ListView Phase 2 (Custom list and section headers and footers, custom row selection, dynamic item loading, search support)
  • Brand new, much improved, platform installation and configuration wizard
  • Asynchronous login to speed up startup time
  • Auto-detection of connected devices with streamlined run/debug interface
  • Overhaul of user interface and switch to Eclipse 4.3 base
Deprecated items/Breaking changes
  • Android: FastDev support
  • Android: All windows are now heavyweight. Use <property name=”ti.android.useLegacyWindow” type=”bool”>true</property> to return to the previous behavior
  • iOS: iOS 5 support and NavigationGroup
  • iOS: Map is now a separate module with new functionality
  • JSS support

Known Issues

Full list here.

  • There are issues packaging Android apps for distribution using Java 1.7. For the immediate moment, use Java 1.6.
  • You may run into an issue regarding x86 support in 3rd-party modules. If so, see TIMOB-15827 for the workaround for the moment.
  • There are currently issues running apps in the iOS 7.1 simulator. Please watch TIMOB-15741 for updates.
  • You may encounter issues with Android debugging on OS X. If so, please add comments to TISTUD-5659.


  1. I do not know if it’s worth file a bug in JIRA, so:

    -> sudo npm install -g titanium@3.2.0-beta

    -> titanium setup

    -> Where do you want to go? k

    ──────────────────┤ Check Environment ├───────────────────

    ✓ node up-to-date (v0.10.22)
    ✓ npm up-to-date (v1.3.14)

    Titanium CLI
    ✓ cli up-to-date (v3.2.0-beta)

    Titanium CLI Dependencies
    ✓ async up-to-date (v0.2.9)
    ✓ colors up-to-date (v0.6.2)
    ✓ fields up-to-date (v0.1.11)
    ✓ humanize up-to-date (v0.0.9)
    ✓ jade up-to-date (v0.35.0)
    ✓ longjohn up-to-date (v0.2.2)

    throw e;
    TypeError: Invalid Version: MISSING.0.0
    at new SemVer (/usr/local/lib/node_modules/titanium/node_modules/node-appc/node_modules/semver/semver.js:271:11)
    at compare (/usr/local/lib/node_modules/titanium/node_modules/node-appc/node_modules/semver/semver.js:424:10)
    at Function.gt (/usr/local/lib/node_modules/titanium/node_modules/node-appc/node_modules/semver/semver.js:453:10)
    at Object.gt (/usr/local/lib/node_modules/titanium/node_modules/node-appc/lib/version.js:79:16)
    at /usr/local/lib/node_modules/titanium/lib/commands/setup.js:768:24
    at Array.forEach (native)
    at /usr/local/lib/node_modules/titanium/lib/commands/setup.js:764:27
    at /usr/local/lib/node_modules/titanium/lib/commands/setup.js:778:5
    at /usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:530:17
    at /usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:116:25
    at Request.init (/usr/local/lib/node_modules/titanium/node_modules/request/request.js:132:10)
    at new Request (/usr/local/lib/node_modules/titanium/node_modules/request/request.js:105:8)
    at request (/usr/local/lib/node_modules/titanium/node_modules/request/index.js:53:11)
    at /usr/local/lib/node_modules/titanium/lib/commands/setup.js:557:8
    at /usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:508:21
    at /usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:224:13
    at /usr/local/lib/node_modules/titanium/node_modules/async/lib/async.js:108:13
    at Array.forEach (native)
    home4:~ nuno$

  2. Is it normal that I get an error code “Access denied” when visiting the OSX SDK download link?
    I get an error when trying to install from Studio (3.2.0).


  3. Really looking forward to 3.2 RC.

    Behaviors looks Very interesting… Looking forward to an example in iOS7 to use behaviors with TableViewRows… (Or ListViewRow), I’m guessing its possible?

  4. I can’t install the Titanium Studio, nor via installer or update site:
    When I run installer it fails at the git step. I see a ticket opened for it https://jira.appcelerator.org/browse/TISTUD-5594.
    I;m using windows 7.

    When I try to run the update site I get the following message:
    An error occurred while collecting items to be installed
    session context was:(profile=profile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
    Problems downloading artifact:
    Error reading signed content:C:\Users\Hoze\AppData\Local\Temp\signatureFile4650922900668315197.jar
    An error occurred while processing the signatures for the file: C:\Users\Hoze\AppData\Local\Temp\signatureFile4650922900668315197.jar
    Problems downloading artifact: osgi.bundle,com.appcelerator.titanium.core,
    Error reading signed content:C:\Users\Hoze\AppData\Local\Temp\signatureFile1120064499165656657.jar
    An error occurred while processing the signatures for the file: C:\Users\Hoze\AppData\Local\Temp\signatureFile1120064499165656657.jar
    Problems downloading artifact: osgi.bundle,com.appcelerator.titanium.rcp,
    Error reading signed content:C:\Users\Hoze\AppData\Local\Temp\signatureFile7987431164863559532.jar
    An error occurred while processing the signatures for the file: C:\Users\Hoze\AppData\Local\Temp\signatureFile7987431164863559532.jar
    Problems downloading artifact: osgi.bundle,com.appcelerator.titanium.studio.rcp.override,
    Error reading signed content:C:\Users\Hoze\AppData\Local\Temp\signatureFile8934223276992514934.jar
    An error occurred while processing the signatures for the file: C:\Users\Hoze\AppData\Local\Temp\signatureFile8934223276992514934.jar
    Problems downloading artifact: osgi.bundle,com.appcelerator.titanium.ui,
    Error reading signed content:C:\Users\Hoze\AppData\Local\Temp\signatureFile3740287436389197064.jar
    An error occurred while processing the signatures for the file: C:\Users\Hoze\AppData\Local\Temp\signatureFile3740287436389197064.jar
    Problems downloading artifact: osgi.bundle,com.appcelerator.titanium.ui.ide,
    Error reading signed content:C:\Users\Hoze\AppData\Local\Temp\signatureFile7303413437793184954.jar
    An error occurred while processing the signatures for the file: C:\Users\Hoze\AppData\Local\Temp\signatureFile7303413437793184954.jar
    Problems downloading artifact: osgi.bundle,com.appcelerator.titanium.usage,
    Error reading signed content:C:\Users\Hoze\AppData\Local\Temp\signatureFile7293088064839559479.jar
    An error occurred while processing the signatures for the file: C:\Users\Hoze\AppData\Local\Temp\signatureFile7293088064839559479.jar
    Problems downloading artifact: org.eclipse.update.feature,com.appcelerator.titanium.feature,
    Error reading signed content:C:\Users\Hoze\AppData\Local\Temp\signatureFile3954028842293053776.jar
    An error occurred while processing the signatures for the file: C:\Users\Hoze\AppData\Local\Temp\signatureFile3954028842293053776.jar
    Problems downloading artifact: org.eclipse.update.feature,com.appcelerator.titanium.feature.rcp,
    Error reading signed content:C:\Users\Hoze\AppData\Local\Temp\signatureFile3617297820422002033.jar
    An error occurred while processing the signatures for the file: C:\Users\Hoze\AppData\Local\Temp\signatureFile3617297820422002033.jar
    Problems downloading artifact: org.eclipse.update.feature,com.appcelerator.titanium.studio,
    Error reading signed content:C:\Users\Hoze\AppData\Local\Temp\signatureFile6625112118186386489.jar
    An error occurred while processing the signatures for the file: C:\Users\Hoze\AppData\Local\Temp\signatureFile6625112118186386489.jar

  5. The new “streamlined run/debug interface” isn’t very streamlined and shouldn’t be used. The older way was much better and should be left that way.

    • The new mechanism is far more scalable, and also allows direct access to devices you’ve plugged in. Why do you like the old way better?

    • You will need to install Studio from preview.appcelerator.com, and then install the NPM packages separately.

  6. Ingo, this bug is marked as resolved but it is not:


    I read once that the Appcelerator team doesn’t get notifications from resolved tickets so I’m posting here for visibility. If the above ticket is the last blocker for Windows support I thought you’d want to know Windows 7 and 8 users are still seeing the issue installing 3.2 Studio nightlies, betas, and RCs.

  7. Cannot install the beta and the NPM pkgs and get everything working – get the following error:
    [WARN] : Requires version >=3.2, currently 3.1.2
    [ERROR] :  Command “build” incompatible with this version of the Titanium CLI
    [ERROR] Unable to find command “build”

    I have been trying to figure this out over the last few days and cannot. This is very frustrating as we wish to test out our app using attributedstrings because it currently has a bug with rich text display since the ios7 release.

    • Hi @Laurence,

      If you run

      ti -v

      does it says your CLI is the 3.2.0-beta? If it doesn’t, then your CLI has not been updated properly.


  8. Hello. I have some trouble with this version.
    I have “Titanium Studio, build:” installed. And also Alloy 1.3.0. Now i make a new project from Alloy template and run it. What i get on build is this:
    [ERROR] : Alloy 1.3.0 requires Titanium SDK 3.2.0 or higher.
    [ERROR] : Alloy compiler failed

    So what is wrong? I always read to also need the SDK 3.20 seperatleyy, but where and how? I dont see this step mentioned here.

Comments are closed.