Known Issues in the In-Browser Client

Product version: AppBuilder 3.7.4

Released: May 12, 2017

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.

The in-browser client is known to have the following issues.

The in-browser client is known to have the following issues from earlier releases.

  • In the in-browser client, the Bower section in the Manage Packages wizard cannot be loaded and the following error message appears: Package retrieval timed out..
    Workaround: Close and then reopen the Manage Packages dialog and try again.

  • You cannot run NativeScript apps in the device simulator.
    Workaround: None. Run your app on device or in the native emulators.

  • When you attempt to run your app on Windows Phone 8 device, the app becomes unresponsive and needs to close.
    AppBuilder lets you build an app with the Windows Phone 8.1 SDK. If you deploy such an app on a Windows Phone 8 device, the app cannot run. It immediately becomes unresponsive and needs to close.
    Workaround: If you want to test your app on a Windows Phone 8 device, verify that the target SDK is Windows Phone 8.0. For more information, see Configure Your App and Windows Phone Properties.

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

  • In the device simulator, the InAppBrowser Apache Cordova plugin always returns the user agent of your current browser instead of the user agent of the simulated mobile device.
    Workaround: None.

  • When you run two or more AppBuilder clients simultaneously, multiple issues might occur.

    • You might lose changes to your app because of synchronization issues.
    • AppBuilder might not recognize connected devices or might not be able to communicate with connected devices properly. You might not be able to deploy your apps on connected device, debug your code or LiveSync changes via cable connection properly.
    • The app might become corrupted.

    Workaround: Avoid running multiple AppBuilder clients simultaneously.

  • If you are running the in-browser client on an iOS device with a connected Apple Wireless Keyboard, you cannot navigate in the code editor with the arrow keys.
    Workaround: None.

  • In the Telerik Platform, you cannot change the description of existing AppBuilder apps.
    When you attempt to change the description of an existing AppBuilder app, the Telerik Platform shows an error message.
    Workaround: None.

  • The in-browser client might not respect account member permissions in Telerik Platform.
    Account members with Can View permissions might be able to edit and delete AppBuilder apps.
    Workaround: None.

  • When you enable Emmet for the first time, the in-browser client confirms that Emmet is enabled but you cannot expand abbreviations and use actions and filters in the code editor.
    Workaround: Restart the browser.

  • When you invite or remove collaborators for a GitHub repository, the list of collaborators might not refresh simultaneously and it might appear that the operation was unsuccessful.
    When you modify the list of repository collaborators from the in-browser client, GitHub might delay the response to the AppBuilder request. In this case, the list of collaborators does not refresh and it appears that the collaborator was not invited or removed successfully.
    Workaround: Wait a few minutes for the list of collaborators to refresh automatically.

  • Sometimes Diff view does not synchronize rows correctly.

  • When you save changes in the code editor and the device simulator is running, the device simulator reloads your app and returns to the home screen.
    Workaround: None.

  • The simulator does not render properly in Chrome under Windows 7 on VMware Fusion (OSX) with 3D Acceleration.
    Workaround: Disable 3D acceleration on the Windows 7 virtual machine.

    1. Shut down or power off the virtual machine.
    2. From the VMware Fusion menu bar, select WindowVirtual Machine Library.
    3. Select the virtual machine and click Settings.
    4. In the Settings Window, in the System Settings section, select Display.
    5. Deselect Accelerate 3D graphics.
    6. Power on the virtual machine.
  • The Kendo UI Designer executes Kendo UI View events and this might prevent you from using the Kendo UI Designer.
    Workaround: None.

  • The Kendo UI Designer does not show design preview for platform-specific HTML files and does not load platform-specific design resources such as images and CSS files.
    Workaround: None.

  • After you add user interface elements in the Kendo UI Designer, you cannot rearrange them.
    Workaround: To rearrange and format user interface elements, you need to modify your code.
    Alternatively, in the Kendo UI Designer, delete the element that you want to move and add it to your app again.

  • In the Kendo UI Designer, you might not be able to work with Kendo UI Core applications created with earlier versions of AppBuilder.
    The Kendo UI Designer supports only Kendo UI Core 2013.2.918 or later and Kendo UI Professional 2013.2.918 or later and might not load properly apps developed with earlier versions of these frameworks and AppBuilder.
    Workaround: Manually update the Kendo UI libraries in your app or create a new Kendo UI Core or Kendo UI Professional app. For more information, see Update the Frameworks in Your App and Create a New App.

  • The Kendo UI Designer does not refresh automatically to list newly created global functions.
    If index.html is open, the newly created global function will not be listed automatically in the Kendo UI Designer. You will not be able to use the Kendo UI Designer to bind the global function to a user interface element.
    Workaround: Reload the Kendo UI Designer.

    1. Verify that the JS file containing the new global function is referenced in index.html.
    2. In the top menu bar, click SaveSave All to save your changes.
    3. Close index.html and reopen it.
    4. If you have switched to Code view, select RunKendo UI Designer, to run the Kendo UI Designer.

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.