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

Known Issues with Frameworks

Product version: AppBuilder 3.7.5

Released: August 23, 2017

AppBuilder is known to have the following issues with supported and third-party frameworks and Apache Cordova plugins.

Check frequently for updates and additions to this list.

If you identify an issue that is not on the list, use our forums to report it. You can also browse the community to check for other issues that might not have made it into this list.

Apache Cordova Plugins

AppBuilder is known to have the following issues with Apache Cordova plugins from earlier releases.

  • If your project contains the Telerik Mobile Testing plugin, when you run it on an Android device in the simulator, the following error message appears in the console: Failed to load resource: the server responded with a status of 404 (Not Found) -- local://simulator/plugins/com.telerik.mobiletesting/src/android/cordova/www/deviceready.js.
    Workaround: Ignore the error and continue your work.

  • The Cordova developer app for Android becomes unresponsive and closes when you test QR code encoding.
    Workaround: To test QR code encoding, build and deploy your project as an application package.

  • On iOS devices, you cannot capture and send screen shots for external views with the Progress AppFeedback plugin.
    Workaround: None.

  • In the Cordova developer app for Android, you cannot share images to Facebook with the SocialSharing plugin.
    Workaround: None.

  • In the device simulator in the in-browser client, you cannot test PushPlugin-related functionality.
    Workaround: Build and deploy your app on device.

  • You cannot run custom Apache Cordova plugins in the simulator.
    Workaround: Run your app on a device. For more information, see Running Apps on Devices.

  • When you import files from an archive created on a macOS system, AppBuilder also imports any system files and folders such as __MACOSX and .DS_Store. This might prevent AppBuilder from building your app.
    By default, all archives created on a macOS system contain system files and folders such as __MACOSX and .DS_Store. When you import files from an archive created on a macOS system, AppBuilder also imports any Mac-specific system files and folders. When you import a custom plugin from such an archive, system folders such as __MACOSX are also added in the Plugins folder of your project. Plugman might identify such folders as separate custom plugins and in this case, searches the folder for a valid plugin.xml file. When Plugman cannot locate a valid plugin.xml file, it cannot complete the plugin installation and AppBuilder cannot complete the build for your project.
    Workaround: After you import files from an archive created on a macOS system, make sure to remove any Mac-specific system files and folders from your project. For example, delete __MACOSX and .DS_Store.

  • On iOS 7 devices, if you have enabled the Progress AppFeedback plugin, the app might not show the text in the status bar.
    The Progress AppFeedback uses the native Telerik UI controls which render the plugin view over the status bar. This prevents the text in the status bar from displaying properly.
    Workaround: Modify the status bar settings in Info.plist.

    1. Open Info.plist for editing.
      For more information about working with Info.plist in AppBuilder, see Edit the Configuration Files.
    2. Make sure that the following keys are present in the markup.

      <key>UIStatusBarHidden</key>
      <false/>
      <key>UIViewControllerBasedStatusBarAppearance</key>
      <false/>
      
  • If your application package is enabled for LiveSync, you might not be able to run automated tests on device with Mobile Testing.
    When you attempt to run automated tests with Mobile Testing on an application package with enabled LiveSync, the following error message might appear: TypeError: ‘undefined’ is not a function’ from undefined:0.
    Workaround: Disable LiveSync for the application package. For more information, see Enable or Disable LiveSync for the Application Package.

  • When testing localStorage, your local storage changes might not refresh properly in the device simulator.
    When you click Refresh or Reload in the simulator, it appears that all previous changes to the local storage are lost. Local Storage in the Resources pane in the debugger is empty but changes to your local storage are preserved.
    Workaround: In the simulator, interact with the local storage to refresh the Resources tab. You can create, delete, modify or search for a record in the local storage.

  • When testing notification.beep, the simulator might not play the beep sound properly.
    Depending on your operating system, hardware and the selected simulated device, you might experience issues when testing notification.beep in the simulator. The simulator might play the beep sound with a delay, might not play a beep sound or might start or stop playing the beep sound after one or more attempts.
    Workaround: Restart the simulator or attempt to play the beep sound again.

jQuery Mobile

AppBuilder is known to have the following issues with jQuery Mobile from earlier releases.

  • Back button in a jQuery Mobile project is lost when the project is LiveSynced. This is expected behavior in jQuery Mobile. For more information, see this GitHub thread.

  • When you run a jQuery Mobile project on a mobile device, the footer might render above the bottom border of the screen and a gap might appear between the footer and the bottom of the screen.
    A known issue in jQuery Mobile might cause the footer to not render properly in Kendo UI Core, Kendo UI Professional or jQuery Mobile projects. A gap might appear between the footer and the bottom border of the screen.
    Workaround: Set the height and the min-height attributes of the <body> element of your app to 100%. For example, replace the opening <body> tag with the following code.

    <body style="height:100%;min-height:100%">
    
  • You cannot use the mouse or the keyboard arrows to interact with jQuery sliders in the device simulator.
    Workaround: None.

Kendo UI

