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

With build configurations, you can customize your apps to create application packages for debugging or distribution. In Progress AppBuilder, you can customize and apply the Debug and Release build configurations, aimed at testing and production, respectively.

Applying Build Configurations

When you set a build configuration for your application package, AppBuilder automatically applies the following changes to your app.

Option Description
Debug
  • Adds the plugins that you have enabled for this configuration and sets their plugin variables with the correct values.
  • Includes any *.debug.* files in your application package, removes the debug modifiers from the file names and renames them to *.*.
  • If applicable to the AppBuilder client, applies any additional exclude or include rules defined in .debug.abignore.
  • Enables LiveSync. Users can receive the latest changes to your app by tapping and holding with three fingers on their device screens. LiveSync might not be available for some changes and users might need to reinstall the updated and rebuilt package.
    Enabling LiveSync enables the INTERNET Android permission.
    When LiveSync is enabled, you can use the LiveSync JavaScript API to work with LiveSync programmatically.
  • Enables debugging for the app, if applicable to the selected mobile platform.
Release
  • Adds the plugins that you have enabled for this configuration and sets their plugin variables with the correct values.
  • Includes any *.release.* files in your application package, removes the release modifiers from the file names and renames them to *.*.
  • If applicable to the AppBuilder client, applies any additional exclude or include rules defined in .release.abignore.
  • Disables LiveSync. Users cannot receive the latest changes to your app by tapping and holding with three fingers on their device screens and users need to reinstall the updated and rebuilt package.
    Disables the INTERNET Android permission, if you have not manually enabled it. This might cause your app to stop working as expected.
  • Disables debugging for the app, if applicable to the selected mobile platform.

Build Configuration Specifics and Limitations

When you work with build configurations in AppBuilder, keep in mind the following specifics and limitations.

Specifics

  • AppBuilder creates new apps with a disabled Telerik Mobile Testing in the Release configuration.
    You can enable it manually.
  • AppBuilder creates new apps with a disabled Console plugin in the Release configuration.
    You can enable it manually.
  • AppBuilder always disables the Telerik Mobile Testing when you build your app for publishing.
    To create a release build with an enabled Telerik Mobile Testing, build your app with the Build or Build in Cloud operation.
  • When you load your app in the Cordova developer app via QR code, AppBuilder applies the currently set build configuration.
  • When you load your app in the Cordova developer app over cable, AppBuilder always applies the Debug configuration.
  • When you load your app in the Cordova developer app from your account from the Platform companion app, AppBuilder applies the build configuration currently set in the Platform companion app.
  • When you run your app on device as an application package, AppBuilder applies the currently set build configuration.
  • When you run your app in the native emulators, AppBuilder applies the currently set build configuration.
  • When you work with configuration-specific files (*.debug.* and *.release.*), AppBuilder takes the file that matches the currently set build configuration, renames it to *.* and includes it in your application package.
    For example, when you run a build with the Debug configuration, AppBuilder takes index.debug.html and includes it in your application package as index.html.
  • When you work with configuration-specific files (*.debug.* and *.release.*), in your code, reference these files without the configuration modifier (debug or release).
    For example, the correct reference to index.debug.html is index.html.

Limitations

  • You cannot work with configuration-specific files in the App_Resources directory in your app.
  • To work with files which are platform- and configuration-specific simultaneously (*.debug.ios.* or *.release.android.*), your file names must use the following format:

    name.configuration.platform.extension
    
    index.debug.ios.html
    index.debug.android.html
    index.release.ios.html
    index.release.android.html
    

In this section, you will find the following resources:

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.