Release History

By product

AppBuilder v2.11

July 28, 2015

Release Notes

NEW

Major Features and Updates

This section contains the major new features and improvements that AppBuilder 2.11 introduces.

  Feature In-Browser Client Windows Client Extension for Visual Studio Command-Line Interface
Hybrid Development Create the icons and splash screens for your app from a single source
Set the deployment target for iOS applications
Enable or disable anonymous error reporting
Migrating to Apache Cordova 4.0.0 automatically enables the Whitelist core plugin for Android
AppBuilder recognizes, respects and runs plugin hooks for the verified plugins, maintained by Telerik
Updated the Telerik Analytics configuration wizard to work with the latest plugin version Not Applicable
Updated the default .abignore file in all sample apps
Updated the default config.xml files for iOS, Android and Windows Phone
Improved cloning of projects from remote repositories Not Applicable Not Applicable
Native Development Develop apps with NativeScript 1.1.2
Use custom modules in your NativeScript apps
Create the icons and splash screens for your app from a single source
Set the deployment target for iOS applications
Hardware acceleration is enabled by default for Android apps
Updated the default .abignore file in all sample apps
Improved cloning of projects from remote repositories Not Applicable Not Applicable
Mobile Website Development Improved cloning of projects from remote repositories Not Applicable Not Applicable

 


Features and Updates in the In-Browser Client

This release of AppBuilder introduces the following features and improvements in the AppBuilder in-browser client.

  • You can use autocompletion for tags, attributes and attribute values for enumerables when writing HTML. Press Ctrl+Space to toggle autocompletion.
  • You can use autocompletion for properties, values and pseudo-classes when writing CSS. Press Ctrl+Space to toggle autocompletion.
  • You can use autocompletion for NativeScript JavaScript. Press Ctrl+Space to toggle autocompletion.
  • You can use autocompletion for NativeScript XML. Press Ctrl+Space to toggle autocompletion.
  • You can export provisioning profiles.
  • You can navigate to a line in your code.
  • Improved migrations between Apache Cordova versions.
    • When you migrate to and from Apache Cordova 4.0.0, the AppBuilder in-browser client does not reload your project.
    • When you migrate to Apache Cordova 4.0.0, the AppBuilder in-browser client enables hardware acceleration for Android.

Features and Updates in the Extension for Visual Studio

This release of AppBuilder introduces the following features and improvements in the AppBuilder extension for Visual Studio.

  • Redesigned the selection of device families, device orientation and other project properties.
  • Use .abignore to determine which files to include or exclude when you build your project.
  • You can use autocompletion for NativeScript XML. Press Ctrl+Space to toggle autocompletion.

Features and Updates in the Command-Line Interface and the Package for Sublime Text

This release of AppBuilder introduces the following features and improvements in the AppBuilder command-line interface and AppBuilder package for Sublime Text.

  • For plugins with plugin variables, you can set values for the variables from the command line using the --var option. For more information, run appbuilder help plugin add or appbuilder help plugin configure
  • You can make your Telerik AppManager publicly available by specifying the --public option for appbuilder appmanager upload operations. Users will be able to install the app from a URL without using the Telerik AppManager companion app.
  • You can automate your Screen Builder project creation and configuration by providing a *.json file with the settings that you want to apply.
  • You can run appbuilder doctor to check your system for configuration issues which might prevent the AppBuilder command-line interface from working properly.
  • When you create a Screen Builder project, the AppBuilder command-line interface launches the device simulator. To avoid launching the simulator, run the create command with the --no-simulator flag.
  • Improved the Screen Builder commands.
    • You can add Progress Data Service data providers to your app.
    • The AppBuilder command-line interface suggests unique names for the Screen Builder components.
  • Improved the appbuilder cloud and appbuilder cloud export commands.
    • appbuilder cloud now lists projects in the context of their solutions.
    • appbuilder cloud export can now export a selected project from a solution. For example: the AppBuilder project from a solution which contains an additional Mobile Testing project.
    • appbuilder cloud export can now export all projects from a solution. For example: the AppBuilder and Mobile Testing projects inside a solution.
  • Multiple usability improvements.
    • Renamed the appbuilder feature-usage-tracking command to appbuilder usage-reporting.
    • After you create a Screen Builder project, the device simulator launches automatically to let you preview your changes.
    • Improved behavior of interactive commands when running in a non-interactive console.

Features and Updates in the Companion Apps

This release of AppBuilder introduces the following features and improvements in the NativeScript companion apps.

  • Hardware acceleration is enabled in the NativeScript companion app for Android.
  • When you update the NativeScript companion app for Android, it preserves your currently loaded project, if no breaking changes are present.
  • When you try to load a project which targets an unsupported NativeScript version, the NativeScript companion app shows a warning.
FIXED

Notable Resolved Issues

This section contains the major bug fixes that AppBuilder 2.11 introduces.

Functional Area Notable Resolved Issues
Frameworks
  • On iOS devices, when you scroll down in an InAppBrowser view, the content of the web page goes under the status bar.
  • You cannot debug Android applications which use the Crosswalk web view.
