Progress will discontinue Telerik Platform on May 10th, 2018. Learn more

AppBuilder 2.10 Release Notes

Product version: AppBuilder 2.10

Released: 2015, June 8

Major Features and Updates

This release of AppBuilder introduces the following major new features and updates across the AppBuilder clients.

  Feature In-Browser Client Windows Client Extension for Visual Studio Command-Line Interface
Hybrid Development Develop with Apache Cordova 4.0.0 (Experimental)*
  Develop Android apps with Apache Cordova 3.7.2**
  Develop Android apps to run in the Crosswalk web view
  Develop iOS apps to run in the WKWebView web view***
  Removed support for Android 3.x devices
Native Development Develop apps with NativeScript 1.0.1
  Migrate NativeScript 0.10.0 apps to NativeScript 1.0.1
  Deprecated support for NativeScript 0.9.0

* Hybrid Development: Develop with Apache Cordova 4.0.0 (Experimental)
When you change the target Apache Cordova version of your app to Apache Cordova 4.0.0, you will actually develop against Apache Cordova 3.8.0 for iOS, Apache Cordova 4.0.2 for Android and Apache Cordova 3.8.0 for Windows Phone.
In this version of AppBuilder, support for Apache Cordova 4.0.0 is experimental. Migrations between Apache Cordova versions have not been verified and you might experience multiple issues when working against Apache Cordova 4.0.0.
When working with Apache Cordova 4.0.0, keep in mind that you might need to modify your code due to breaking changes in the APIs.
Apache Cordova 4.0.0 will become fully supported in a future release of AppBuilder.

For more information about how to migrate your app, see Configure the Target Apache Cordova Version.

** Hybrid Development: Develop Android apps with Apache Cordova 3.7.2
AppBuilder 2.10 introduces support for Apache Cordova 3.7.2 for Android which contains an important security fix. For more information about the security issue that this Apache Cordova release resolves, see Apache Cordova Android 4.0.2 and 3.7.2 released.
AppBuilder introduces support for Apache Cordova 3.7.2 for Android as part of the support for Apache Cordova 3.8.0. Apps that are newly migrated to Apache Cordova 3.8.0 will target Apache Cordova 3.7.2 for Android. If your existing app currently targets Apache Cordova 3.8.0, you need to perform the following steps to migrate it to Apache Cordova 3.7.2 for Android.

  1. Migrate your app to Apache Cordova 3.7.0 or earlier and save your changes.
  2. Migrate your app back to Apache Cordova 3.8.0 and save your changes.

For more information about how to migrate your app, see Configure the Target Apache Cordova Version.

*** Hybrid Development: Develop iOS apps to run in the WKWebView web view
Support for the WKWebView in Apache Cordova is still in its early stages. While this web view provides superior performance, it poses multiple development challenges such as incompatibility with the core Apache Cordova File and Camera APIs and inability to use LiveSync and AppManager LiveSync. For more information about the WKWebView and Apache Cordova, see the WKWebView section here.

Top of Page

Breaking Changes

Hybrid Development

Warning When you update your app to target Apache Cordova 4.0.0, you might experience multiple issues due to breaking changes in the APIs. For more information about the major changes in Apache Cordova 4.0.0, see the iOS release notes, the Android release notes and the Windows Phone 8 release notes.
In addition, make sure to check the detailed release notes for the plugins that you have enabled in your app.

Warning Removed support for Android 3.x devices for Apache Cordova apps. Apache Cordova officially supports Android 2.3.x and 4.x as stated here. You can still deploy your apps on Android 3.x devices but they might not work as expected.

Warning Removed the appbuilder add-signin and appbuilder add-signup commands from the command-line interface. To add login and registration functionality for your app, use appbuilder add-authentication instead. This change will affect any existing scripts that call appbuilder add-signin and appbuilder add-signup.

Native Development

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

Warning When you update your NativeScript developer app to the latest version that targets NativeScript 1.0.1, you will no longer be able to test NativeScript 0.10.0 apps in it.

Warning Removed support for NativeScript 0.9.0. You can build existing apps but you might not be able to run them on device or in the companion app. You need to manually migrate your app to a later NativeScript version.

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

Top of Page

Features and Updates in the In-Browser Client

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

  • You can no longer enable your app for AppManager LiveSync from PropertiesPlugins. You can enable AppManager LiveSync only during publishing.
  • Redesigned the icons for the Background Mode settings in the iOS tab in the Properties.

Top of Page

Features and Updates in the Windows Client

This release of AppBuilder introduces the following features and improvements in the classic Windows desktop client.

Top of Page

Features and Updates in the Extension for Visual Studio

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

