Release History

AppBuilder v2.10

June 8, 2015

Release Notes

NEW

Major Features and Updates

This section contains the major new features and improvements that AppBuilder 2.10 introduces. For a complete list of the updates that AppBuilder 2.10 introduces, click here.

	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 project 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 project, 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. Projects that are newly migrated to Apache Cordova 3.8.0 will target Apache Cordova 3.7.2 for Android. If your existing project 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 project to Apache Cordova 3.7.0 or earlier and save your changes.
2. Migrate your project back to Apache Cordova 3.8.0 and save your changes.

For more information about how to migrate your project, 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.

FIXED

Notable Resolved Issues

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

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 project for Android. On iOS devices, the status bar for newly created projects 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 AppBuilder 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 AppBuilder in-browser client preserves a toggled context menu when you switch between projects. The AppBuilder in-browser client caches the Run menu when you switch between projects.
Windows Client	The AppBuilder Windows client caches a copy of your cloud project locally. When you switch between branches, the AppBuilder Windows 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 project. The code editor shows errors and warnings for JavaScript objects which contain getters and setters. When you import a project from archive, the AppBuilder Windows client does not update the project name in the project configuration. When you add the SQLite plugin from the Telerik Verified Plugins Marketplace, the AppBuilder Windows client shows it as disabled even though the plugin is available to use inside your project. You cannot rename, cut, copy, paste or move by dragging build-configuration-specific files. The AppBuilder Windows client does not exclude the .abpublish file from your mobile website project when you upload it to FTP. When you attempt to clone a remote repository from an invalid clone URL, the AppBuilder Windows client shows a misleading error message.
Extension for Visual Studio	If a file referenced in your code is missing from your project, the AppBuilder 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 project, the AppBuilder 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 AppBuilder extension for Visual Studio shows it as disabled even though the plugin is available to use inside your project. The Build wizard does not provide an easy way to import certificates and provisioning profiles, if missing. If your solution contains multiple projects, when you open the Project Properties for two or more of the projects, AppBuilder extension for Visual Studio does not show the correct project 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 AppBuilder extension for Visual Studio prompts you for authentication inside the Project Properties dialog after reopening the project, if the Project Properties dialog remained open when closing the project.
Command-Line Interface	On OS X systems, you might not be able to switch to an Android device in the device simulator. You cannot debug your NativeScript projects on Android devices and emulators on Windows systems. If your project 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.

 

CHANGED

Breaking Changes

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

Hybrid Development

When you update your project 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 project.

Removed support for Android 3.x devices for Apache Cordova projects. 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.

Removed the appbuilder add-signin and appbuilder add-signup commands from the AppBuilder 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

When you update your project 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 project to NativeScript 1.0.1, see Configure the Target NativeScript Version.

When you update your NativeScript companion 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.

Removed support for NativeScript 0.9.0. You can build existing projects but you might not be able to run them on device and in the companion app. 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.