Appcelerator Blog

The Leading Resource for All Things Mobile

RC Releases for 6.0.0 of SDK, CLI & 4.8.0 of Studio

31 Flares 31 Flares ×

Today, we published the following Release Candidate (RC) releases:

  • Titanium SDK 6.0.0
  • Appcelerator CLI 6.0.0
  • Appcelerator Studio 4.8.0

We’d like to thank the Appcelerator Community members who contributed to this release:

Before You Upgrade

Titanium SDK 6.0.0 RC is a MAJOR release that requires updates to your apps. If you haven’t already upgraded to the Beta versions, read through the 6.0.0 Beta Release blog to understand breaking changes and ALL of the release notes BEFORE you upgrade.

Here is a list of breaking changes for SDK 6.0.0:

  • Removal of Ti.include: Ti.include has been deprecated since version 3.3.0, but is completely removed with 6.0.0.
  • Node.js: SDK 6.0.0 brings full Node.js support. Node 4.20 is the new minimum supported version, 4.6.x is the maximum supported version.
  • Xcode: Xcode 8.0 is the minimum supported version
  • Deprecated APIs: Please see this table to see how it would affect your projects.
  • watchOS 1: The watchOS 1 template and all related code are no longer supported
  • Listen to androidback: This version changes how the overrride of default behavior for the back button on Android works.
  • Logging system and TCP ports: Port number is determined at build time, never at run time.
  • Rebuild Android Modules: Android titanium modules must be rebuilt with V8. For an example, check out Tim Poulson’s step-by-step blog on the subject.
  • If you upgraded SDK to version 6.0.0, we strongly urge you to upgrade Studio to version 4.8.0 to avoid any backwards compatibility issues.
  • Hyperloop 2.0.0+ requires Titanium 6.0.0+

Other Notable Items in the Release

Here are a few more notable features and improvements of this release:

  • Ability to enable Multi-dex to avoid the 65k method limit during Android builds
  • Ability for apps using <use -jscore-framework> to use Studio debugger. On iOS, you will need to turn on true. Also, you can use Safari to debug your app.
  • Support for iPhone 7 Haptic Engine API

Known Issues

  • TIMOB-23761 – Hyperloop: Errors when running project with LiveView and hyperloop enabled
  • TIMOB-24037 – Android: Debugging not working with hyperloop enabled with run-on-main-thread set to true or false
  • TIDOC-2553 – Studio Troubleshooting: Launch issue in Windows 64-bit machines
  • TISTUD-8613 – iOS Debugger: Breakpoint is not hit for the first time for a clean alloy project

Release Notes

These releases include 190 bug fixes, 48 improvements, and 30 new features. For a more detailed overview, known issues and closed tickets see the following links:

Update Titanium SDK

To update the Titanium SDK from the command line:

[appc] ti sdk install --branch 6_0_X 6.0.0.v20161101155110
To roll back:

[appc] ti sdk select latest

Update Appcelerator CLI

Both the Appcelerator CLI Installer and the Core Package have been updated.

To update from the command line:

[sudo] npm install -g appcelerator@4.2.8-9
appc use 6.0.0-68
To roll back:

[sudo] npm install -g appcelerator

Update Appcelerator Studio

Get the RC of Studio by changing the update type to Release Candidate and then check for updates.

To roll back delete the beta version and download and install the latest stable version.

Update Hyperloop

If you plan to use Titanium SDK 6.0.0, you will need Hyperloop 2.0.0. To use Hyperloop 2.0.0, update to Titanium SDK 6.0.0, then update from the command line using:

appc new

NOTE: The above method only works using appc cli 6.0.0-68. Alternatively, entering appc config set lastUpdateCheckTiDownloads null before appc run will trigger modules download.

Report 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 Community (AC) project and add as much relevant information as you can, including the release version you are using.

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

31 Flares Twitter 0 Facebook 0 Google+ 2 LinkedIn 29 Email -- 31 Flares ×

2 Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

  1. Chris

    Hi

    Is “Rebuild Android Modules” for SDK 6.0 a must?

    Greetings Chris

    • Hans Knoechel

      Hey Chris!

      In Titanium 6.0.0, we updated the Android V8 engine to greatly improve the Android performance and stability. Because we moved from one major version to another, the V8 implementation had breaking changes that needed native modules to be recompiled if you want to use them in Titanium SDK 6.0.0 and later. The migration usually just means to change the apiversion from 2 to 3 and update the architectures in the manifest file. Some modules require minor additional changes as you can see in the migration guide and core-modules linked in this blog post.

      I hope that helps! – Hans

Sign up for updates!

Become a mobile leader. Take the first step to scale mobile innovation throughout your enterprise.
Get in touch
computer and tablet showing Appcelerator software
Start free, grow from there.
31 Flares Twitter 0 Facebook 0 Google+ 2 LinkedIn 29 Email -- 31 Flares ×