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

AppBuilder 2.12 Release Notes

Product version: AppBuilder 2.12

Released: 2015, October 1

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 hybrid mobile apps with Apache Cordova 3.8.0 (Verified)*
  Build Apache Cordova 4.0 apps with iPhone SDK 9.0**
  View and install only Telerik Verified Plugins Marketplace plugins and plugin versions applicable to the current target Apache Cordova version Not available
  Create new apps with Kendo UI 2015.2.805
  Build iOS apps with unique CFBundleVersion key values generated on build
  Review the release notes for the Kendo UI package that you want to install
  Work with Apache Cordova plugins referencing Android SDK JAR archives
  Improved generation of icons and splash screens
  Improved error reporting when working with Progress AppManager
  Improved error reporting when your app file contains invalid data
Native Development Install npm packages
  Install plugins from the Telerik Verified Plugins Marketplace
  View detailed logs of build operations
  Build iOS apps with unique CFBundleVersion key values generated on build
  Improved generation of icons and splash screens
  Improved error reporting when working with Progress AppManager
  Improved error reporting when your app file contains invalid data
Mobile Website Development Create new apps with Kendo UI 2015.2.805

* Develop hybrid mobile apps with Apache Cordova 3.8.0 (Verified)
This version of AppBuilder introduces verified support for Apache Cordova 3.8.0 for iOS, Apache Cordova 3.8.0 for Windows Phone and Apache Cordova 3.7.2 for Android.
When you migrate to the latest supported Apache Cordova, keep in mind that you might need to modify your code due to breaking changes in the APIs.

** Build Apache Cordova 4.0 apps with iPhone SDK 9.0
When you issue an iOS build, AppBuilder uses the following toolset to build your app.

  • If your app targets Apache Cordova 4.0.0, AppBuilder now builds your iOS apps with Xcode 7 and the iOS 9 SDK. Your iOS apps support both 32-bit and 64-bit architectures.
  • If your app targets Apache Cordova 3.7.0 or 3.8.0, AppBuilder now builds your iOS apps with Xcode 6 and the iOS 8.4 SDK. Your iOS apps support both 32-bit and 64-bit architectures.

Top of Page

Breaking Changes

Hybrid Development

Warning The classic Windows desktop client, the extension for Visual Studio and the command-line interface for Windows no longer support .NET 4.0. To continue working with any of these clients, update to .NET 4.5 or later.

Warning The command-line interface now requires the latest Node.js 0.10.x or Node.js 0.12.x to run. You cannot install and run the command-line interface on Node.js 4.x.

Warning Deprecated the appbuilder update-kendoui command in the command-line interface. This command will be removed in a future release. Use the appbuilder kendoui commands instead.

Warning AppBuilder no longer builds Apache Cordova 3.7.0 and later apps to support the armv7s architecture.

Warning AppBuilder now builds Apache Cordova 4.0.0 apps with Xcode 7 and the iOS 9 SDK.

Native Development

Warning Starting with AppBuilder 2.14, support for NativeScript versions earlier than NativeScript 1.1.2 will be deprecated. Deprecated versions will be removed in a future release.

Warning The classic Windows desktop client, the extension for Visual Studio and the command-line interface for Windows no longer support .NET 4.0. To continue working with any of these clients, update to .NET 4.5 or later.