Top of Page

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 command-line interface and package for Sublime Text.

  • Improved app generation with Screen Builder.
    • You can add About views to your app with the appbuilder add-about command.
    • You can create sign in and sign up forms with the appbuilder add-authentication command.
    • You can no longer use the appbuilder add-signin and appbuilder add-signup commands. You need to use appbuilder add-authentication instead.
  • Improved appbuilder plugin add
    • You can set the --default flag to install the recommended version of the selected plugin from the Telerik Verified Plugins Marketplace.
    • You can set the --latest flag to install the latest available version of the selected plugin from the Telerik Verified Plugins Marketplace.
  • Improved the appbuilder prop set of commands.
    • You can set the --debug or --release flag in appbuilder prop print commands to print configuration settings for the respective build configuration.
    • You can set the --debug or --release flag in appbuilder prop add CorePlugins commands to enable plugins for the respective build configuration.
    • You can set the --debug or --release flag in appbuilder prop set CorePlugins commands to set plugins for the respective build configuration.
    • You can set the --debug or --release flag in appbuilder prop remove CorePlugins commands to disable plugins for the respective build configuration.
  • Improved the appbuilder appmanager set of commands.
    • You can list the distribution groups in your Telerik AppManager private store with appbuilder appmanager groups
    • You can publish your app after the upload completes by setting the --publish flag for appbuilder appmanager upload commands.
    • You can send emails to your users when you upload and publish a new version of your app by setting the --send-email flag for appbuilder appmanager upload <Platform> --publish commands.
    • You can send push notifications to your users when you upload and publish a new version of your app by setting the --send-push flag for appbuilder appmanager upload <Platform> --publish commands.
    • You can make your app available to selected user groups by setting the --group option for appbuilder appmanager upload commands.
  • Improved appbuilder update-kenodui
    • You can set the --verified flag to list the available stable Kendo UI Service Pack packages.
    • You can set the --latest flag to list the latest available Kendo UI packages.
    • You can set the --latest flag to quickly install the latest available Kendo UI package of the specified type.
    • You can set the --latest and the --verified flags to list the latest available stable Kendo UI Service Pack packages.
    • You can set the --latest and the --verified flags to quickly install the latest available stable Kendo UI Service Pack package of the specified type.
  • Removed support for 9-patch images in the Android device simulator on macOS system to resolve a critical issue.
  • Multiple usability improvements in the command-line interface.
    • Added new warning about missing or misconfigured Mono dependency during the installation.

Top of Page

Features and Updates in the Companion Apps

This release of AppBuilder introduces the following features and improvements in the Cordova developer apps.

  • In the Cordova developer app for Android, you can configure your on-scan settings.
    • You can enable and disable vibration on scan.
    • You can enable and disable beep on scan.
    • You can enable and disable hardware acceleration in the Cordova developer app. This setting will not affect your app and its settings.

Top of Page

Notable Resolved Issues

This release of AppBuilder introduces the following notable resolved issues.

Functional Area Notable Resolved Issues
Frameworks
  • When you scroll through a ListView element and your mouse pointer moves outside the visible application area in the simulator, the scroll freezes. If you attempt to click on an item in the list, the associated click event does not fire.
  • After you add the StreetHawk plugin from the Telerik Verified Plugins Marketplace, you can no longer build your app for Android.
  • On iOS devices, the status bar for newly created apps appears as a white strip.
In-Browser Client
  • If the clone URL for your git repository contains escaped spaces (%20), you cannot connect to the remote repository. The in-browser client prompts you that the URL is invalid.
  • When you add a plugin, Bower packager or Kendo UI package from the Manage Packages wizard, unsaved changes are lost.
  • The in-browser client preserves a toggled context menu when you switch between apps.
  • The in-browser client caches the Run menu when you switch between apps.
Windows Client
  • The classic Windows desktop client caches a copy of your cloud app locally. When you switch between branches, the classic Windows desktop client might not update the cache properly. The device simulator loads resources from the local cache and if they are not updated properly, you might be able to see and access resources that are not actually present in the current state of the app.
  • The code editor shows errors and warnings for JavaScript objects which contain getters and setters.
  • When you import an app from archive, the classic Windows desktop client does not update the app name in the app configuration.
  • When you add the SQLite plugin from the Telerik Verified Plugins Marketplace, the classic Windows desktop client shows it as disabled even though the plugin is available to use inside your app.
  • You cannot rename, cut, copy, paste or move by dragging build-configuration-specific files.
  • The classic Windows desktop client does not exclude the .abpublish file from your mobile website app when you upload it to FTP.
  • When you attempt to clone a remote repository from an invalid clone URL, the classic Windows desktop client shows a misleading error message.
Extension for Visual Studio
  • If a file referenced in your code is missing from your app, the extension for Visual Studio produces the following misleading error during Build operations: Cannot find application package.
  • If a file referenced in your code is missing from your app, the extension for Visual Studio produces the following misleading error during Publish operations: Log (Exception,High): System.ArgumentException: Parameter must not be null or empty.
  • When you add the SQLite plugin from the Telerik Verified Plugins Marketplace, the extension for Visual Studio shows it as disabled even though the plugin is available to use inside your app.
  • The Build wizard does not provide an easy way to import certificates and provisioning profiles, if missing.
  • If your solution contains multiple apps, when you open the Properties for two or more of the apps, extension for Visual Studio does not show the correct app configurations.
  • When you attempt to clone multiple samples, you might exceed the GitHub API limit and the following error message might appear: Status code not successful: (403) Forbidden.
  • The extension for Visual Studio prompts you for authentication inside the Properties dialog after reopening the app, if the Properties dialog remained open when closing the app.
Command-Line Interface
  • On macOS systems, you might not be able to switch to an Android device in the device simulator.
  • You cannot debug your NativeScript apps on Android devices and emulators on Windows systems.
  • If your app created with Screen Builder does no contain a form, running appbuilder add-field throws an error.
Companion Apps
  • Fixed Compainion typo in the welcome screen.

Top of Page

Contact us: +1-888-365-2779
sales@telerik.com
Copyright © 2016-2017, Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.