AppBuilder is known to have the following issues with Kendo UI from earlier releases.

  • In the developer app for Windows Phone, you cannot test Kendo UI Mobile native scrolling.
    Workaround: Build and deploy your app as an application package.

  • If you have started development from a Kendo UI-based project template, your app might not look and behave properly on Windows Phone 8.1 devices.
    Workaround: Update Kendo UI to the latest stable official package. For more information about how to update Kendo UI in your project, see Update the Code Libraries in Your Project.

  • On iOS 7 devices and in the device simulator, the Kendo UI mobile app with data visualization sample app might not render properly. The header might be too large and the footer might be truncated.
    By default, the StatusBar plugin is disabled for the Kendo UI project templates and sample apps. This might cause styling issues on iOS 7 devices and in the device simulator.
    Workaround: Initialize your Kendo UI application with the black translucent status bar style. For example:

    app.application = new kendo.mobile.Application(document.body, { layout: "tabstrip-layout", statusBarStyle: "black-translucent" });
      }, false);`
    
  • If the StatusBar custom plugin is enabled and you initialize your Kendo UI app with the black translucent status bar style, the app might not render properly on iOS 7 or later devices. The header might be too large and the footer might be truncated.
    Workaround: Disable the StatusBar plugin and re-build your app.

  • When you run a Kendo UI Core or Kendo UI Professional project on a mobile device, the footer might render above the bottom border of the screen and a gap might appear between the footer and the bottom of the screen.
    A known issue in jQuery Mobile might cause the footer to not render properly in Kendo UI Core, Kendo UI Professional or jQuery Mobile projects. A gap might appear between the footer and the bottom border of the screen.
    Workaround: Set the height and the min-height attributes of the <body> element of your app to 100%. For example, replace the opening <body> tag with the following code.

    <body style="height:100%;min-height:100%">
    
  • The built-in Kendo UI mobile app and Kendo UI mobile app with data visualization sample apps run in different color schemes in the Windows Phone device simulator and on a physical Windows Phone device.
    The built-in Kendo UI mobile app and Kendo UI mobile app with data visualization templates run in a light color scheme in the Windows Phone device simulator and in a dark color scheme on a physical Windows Phone device.
    Workaround: None.

  • When you are running the Kendo UI mobile app with data visualization sample app on Android devices, you cannot view chart values. You can tap the chart to select the value, but the label for the value does not appear.

NativeScript

AppBuilder 3.7.x introduces the following issue with NativeScript.

  • In the extension for Visual Studio, you cannot redeploy NativeScript apps in the Microsoft Visual Studio emulator.
    Workaround: Uninstall the app and deploy it again.

AppBuilder is known to have the following issues with NativeScript from earlier releases.

  • In Microsoft Visual Studio with TypeScript 2.0.x installed, when you build the NativeScript Groceries sample app and deploy it on a device, the app becomes unresponsive and needs to close.
    Workaround: Install TypeScript 2.1.x for Microsoft Visual Studio version or later.

  • In the extension for Visual Studio, you cannot use the built-in AppBuilder debug tools to debug Angular 2-based NativeScript apps on connected Android devices. When you attempt to debug the app, it becomes unresponsive on the device and needs to close.
    Workaround: Use the Microsoft Visual Studio debug tools instead.

  • After updating your NativeScript app to be able to use the latest TypeScript improvements, transpilation of native iOS or Android calls no longer works.
    Starting with AppBuilder 3.5, NativeScript apps no longer contain the typings/tns-core-modules directory and the android17.d.ts and ios.d.ts files. These files provide TypeScript definitions for native iOS and Android calls.
    Workaround: None.

  • After updating your NativeScript app to be able to use the latest TypeScript improvements, code completion for native iOS or Android calls no longer works.
    Starting with AppBuilder 3.5, NativeScript apps no longer contain the typings/tns-core-modules directory and the android17.d.ts and ios.d.ts files. These files provide TypeScript definitions for native iOS and Android calls.
    Workaround: None.

  • If your app targets NativeScript 2.2.0 and contains nested Observable objects, you cannot run it on device. When you deploy and run the app, it becomes unresponsive and closes with the following error message: TypeError: Cannot set property 'disableNotifications' of undefined..
    Workaround: Migrate your app to NativeScript 2.3.0.

  • You cannot build NativeScript apps if you have declared one or more dependencies using mixed casing (for example, KebabCase or camelCase).
    AppBuilder cannot resolve non-lowercase-only dependencies properly.
    Workaround: Manually change the mixed casing declarations to lowercase declarations.

    1. Open the package.json in the root of your app.
    2. Modify non-lowercase dependencies to be lowercase. For example: change nativescript-IQKeyboardManager to nativescript-iqkeyboardmanager.
    3. Save changes.
  • You cannot run NativeScript apps in the device simulator.
    Workaround: None. Run your app on device or in the native emulators.

  • Sometimes, the NativeScript developer app for Android becomes unresponsive and needs to close after the synchronization of changes completes.
    Workaround: Restart the developer app.

  • Sometimes, you cannot LiveSync changes to the NativeScript developer app for Android over cable.
    Workaround: Verify that the time and date on the mobile device and your computer match.

  • If a plugin for NativeScript contains .gz files, you cannot build for Android.
    Workaround: Remove the plugin or migrate it to a version which does not contain .gz files and try again.

  • Migrating between NativeScript versions completely replaces the tns_modules folder. Any plugins or files will be lost.
    Workaround: To be able to use any plugins, make sure that they are available as npm packages and list them in the dependencies section in the package.json file in the root of the project. The AppBuilder will resolve them on build. For more information about the dependencies syntax, see Specifics of npm's package.json handling. For more information about working with custom NativeScript plugins, see Use plugins in your NativeScript apps.

  • On Android 5.1 devices, when you restore a minimized app, the app becomes unresponsive and closes.
    Workaround: Restart the app.

  • Sometimes when you debug your NativeScript project on an iOS device, the app might exit on device and the debug session might end.
    Workaround: Restart the app and try again.

  • You cannot debug your NativeScript projects on Android devices and emulators in the command-line interface.
    Workaround: Debug your project in the classic Windows desktop client or the extension for Visual Studio.

  • You cannot debug your NativeScript project on multiple connected devices simultaneously.
    Workaround: Debug on one device or emulator at a time.

See Also

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.