Warning The command-line interface now requires the latest Node.js 0.10.x or Node.js 0.12.x to run. You cannot install and run the command-line interface on Node.js 4.x.

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.

  • Improved publishing to Progress AppManager.
    • You can choose to immediately publish your apps after a successful upload.
    • You can choose which distribution groups will be able to access your app.
    • You can choose to send email and push notifications for your published app.
    • You can choose to create a public record in Progress AppManager.
  • Multiple usability improvements.
    • Double-click the Plugins node in the Project Navigator to start managing the plugins in your app.
    • Install Apache Cordova plugins from the Telerik Verified Plugins Marketplace by right-clicking the Plugins node in the Project Navigator and selecting Install Verified Plugins.
    • Improved performance when loading the Kendo UI and Bower tabs in the Manage Packages wizard.

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.

  • Removed support for .NET 4.0.
  • Improved renaming of platform-specific and configuration-specific files.
  • For newly created apps, AppBuilder excludes the .vs folder from your LiveSync-via-USB operations.

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.

  • Updated the Node.js system requirements.
  • Removed support for .NET 4.0 for the command-line interface for Windows.
  • For newly created apps from template or sample, AppBuilder excludes the .vs folder from your build and LiveSync-via-USB operations.
  • Improved commands for installing and updating Kendo UI packages in your app.
    • Deprecated the appbuilder update-kendoui command. This command will be removed in a future release. Use the appbuilder kendoui commands instead.
    • Added the appbuilder kendoui command. You can run it to list the available Kendo UI packages that you can install in your app.
    • Added the appbuilder kendoui install command. You can run it to install a selected Kendo UI package in your app.
    • Added the appbuilder kendoui notes command. You can run it to view the release notes for a selected Kendo UI package.
  • When you perform a build-related operation with the --download flag, the command-line interface downloads the decrypted manifest file for the respective platform (AndroidManifest.xml, Info.plist or WMAppManifest.xml). This way, you can review the final manifest of your application package.
  • All Screen Builder-related commands now suggest relevant Screen Builder commands to run next.

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.

  • The built-in QR code scanner in the Cordova developer app for Windows Phone recognizes and processes links to builds for the companion app and to application package builds.
  • The three-finger refresh gesture and programatic LiveSync with the LiveSync JavaScript API both reload your app in the Cordova developer app.
  • Removed support for the AdMob plugin in the Cordova developer app for Android.

Top of Page

Notable Resolved Issues

This release of AppBuilder introduces the following notable resolved issues.

Functional Area Notable Resolved Issues
General
  • When you attempt to add an existing folder, the in-browser client creates an empty file without a file extension in your app.
    When you run the AddExisting Files operation, in the Upload pop-up window, you can drag a folder to the drop files here to upload text box. If you drag a folder, the in-browser client adds the folder as an empty file with no extension to your app.
  • The icons and splash screens for iPhone 6 and iPhone 6 Plus are missing from the NativeScript app templates.
Frameworks
  • You cannot debug NativeScript apps. On Android devices, the debug tools do not hit your breakpoints. On iOS devices, AppBuilder does not detect NativeScript apps as debuggable.
  • When you attempt to attach the debug tools to an iOS device for the second time in one classic Windows desktop client session, an error is added to the log and debug tools window remains blank.
  • Sometimes when you debug your NativeScript app on an iOS device, the debug tools might not show code and resources.
  • If your app targets Apache Cordova 4.0 and contains the Telerik AppFeedback plugin, you cannot build your app for Android devices.
  • You cannot work with Apache Cordova plugins which require frameworks with parents, such as the Telerik AppFeedback plugin.
  • If your app targets Apache Cordova 4.0 and contains the LeanPlum plugin, you cannot build your app for Android devices.
Mobile Devices and Platforms
  • Sometimes when you debug your NativeScript app on an iOS device, the debug tools might not show code and resources.
  • After you deploy your app on an Android device for the first time, you might experience issues with running in background mode during the first run. When you put the app in background mode and then tap its icon to restore it, the app reloads entirely and lands on the home page. If you exit the app, this behavior does not reproduce the next time you run the app.
  • External links such as tel: and mailto: do not launch in the Cordova developer app for Android.
    Apache Cordova 3.7.0 has introduced a breaking change - for Android to open external links, you must add them to the whitelist in your config.xml. However, the Cordova developer app does not respect config.xml and AndroidManifest.xml for user apps and its config.xml currently does not whitelist them.
  • You cannot debug NativeScript apps. On Android devices, the debug tools do not hit your breakpoints. On iOS devices, AppBuilder does not detect NativeScript apps as debuggable.
  • When you attempt to debug NativeScript apps on iOS devices, the resources never populate.
  • If your app targets Apache Cordova 4.0 and contains the Telerik AppFeedback plugin, you cannot build your app for Android devices.
  • The icons and splash screens for iPhone 6 and iPhone 6 Plus are missing from the NativeScript app templates.
