Titanium Studio/SDK Beta 2 Now Available

Two photographs of colored pencils and a paint brush combined to form a new object.

Today we release the second beta of the newest version of our Titanium platform–SDK and Studio 3.0.0. This version includes several additional features as well as bug fixes uncovered during our (and your) testing. Read on below, and for full information, please see the release notes.

This release includes several new features related to the Android action bar.

  • TIMOB-11601 Android: Expose ActionBar methods.
  • TIMOB-11602 Android: Expose activity.invalidateOptionsMenu to allow changing action items in Android 3.0 and above.

Fixed since 3.0 Beta 1

  • TIMOB-6891 Android: Tab’s window property is null if set via creation arguments.
  • TIMOB-6906 Tooling: tiapp.xml – line breaks in description field break compilation.
  • TIMOB-10363 Android: Picker “add” method is dead slow
  • TIMOB-11525 Android: Relative path for Window URL does not work on 3_0_X.
  • TIMOB-11585 CLI: Error messaging is showing undefined for SDK version.
  • TIMOB-11598 CLI: iOS: generated xcode project cannot find “node”.
  • TIMOB-11599 CLI: Using XCode to run app on device won’t work.
  • TIMOB-11664 Android: TabGroup: Tabgroup focus event fired twice on application launch and one of those with source as undefined. This was a regression in 3.0.
  • TIMOB-11678 CLI: iOS: iPad Simulator launches as iPhone Simulator.
  • TIMOB-11685 iOS: Packaging – Packaged application logs messages in Xcode console. This was a regression occurring in Release 3.0 and 2.1.3.
  • TIMOB-11710 CLI build failure reason is only available when tracing is on.
  • TIMOB-11751 Android: HTTPClient.onreadystatechange not dispatched. This was a regression in 3.0.

Note: This is a beta 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. We will follow with a release candidate in the coming weeks. If you find an issue, please report it in JIRA with a reproducible test case.

How to Update

These are links to continuous integration builds. To install them, choose “Help Menu > Install Specific Titanium SDK…” from inside Titanium Studio.

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

New Features in Titanium SDK 3.0.0

The docs are all available at: http://docs.appcelerator.com/titanium/3.0/

As a reminder, some of the new features coming in SDK Platform 3.0:

  • On-Device Debugging
  • Alloy Framework
  • Titanium Command-Line Interface
  • Event Bubbling API Changes
  • Android Action Bar Support
  • Accessibility Features

New Features in Titanium Studio 3.0.0

One of the major differences with version 3.0 of the Titanium SDK is that a number of projects come as node modules. Studio will look for a Node.js installation on your system. If it does not find it, it will install it, and then prompt you to install the necessary modules via NPM.

  • Performance Improvements
  • Alloy Integration
  • Node.ACS Integration
  • On-Device Debugging
  • Deprecation Warnings

1 COMMENT

  1. I installed the new CLI and with that, I installed the SDK 3.0 Beta.
    The Build script doesn’t work for me, it doesn’t find any Provisioning Profiles.
    I don’t want to install Titanium Studio on my build server just for this.

    Am I doing anything wrong?

  2. Cant wait for this to hit the street, this will make a huge business impact for the Enterprise customers we are serving. Thanks guys for another awesome version upgrade!

  3. I installed XCode from the App Store, also installed the command line utilities and imported my certificates and provisioning profiles.
    I installed nodejs with npm, installed alloy and titanium cli

    With the titanium CLI I downloaded the current Beta SDK and made it the default, logged in etc.
    In the Project directory I now run

    > titanium build -b -f -p ios –target “dist-adhoc” -R “” -P “” -O ./ipa

    response:

    > [ERROR] Invalid Provisioning Profile UUID “”
    >
    > Available Provisioning Profile UUIDs:

    And then nothing…

    P.S. Note that the Stuff in has the correct values when I execute the command. I just have them removed here.

    • @CBeloch. It sounds like there is something missing in your setup, but we should be better about alerting you. Would you please mind filing those steps as a JIRA ticket and we’ll investigate for you?

  4. Downloading Titanium Mobile SDK 3.0 beta 2: Error 403, Forbidden.

    $ wget http://builds.appcelerator.com.s3.amazonaws.com/mobile/3_0_X/mobilesdk-3.0.0.v20121113170203-linux.zip
    –2012-12-02 08:57:28– http://builds.appcelerator.com.s3.amazonaws.com/mobile/3_0_X/mobilesdk-3.0.0.v20121113170203-linux.zip
    Resolving builds.appcelerator.com.s3.amazonaws.com (builds.appcelerator.com.s3.amazonaws.com)… 207.171.189.81
    Connecting to builds.appcelerator.com.s3.amazonaws.com (builds.appcelerator.com.s3.amazonaws.com)|207.171.189.81|:80… connected.
    HTTP request sent, awaiting response… 403 Forbidden
    2012-12-02 08:57:28 ERROR 403: Forbidden.

    Any mirror?