Product version: AppBuilder 3.7.5
Released: August 23, 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 classic Windows desktop client is known to have the following issues.
When you import a custom plugin, it is placed in the root folder of your app instead of the Plugins folder. Referencing the plugin in your app is causing the following error message:
"pluginName is undefined"
Workaround: After you import a custom plugin, you should drag and drop the plugin folder from the root of the app to the Plugins folder.
When you add the Progress AppFeedback plugin, the Feedback service in not enabled
Workaround: Enable Feedback in the in-browser client.
The device simulator does not persist your configuration settings across sessions.
In the classic Windows desktop 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.
In the classic Windows desktop client, you cannot develop TypeScript-based NativeScript apps. When you open such apps, the client becomes unresponsive and needs to close.
You cannot use the built-in resource generator to create the required splash screens for your app.
Workaround: Configure your splash screens manually or use the built-in generator in the in-browser client.
If your Windows user account name contains a special character, you might not be able to run the classic Windows desktop client.
When you attempt to run the classic Windows desktop client, it might become unresponsive and might need to close.
If you delete, rename or move the file for the view currently open in the device simulator, your change is not synchronized on save.
Workaround: Reload the simulator.
When using the built-in AppBuilder debug tools or the debug tools in the device simulator, you cannot edit HTML attributes by double-clicking them.
When you attempt to install or update the universal desktop client or the classic Windows desktop client on Windows systems, a message that AppBuilder is untrusted or not commonly downloaded might appear.
Recently, Windows has started enforcing authenticode code signing and timestamping of third-party applications. This breaking change causes Windows Smartscreen to issue warnings for multiple third-party programs, including AppBuilder.
Workaround: Click Run anyway and proceed with the AppBuilder installation.
You cannot run NativeScript apps in the device simulator.
Workaround: None. Run your app on device or in the native emulators.
If your app 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.
Sometimes when you debug your NativeScript app 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 app on multiple connected devices simultaneously.
Workaround: Debug on one device or emulator at a time.
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.
After you import a custom plugin, you might not be able to open, edit, move or delete one or more files of the plugin.
The classic Windows desktop client stores a local copy of your app. If the file path of a file in this local copy exceeds 256 characters, you will not be able to work with this file.
Workaround: Open your app in the in-browser client, make your changes, save them and continue your work in the classic Windows desktop client.
When you right-click on the device screen in the device simulator, AppBuilder fires the events attached to the UI element on which you clicked.
When you debug on iOS 7.x devices, you cannot view and examine the network requests for your app. The Network pane remains blank.
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.
When you debug apps with the device simulator, the classic Windows desktop client does not show the contents of
index.htmlin the Sources tab.
Workaround: In the main menu bar of the simulator, click Refresh.
Running multiple instances of the classic Windows desktop client might increase the consumption of hardware resources.
AppBuilder does not support running multiple instances of the classic Windows desktop client.
Workaround: To run multiple instances of AppBuilder, open in-browser client in multiple tabs or windows in your browser.
The classic Windows desktop 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.
Attempting to cancel a long-running operation before it completes might cause multiple issues.
In the classic Windows desktop client, you can close the pop-up window for some long-running operations such as build, build and deploy, upload files and others. When you attempt to cancel the operation by closing the window, the classic Windows desktop client does not stop running the operation. If you continue your work while the operation is running in the background, this might cause multiple issues including but not limited to adding exceptions to the log or causing the classic Windows desktop client to stop responding.
Workaround: None. Do not close the pop-up windows for long-running operations before the operations are complete.
In the classic Windows desktop client, you cannot filter or clear the Data, Users, Notifications and Business Logic business logic (cloud code) log. You can only sort it.
Workaround: To filter or clear the business logic (cloud code) log, open it in the Data, Users, Notifications and Business Logic web portal.
- In the Data Navigator, right-click your app.
- Select Show application.
AppBuilder opens the Data, Users, Notifications and Business Logic web portal in your default browser. You might be prompted to log into Data, Users, Notifications and Business Logic in the browser. Use the same login provider you are using with the classic Windows desktop client.
- In the Data, Users, Notifications and Business Logic web portal, click Cloud code log.
The fonts in the device simulator appear pixelated if the DPI size for your display exceeds 100%.
When you increase the DPI size for your display, fonts in the device simulator do not adjust to the change and appear pixelated.
Workaround: Decrease the DPI size to 100%. For more information about how to change this setting in Windows, see Make the text on your screen larger or smaller.
The device simulator might not show fonts in your application accurately.
Workaround: Run your app on a physical device.
If you are accessing the Internet via web proxy that requires authentication, the classic Windows desktop client cannot update automatically.
The classic Windows desktop client is distributed as a ClickOnce application. Microsoft ClickOnce does not support proxy authentication and the classic Windows desktop client application cannot update automatically.
Workaround: Contact AppBuilder support over the AppBuilder forums or in a support ticket.
Sometimes Diff view does not synchronize rows correctly.
If you remove the script reference to
cordova.jsfrom your home page, the device simulator always returns iPhone as the user agent.
Workaround: Verify that
<script src="cordova.js"></script>is present in your home page.
When you launch the simulator, the simulator loads but the device screen remains white or the simulator loads but the application is not rendered properly.
When you launch the simulator, the application is not rendered properly. This might be caused by outdated device drivers for your graphics card or a corrupted simulator module.
- Update the device drivers for your graphics card.
- If updating the device drivers does not resolve the problem, perform a clean install of the classic Windows desktop client.
- Close all running instances of the classic Windows desktop client.
- From the Windows Control Panel, uninstall classic Windows desktop client.
- In a file explorer, navigate to
%localappdata%\Tempand delete the
IceDeviceSimulatordirectory and all its contents.
- Navigate to
%localappdata%\Telerikand delete the
BlackDragondirectory and all its contents.
- Navigate to
%localappdata%\Apps\2.0and delete the contents of the directory.
- Install classic Windows desktop client.
You can use the same
setup.exethat you used for the initial installation.
You cannot play audio or video in the simulator using the <audio> or <video> tags.
Workaround: Run your app on a physical device.
The Kendo UI Designer executes Kendo UI View events and this might prevent you from using the Kendo UI Designer.
The Kendo UI Designer does not show design preview for platform-specific
HTMLfiles and does not load platform-specific design resources such as images and
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.