Release History

By product

AppBuilder v2.14

November 4, 2015

Release Notes

NEW

For a complete list of the features and updates available in AppBuilder 2.14, click here.

Major Features and Updates

This release of AppBuilder introduces the following major feature across the AppBuilder clients.

FIXED

Notable Resolved Issues

This release of AppBuilder introduces the following notable resolved issues.

Functional Area Notable Resolved Issues
General
  • If you export a project which contains an empty file, you cannot unzip the archive on OS X systems.
Mobile Devices and Platforms
  • If your project contains build configuration-specific .abignore files, you cannot build for Android.
  • When you deploy your app on the Apple Watch, the icons for the watch app are always the default AppBuilder icons.
  • If your project targets Apache Cordova 4.0.0, you cannot build and run your app in the iOS Simulator.
In-Browser Client
  • You cannot delete items from the root of App_Resources.
  • Sometimes, AppBuilder does not save changes to Project Properties correctly.
Windows Client
  • If you have both a regular PNG and a 9-patch splash screen for the same screen resolution, you cannot build your app for Android. The following error message appears: Resource entry splashscreen is already defined..
  • If you are running different versions of the AppBuilder Windows client and the AppBuilder extension for Visual Studio on the same system, you cannot simultaneously run the device simulator from both AppBuilder clients.
  • In the device simulator, if you open a modal alert while a non-modal alert is open, the simulator becomes unresponsive.
Extension for Visual Studio
  • If you have both a regular PNG and a 9-patch splash screen for the same screen resolution, you cannot build your app for Android. The following error message appears: Resource entry splashscreen is already defined.code>.
  • If you are running different versions of the AppBuilder Windows client and the AppBuilder extension for Visual Studio on the same system, you cannot simultaneously run the device simulator from both AppBuilder clients.
  • In the device simulator, if you open a modal alert while a non-modal alert is open, the simulator becomes unresponsive.
  • When you switch between projects, Project Properties might not show your project configuration properly.
  • When you create a project from a sample, the project does not appear in the list of recently opened projects.
  • You cannot configure plugin variables longer than 50 characters.
Command-Line Interface
  • In the device simulator on Windows systems, if you open a modal alert while a non-modal alert is open, the simulator becomes unresponsive.
Package for Sublime Text
  • You cannot deploy your project on multiple connected devices simultaneously.
CHANGED

Breaking Changes

Warning When you update your project to target NativeScript 1.4.3, you might experience multiple issues due to breaking changes in the APIs. For more information about the major changes in NativeScript 1.4.3, see Changelog for the cross-platform modules, Changelog for the iOS runtime and Changelog for the Android runtime.
For more information about how to migrate your project to NativeScript 1.4.3, see Configure the Target NativeScript Version.

Warning When you update your project to target NativeScript 1.4.3, AppBuilder removes the tns_modules directory from your project and updates your package.json to reference the modules as an npm package. In addition, AppBuilder removes App_Resources\Android\values*\styles.xml which might cause the action bar in Android apps to appear twice.
For more information about how to migrate your project to NativeScript 1.4.3, see Configure the Target NativeScript Version.
For more information about how to work around the double action bar in Android apps, see Known Issues with Frameworks.

Warning Deprecated support for NativeScript 0.10.0 and 1.0.1. You can no longer change the target NativeScript version to 0.10.0 and 1.0.1. You will still be able to develop and build existing projects that target NativeScript 0.10.0 and 1.0.1.
Support for NativeScript 0.10.0 and 1.0.1 will be removed in a future release.

Warning Removed support for NativeScript 0.9.0. You can no longer build projects targeting NativeScript 0.9.0. To be able to continue development, you need to manually migrate your project to a later NativeScript version.

  1. Create a new blank NativeScript project.
  2. In the newly created project, replace the /app folder with the one from your NativeScript 0.9.0 project.
  3. In the newly created project, in the /app/App_Resources folder, copy any unique platform-specific assets from the /App_Resources folder from your NativeScript 0.9.0 project.
    Make sure to preserve the initial directory structure of App_Resources.
  4. Address any breaking changes in the NativeScript APIs in your code.