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

AppBuilder 2.8.2 Release Notes

Product version: AppBuilder 2.8.2

Released: 2015, March 5

AppBuilder 2.8.2 is an update release. For a list of the new features and updates introduced in the earlier major release, AppBuilder 2.8, see AppBuilder 2.8 Release Notes.

This release introduces the following updates in AppBuilder.

  • You can debug NativeScript apps while running on devices.
  • You can develop cross-platform native apps with NativeScript 0.9.0.
  • You can create new NativeScript apps from the extension for Visual Studio.
  • You can run the command-line interface on systems with Node.js 0.12.0 installed.

This release introduces the following breaking change in AppBuilder.

Warning Introduced new Windows Phone 8.1-specific app properties required for publishing.
If you have created your app with an earlier version of AppBuilder, you need to open Properties once or run an appbuilder prop command to let AppBuilder set default values for the new properties. Keep in mind that you will not be able to publish your app with the default values.

Warning Introduced new Windows Phone 8.1-specific icons and splash screens for publishing.
If you have created your app with an earlier version of AppBuilder, you need to manually add the missing image resources.

Warning Deprecated the NativeScript extension for Visual Studio.
You can now develop cross-platform native apps with NativeScript in the extension for Visual Studio.

This release resolves the following issues in AppBuilder.

  • You cannot publish Windows Phone 8.1 apps in the Windows Phone Store.
  • If your App ID contains a dash, you cannot upload your app to iTunes Connect from the command-line interface.
  • When you attempt to edit AndroidManifest.xml or Info.plist in a NativeScript app, AppBuilder opens the respective configuration files for hybrid development instead of native development.
  • If your app accesses the local storage, you cannot run it in the device simulator in the command-line interface.
  • The links on the dashboard in the classic Windows desktop client are outdated and do not provide relevant information.
  • If your app makes an empty request, the device simulator becomes unresponsive and needs to close.
  • You cannot switch between accounts in the in-browser client.
  • The command-line interface does not recognize some AppBuilder samples as valid apps. When you attempt to run commands on such apps, the command-line interface shows the following error message:
The app file /FILE_PATH/.abproject is corrupted.
Consider restoring an earlier version from your source control or backup.
To create a new one with the default settings, delete this file and run $ appbuilder init hybrid.
Additional technical info: Exception: FUTURE_PROJECT_VER
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.