Titanium SDK 5.3.0.RC Release Note

Titanium SDK 5.3.0.RC - 5 May 2016


About This Release

Titanium SDK 5.3.0.RC is a minor release of the SDK, addressing high-priority issues from previous releases.

As of this release, Titanium SDK 5.2.x will not be supported six months from 5.3.0.GA's release date. See Axway Appcelerator Deprecation Policy and Nominal Lifetimes documents for details.

Windows 8.1 and Windows 10

With the release of SDK 5.3.0, we put some focus on supporting Windows 10 and Windows 10 mobile features (TIMOB-19816).

We updated the way you can specify capabilities of your app in the tiapp.xml to account for namespace and naming differences between Windows 8.1 and 10 apps (TIMOB-20231). Previously, you would have to include capabilities in the xml namespace on the tag. You had to know what namespace prefix to use based on what capability your app for each platform and version. See Handling differing capabilities between Windows 8.1 and 10 for some examples on for Windows 8.1 and Windows 10 capabilities.

This release also includes support of localization (TIMOB-20315) that includes localization of application name and properties for the Ti.Locale module:


On the SDK and tooling side, we added support for Windows 10 detection and tooling without requiring the user to also have Windows 8.1 SDK/tooling (TIMOB-20198). Listing of emulators was improved when no specific Windows SDK version is specified to include all available emulators (TIMOB-20571 and TISTUD-8447). The SDK no longer requires explicit setting of the --wp-sdk option for SDK version when the version of the SDK can be determined by the chosen emulator (i.e. If a user chooses to build for a Windows 10 emulator, they no longer also have to provide the --wp-sdk 10.0 flag). Updated CLI and tooling to support deploying to Windows 10 mobile devices and emulators (TIMOB-20096). And, to support Windows 10 policy changes for signing apps, we now support generating private keys to sign for Windows 10 mobile apps. FA temporary key is generated for development if the user has no certificate or private key (TIMOB-20145).

Also, we updated Ti.Media.AudioPlayer’s use of background audio APIs due to changes in Windows 10 API (TIMOB-20080) and added support for handling window size under the Windows 10 Store desktop apps (TIMOB-20187).

Finally, if the tooling is unable to launch the app, the developer now gets a notification to open the app on their device when building to a Windows 10 mobile device (TIMOB-20611).

New Features

iOS Platform

  • TIMOB-17335 - iOS8: Add support for Share Extensions
    • Added support for iOS8 Share Extensions

Windows Platform

App Preview

App Preview integration with iOS Adhoc and Android builds (TISTUD-8009 and TISTUD-8010). App Preview is a new capability to distribute beta versions of your apps to testers and stakeholders. With this integration, Studio users can be able to upload an app to app preview.

App Preview has also been integrated with the CLI (CLI-664)

App Designer

App Designer is a powerful drag-and-drop UI design capability feature which now comes with the Appcelerator Studio as a default editor for Alloy Views. App Designer supports both designer and code editor.

App Designer is installed when Mac and Windows users install Appcelerator Studio 4.6.0 (TISTUD-8457 and TISTUD-8448). When the users upgrade Appcelerator Studio from previous versions to 4.6.0, App Designer is also upgraded to version 4.6.0.

Community Credits