In-Browser Client
  • When you attempt to add an existing folder, the in-browser client creates an empty file without a file extension in your app.
    When you run the AddExisting Files operation, in the Upload pop-up window, you can drag a folder to the drop files here to upload text box. If you drag a folder, the in-browser client adds the folder as an empty file with no extension to your app.
  • The in-browser client does not show data link server-related information properly in the Data Navigator.
Windows Client
  • Sometimes when you debug your NativeScript app on an iOS device, the debug tools might not show code and resources.
  • If a virtual Android device is already running, when you select to launch the emulator with its image, the classic Windows desktop client runs another instance of the image. This instance never loads and your app is not deployed in any of the instances.
  • When you attempt to attach the debug tools to an iOS device for the second time in one classic Windows desktop client session, an error is added to the log and debug tools window remains blank.
  • Sometimes the classic Windows desktop client recognizes valid 9-patch images as malformed.
  • You cannot debug NativeScript apps. On Android devices, the debug tools do not hit your breakpoints. On iOS devices, AppBuilder does not detect NativeScript apps as debuggable.
  • When you attempt to debug NativeScript apps on iOS devices, the resources never populate.
  • When you set a target iOS Simulator device type on which to test your app, the command-line interface does not respect your choice.
  • You cannot delete the values of your plugin variables.
Extension for Visual Studio
  • Sometimes when you debug your NativeScript app on an iOS device, the debug tools might not show code and resources.
  • If a virtual Android device is already running, when you select to launch the emulator with its image, the extension for Visual Studio runs another instance of the image. This instance never loads and your app is not deployed in any of the instances.
  • When you add an existing TypeScript file to your app, the extension for Visual Studio sets an incorrect build action for the file - Content instead of TypeScriptCompile. Because of this, your TypeScript files do not compile to JavaScript files.
  • Sometimes the extension for Visual Studio recognizes valid 9-patch images as malformed.
  • In Microsoft Visual Studio 2015, you might not be able to trigger autocompletion inside <a href> tags.
  • In Microsoft Visual Studio 2015, you cannot use the built-in debug tools to debug your AppBuilder apps.
  • You cannot debug NativeScript apps. On Android devices, the debug tools do not hit your breakpoints. On iOS devices, AppBuilder does not detect NativeScript apps as debuggable.
  • When you attempt to debug NativeScript apps on iOS devices, the resources never populate.
  • You might not be able to debug NativeScript apps on Android devices with the built-in debug tools of Microsoft Visual Studio.
  • When you set a target iOS Simulator device type on which to test your app, the command-line interface does not respect your choice.
  • You cannot delete the values of your plugin variables.
Command-Line Interface
  • Sometimes when you debug your NativeScript app on an iOS device, the debug tools might not show code and resources.
  • After a Screen Builder command completes, the command-line interface does not release the console.
  • If your app does not contain a valid form, running appbuilder add-field might throw an error.
  • You can set the data provider to None for appbuilder add-list commands.
  • Some Screen Builder commands lack the Y/N options and this might cause your configuration to fail with a Missing or invalid component options. error message.
  • In the classic Windows desktop client and the extension for Visual Studio, when you set a target iOS Simulator device type on which to test your app, the command-line interface does not respect your choice.
  • On Android devices configured to a language different from English, the Cordova developer app display name is Barcode Scanner.
Companion Apps
  • External links such as tel: and mailto: do not launch in the Cordova developer app for Android.
    Apache Cordova 3.7.0 has introduced a breaking change - for Android to open external links, you must add them to the whitelist in your config.xml. However, the Cordova developer app does not respect config.xml and AndroidManifest.xml for user apps and its config.xml currently does not whitelist them.
  • The Cordova developer app for iOS scales the contents of your apps on iPhone 6 and iPhone 6 Plus devices.
  • You cannot load your app in the Cordova developer app for Android if the language of your device is not English.

Top of Page

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