Known Issues in the Extension for Visual Studio

Product version: AppBuilder 3.7.2

Released: April 24, 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 extension for Visual Studio is known to have the following issues.

AppBuilder 3.7.x introduces the following issues with the extension for Visual Studio.

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

  • In the extension for Visual Studio, your solution cannot contain multiple cloud-connected AppBuilder projects.
    Workaround: Have a separate solution for each cloud-connected project.

  • In the extension for Visual Studio, the Telerik Platform Enterprise subscriptions are shown as Business subscriptions.
    Workaround: None.

  • In the extension for Visual Studio, when you add the Telerik AppFeedback plugin, the Feedback service in not enabled
    Workaround: Enable Feedback in the in-browser client.

The extension for Visual Studio is known to have the following issues 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.

  • The device simulator does not persist your configuration settings across sessions.
    Workaround: None.

  • In the extension for Visual Studio, 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.

  • On iOS devices, when you LiveSync changes that include renaming or deleting files, the synchronization cannot complete and the device is disconnected.
    Workaround: None.

  • Sometimes, when you run the extension for Visual Studio on Microsoft Visual Studio 2017, the IDE might prompt you that the extension is slowing it down.
    Workaround: Ignore the warning and continue your work.

  • 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.

  • The device simulator becomes unresponsive and needs to close when you attempt to take screenshots of apps that contain animations.
    Workaround: None.

  • 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 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.
    Workaround: None.

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

  • 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.

  • 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 project 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 Project and Project Properties for Windows Phone Devices.

  • 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.
    Workaround: None.

  • When you debug on iOS 7.x devices, you cannot view and examine the network requests for your app. The Network pane remains blank.
    Workaround: None.

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

    • You might lose changes to your project 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 project might become corrupted.


    Workaround: Avoid running multiple AppBuilder clients simultaneously.

  • When you debug apps with the device simulator, the extension for Visual Studio does not show the contents of index.html in the Sources tab.
    Workaround: In the main menu bar of the simulator, click Refresh.

  • Attempting to cancel a long-running operation before it completes might cause multiple issues.
    In the extension for Visual Studio, 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 extension for Visual Studio 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 extension for Visual Studio to stop responding.
    Workaround: None. Do not close the pop-up windows for long-running operations before the operations are complete.

  • In the extension for Visual Studio debug tools, you cannot use F8, F10 or F11. When you press any of these keys in the debug tools, the extension for Visual Studio runs the Microsoft Visual Studio-related command instead of the debug tools-related command.
    Workaround: None.

  • In Microsoft Visual Studio 2012 Update 3 and earlier, if you have one or more connected devices and you attempt to open an AppBuilder project while another AppBuilder project is already open, Microsoft Visual Studio becomes unresponsive and needs to close.
    Workaround: Update your copy of Microsoft Visual Studio 2012 to Update 4.

  • Closing the Project Properties dialog saves your changes automatically.
    When you close the Project Properties dialog, AppBuilder does not prompt you to save or discard your changes. Unsaved changes are saved automatically.
    Workaround: Manually undo any changes that you want to discard and press Ctrl+S to save your changes.

  • If you remove the script reference to cordova.js from 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.

  • The device simulator might not show special characters properly.
    The default encoding for projects created with the extension for Visual Studio is the default encoding for your system. If your project contains special characters such as accentuated symbols, the device simulator might not show them properly.
    Workaround: Change the encoding of your files to Unicode.

    1. Open the file that contains the special characters in the code editor.
    2. Select FileAdvanced Save Options.
    3. From the Encoding drop-down menu, select Unicode (UTF-* without signature).
    4. Click OK.
    5. Press Ctrl+S to save your file.
  • 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.

  • 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.
    Workaround:

    • Update the device drivers for your graphics card.
    • If updating the device drivers does not resolve the problem, perform a clean install of AppBuilder.
  • You cannot play audio or video in the simulator using the <audio> or <video> tags.
    Workaround: Run your app on a physical device.

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.