Fixed Issues

  • CLI-955 - CLI should not tell a user to install a pre-release CLI as an update from a GA version
  • CLI-978 - Appc config get <key> always returns null
  • CLI-987 - Appcelerator Login not triggered when login is required on production build
  • CLI-1000 - Uploading app to app preview progress bar is seen multiple times in the studio console
  • TIMOB-19673 - windowslib: visualstudio.detect failed for VS 2015
  • TIMOB-19937 - Windows: Titanium.UI.ImageView animation events
  • TIMOB-19954 - Windows: Implement ImageView properties
  • TIMOB-19958 - Windows: Missing events in ScrollableView
  • TIMOB-19959 - Windows: Missing events in ScrollView
  • TIMOB-19960 - Windows: background color/image for Ti.UI.Tab and TabGroup
  • TIMOB-19964 - Windows: attributedString for Label
  • TIMOB-20035 - Windows:Ti.Media.AudioPlayer => allowBackground has no effect
  • TIMOB-20095 - Windows: Cannot deploy app to Win 10 Mobile emulator
  • TIMOB-20097 - Windows: Windows 10 Mobile requires pfx
  • TIMOB-20143 - Windows: Titanium.UI.WebView don't load local html page
  • TIMOB-20155 - Windows: Ti.Codec.encodeNumber hangs on Windows 10
  • TIMOB-20166 - Windows: Window.fullscreen on Windows 10 doesn't work
  • TIMOB-20167 - Windows: Platform.version on Windows 10
  • TIMOB-20172 - Windows 10: Cannot package for the phonestore or winstore
  • TIMOB-20173 - Windows: Ti.Platform.username on Windows 10
  • TIMOB-20190 - Titanium.Database.ResultSet.fieldName([index]) is not returning the correct value
  • TIMOB-20191 - The e.source of a table click event is supposed to return the table row but instead it returns the table view
  • TIMOB-20192 - [Windows Phone 8.1] Certification reject - This API is not supported for this application type - Api=OutputDebugStringA. Module=api-ms-win-core-debug-l1-1-1.dll
  • TIMOB-20195 - Windows: The textAlign and verticalAlign property of the label is not working on windows phone
  • TIMOB-20222 - Windows: Error while createcollection on Windows Phone
  • TIMOB-20236 - Windows: Downloaded image not show in ImageView
  • TIMOB-20246 - Windows: generate_project.js does not set MSBuild version
  • TIMOB-20282 - Windows: ProgressBar default layout should be SIZE, not FILL
  • TIMOB-20288 - Windows: File.write can't handle UTF-8 string
  • TIMOB-20370 - Windows: Running desktop app doesn't show logs in console
  • TIMOB-20372 - Windows: Ti.App.fireEvent and listener doesnt work in static javascript/html page loaded in webview
  • TIMOB-20376 - Windows Phone: Cannot read property 'split' of undefined
  • TIMOB-20382 - Windows: Custom iconic fonts do not render properly.
  • TIMOB-20385 - Windows: ScrollView does not respect `top` property on views
  • TIMOB-20386 - Windows: View based click event are not working consistently
  • TIMOB-20440 - Android 6.0: writing to applicationDataDirectory fails without External storage permissions
  • TIMOB-20478 - Windows: Implement missing Ti.Locale properties
  • TIMOB-20480 - Windows: Implement missing Ti.Locale functions
  • TIMOB-20481 - Windows: Support l10n application name
  • TIMOB-20566 - Windows: Building to a Windows 10 mobile device errors with 'Failed to conect to emulator'
  • TIMOB-20569 - Windows: View visible property doesn't seem to work on Windows phone
  • TIMOB-20572 - Windows: Windows 10 Mobile device is listed as available to build to when not connected by USB
  • TIMOB-20581 - Windows: Ti App Properties Crashes while storing large data
  • TIMOB-20598 - Windows: views not animating correctly
  • TIMOB-20600 - Windows: close window throws unknown exception
  • TIMOB-20601 - Windows: Support bindId property on ListView
  • TIMOB-20605 - Windows: view.center not working
  • TIMOB-20609 - Windows: ImageView.image doesn't handle Windows-style path
  • TIMOB-20612 - Windows: postlayout events not firing
  • TIMOB-20613 - Android native modules build is getting failed with Android NDK r11
  • TIMOB-20625 - SplashScreen is used for "Ti.App.forceSplashAsSnapshot" instead of LaunchScreen
  • TIMOB-20627 - iOS: App rejected by Apple due to use of the nativeObject API
  • TIMOB-23127 - Windows: Ti.Network.HTTPClient.setRequestHeader is crashing
  • TIMOB-23146 - iOS/WatchOS: Installing to Simulators hangs since Xcode 7.3
  • TIMOB-23170 - If you launch the default Alloy app on Windows 8.1 emulator, "[ERROR] [object CallbackObject]" appears in the console
  • TIMOB-23171 - Cannot package Alloy app for dist-winstore
  • TIMOB-23172 - Default min-ios-ver and default enable-launch-screen-storyboard combination rejected by Apple
  • TIMOB-23181 - Windows: Install of app to Windows 10 Mobile device fails on second build of application
  • TIMOB-23192 - Windows: Prompt for selecting wp-sdk option contains unsupported 8.0
  • TIMOB-23208 - CLI: Error when building for Windows Phone
  • TIMOB-23214 - Windows: raulriera/XHR doesn't work with HTTPClient implementation
  • TIMOB-23217 - Windows: Packaging for dist-winstore with 8.1 SDK fails
  • TIMOB-23223 - Windows: No splash screen when deploying alloy app to windows 10 mobile
  • TIMOB-23235 - Windows: Splash screen on Win 10 mobile doesn't look right
  • TIMOB-23237 - Windows: Inconsistencies in Ti.API.log
  • TIMOB-23241 - Windows: logging from native module doesn't work
  • TIMOB-23253 - Windows: Build errors when building to device and selecting second option in device prompt
  • TIMOB-23274 - Windows: No warn logging from internal TITANIUM_LOG_WARN
  • TIMOB-23301 - Windows: Ti.API.log doesn't handle single argument
  • TISTUD-7602 - Remove Samples View from Appcelerator Studio
  • TISTUD-7952 - iOS: Breakpoints not hit when debugging projects
  • TISTUD-7997 - SDK update to 5.2.0.GA not found when 6.0 nightly is installed
  • TISTUD-8018 - iOS Debugger: failed to connect.
  • TISTUD-8019 - Studio: Selecting Two-Tabbed Alloy mobile app project generates a default Alloy project instead
  • TISTUD-8023 - Don't allow to edit organization name in the Splash screen user login prompt
  • TISTUD-8026 - Studio can't deal with Genymotion 2.6.0 or later
  • TISTUD-8460 - Default Android SDK downloaded by configuration is to old and not supported by Titanium 5.2.2
  • TISTUD-8464 - xml views files are in web format, cannot open with studio
  • TISTUD-8465 - Tiapp now opens with the XML editor by default
  • TISTUD-8471 - Android: Creating project with just android 6.0 platform installed studio shows a message "Android development requires [2.3.3,6.0)"
  • TISTUD-8473 - Unable to create android module in studio.
  • TISTUD-8474 - Enable app preview options if appc core is bundled with an app preview hook
  • TISTUD-8475 - Unable to build to Windows device
  • TISTUD-8476 - Run targets should show the Windows phone device name rather than udid


  • In App Designer, when creating an event in the properties of an element, the controller for the event is opened
  • In App Designer, Scratchpad's XML editor now includes IntelliSence behavior (similar to how IntelliSence works on Alloy View XML editor)
  • CLI-963 - CLI: enable template options when creating Alloy project
    • Added feature that allows for creating two_tabbed Alloy project from CLI

  • TIMOB-18066 - Support remote debugging / inspecting of Android webviews
    • Support remote debugging and inspecting of Android webviews

  • TIMOB-18531 - Windows: Use default publisher-guid when none is given on build
    • Ti CLI now uses a default publisher GUID for non-production builds (00000000-0000-1000-8000-000000000000) and will prompt developers to enter a guid only when building for dist-phonestore or dist-winstore with no value for windows.publisherId configured

  • TIMOB-18707 - Windows: Support Ti.UI.View border* properties
    • Added support for Ti.UI.View border properties (borderColor, borderRadius, and borderWidth)
  • TIMOB-19946 - Windows: Implement Titanium.UI.AlertDialog.hide
    • Added Titanium.UI.AlertDialog.hide for Windows
  • TIMOB-20085 - Windows: ti clean should cleanup VS temporary build directory
    • The ti clean command cleans up the temporary build directory

  • TIMOB-20241 - Windows: Implement Ti.UI.View.convertPointToView( point, destinationView )
  • TIMOB-20281 - Windows: Implement enabled property for View
    • Implemented the Ti.UI.View.enabled property. This is currently not in our docs, but Android (and now Windows) has it. This makes it so that the backgroundDisabledColor and backgroundDisabledImage would be shown when enabled is set to false (otherwise, I’m not sure when those values would ever be used). Other than that, I don’t think it “disables” all the controls on the view from being clickable/editable/etc for us. Since this wasn’t really defined ind acs, I’m guessing we may need to revisit and make sure we’re in parity with Android.

  • TISTUD-7717 - Reconnect to the debug session after the app is restarted
    • Reconnect to the debug session after the app is restarted. If the app is accidentally crashed or terminated on a device or simulator, then the user doesn't need to re-launch the studio debug session, rather it automatically connects upon the app launch.
  • TISTUD-7946 - User should be able to set Arrow port in the launch configuration for Studio
    • Studio users can set Arrow port through Studio Arrow preference option. This option provides a provision to set user specific port, any free port, and default configuration port.
  • TISTUD-8003 - Non-modal dialog for submitting JIRA ticket from the studio
    • Non-modal dialog for submitting JIRA tickets from Studio
  • TISTUD-8012 - Studio needs to call "appc run" / "ti build" to build iOS/Android modules
    • Studio builds iOS and Android modules using appc run command that avoids the dependency of python and ant scripts for iOS and Android builds
  • TISTUD-8447 - Windows: Studio needs to specify the Windows SDK to be used when building to a Windows 10 emulator
    • Studio sends a windows SDK flag --wp-sdk while building for Windows platform emulators to enable SDK specific builds
  • TISTUD-8455 - An option to set App designer Scratchpad XML editor as a default alloy view editor
    • Studio 4.6.0 comes with App Designer as a default editor for Alloy Views, but that can be changed to standard Alloy View editor using Studio editor preference options

API Changes

The following APIs are deprecated in Release 5.3.0.RC.

API Type Notes
Titanium.UI.Picker.getUseSpinner method

This property is deprecated. Please use the default native "dropdown" style.

Titanium.UI.Picker.setUseSpinner method

This property is deprecated. Please use the default native "dropdown" style.

Titanium.UI.Picker.useSpinner property

This property is deprecated. Please use the default native "dropdown" style.

Related Links