Mobile Devices and Platforms
  • If your app uses the WKWebView web view for iOS, you cannot LiveSync changes.
  • If your app uses the WKWebView web view for iOS, you cannot provide AppManager LiveSync updates for your app.
  • When two users build for iOS with the same provisioning profile simultaneously, the build of the user who issued the operation first cannot complete.
  • If you set the Android theme to the default one in your AndroidManifest.xml, you can no longer LiveSync your changes.
  • Some of the names of the iOS icons are incorrect.
  • On, iPhone 6 Plus devices, the app icon does not show as expected.
In-Browser Client
  • Sometimes if your solution contains two projects, when you attempt to export your project, the AppBuilder in-browser client exports the Mobile Testing project instead of the AppBuilder project.
  • You cannot clone project from a remote repository if the project files are not nested in a folder.
  • After dismissing a modal popup window, you can no longer use the keyboard shortcuts in the Project Navigator.
  • In Firefox, you cannot import archives by dragging and dropping them in the Add from archive dialog.
  • The AppBuilder in-browser client does not prompt you for confirmation when you delete a remote server connection.
Windows Client
  • The device simulator shows the pinch-to-zoom cursor in mobile website projects.
  • If you have disabled the network connection for another project, the Internet connection for your mobile website becomes disabled and the device simulator does not load it. This causes your project to appear blank in the device simulator.
  • Sometimes if your solution contains two projects, when you attempt to export your project, the AppBuilder Windows client exports the Mobile Testing project instead of the AppBuilder project.
  • When you attempt to connect to your GitHub account by providing your GitHub credentials in the Configure Remote Repository wizard, the AppBuilder Windows client cannot complete the operation and shows the following error message: Access to this method requires an authenticated user.
  • When the device simulator shows an alert, the AppBuilder Windows client becomes unresponsive until you dismiss the alert.
  • When you load cordova.js through the require.js configuration options, the device simulator cannot detect touch events.
  • You can disable all device orientations.
  • You cannot clone project from a remote repository if the project files are not nested in a folder.
  • The AppBuilder Windows client becomes unresponsive after you confirm that you want to save unsaved changes when attempting to close the AppBuilder Windows client.
Extension for Visual Studio
  • The device simulator shows the pinch-to-zoom cursor in mobile website projects.
  • If you have disabled the network connection for another project, the Internet connection for your mobile website becomes disabled and the device simulator does not load it. This causes your project to appear blank in the device simulator.
  • When the device simulator shows an alert, the AppBuilder extension for Visual Studio becomes unresponsive until you dismiss the alert.
  • When you load cordova.js through the require.js configuration options, the device simulator cannot detect touch events.
  • You can disable all device orientations.
  • When you create new XML in a NativeScript project, the AppBuilder extension for Visual Studio sets $itemname$ as file name.
  • In Visual Studio 2012, you cannot migrate NativeScript TypeScript projects.
Command-Line Interface
  • On Windows systems, the device simulator shows the pinch-to-zoom cursor in mobile website projects.
  • On Windows systems, if you have disabled the network connection for another project, the Internet connection for your mobile website becomes disabled and the device simulator does not load it. This causes your project to appear blank in the device simulator.
  • When you load cordova.js through the require.js configuration options, the device simulator cannot detect touch events.
  • You cannot run Android-related commands, if your Windows user name consists of two or more words separated by a space.
  • You can add Telerik Verified Plugins Marketplace plugins which are incompatible with the current Apache Cordova version of your project.
Companion Apps
  • You cannot load your app in the NativeScript companion app for Android by scanning the QR code with the built-in QR code scanner.
  • When no project is loaded, the NativeScript companion app for Android shows the following error message: Error: Invalid url: ''. Url must start with prefix: 'nativescript:'..

 

CHANGED

Breaking Changes

This section contains the major breaking changes that AppBuilder 2.11 introduces.

Hybrid Development

Warning Renamed the appbuilder feature-usage-tracking command to appbuilder usage-reporting in the AppBuilder command-line interface. You need to update existing scripts which call appbuilder feature-usage-tracking to call appbuilder usage-reporting instead.

Warning If your project targets Apache Cordova 4.0.0 or later, the Telerik Analytics, Telerik Mobile Testing and Telerik AppFeedback plugins are available as verified plugins from the Telerik Verified Plugins Marketplace and not as integrated plugins from the Project Properties dialog.

Native Development

Warning Renamed the appbuilder feature-usage-tracking command to appbuilder usage-reporting in the AppBuilder command-line interface. You need to update existing scripts which call appbuilder feature-usage-tracking to call appbuilder usage-reporting instead.

Warning When you update your project to target NativeScript 1.1.2, you might experience multiple issues due to breaking changes in the APIs. For more information about the major changes in NativeScript 1.1.2, 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.1.2, see Configure the Target NativeScript Version.

Warning Migrating between NativeScript versions completely replaces the tns_modules folder. Any custom modules or files will be lost. To be able to use any custom modules, make sure that they are available as npm packages and list them in the dependencies section in the package.json file in the root of the project. The AppBuilder will resolve them on build. For more information about the dependencies syntax, see Specifics of npm's package.json handling.