Known Issues with the Command-Line Interface and the Package for Sublime Text

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 command-line interface and package for Sublime Text are known to have the following issues.

AppBuilder 3.7.x introduces the following issue with the command-line interface.

  • In the command-line interface, when you downgrade your app to target Apache Cordova 4.0.0, all core plugins are enabled.
    Workaround: Disable any unused core plugins.

  • In the command-line interface, the Telerik Platform Enterprise subscriptions are shown as Business subscriptions.
    Workaround: None.

The command-line interface and package for Sublime Text are known to have the following issues from earlier releases.

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

  • When you run $ appbuilder fetch or $ appbuilder find, you might receive the following error message: CALL_AND_RETRY_LAST Allocation failed - process out of memory.
    When you are running a 32-bit Node.js, you cannot run fetch and find operations because of memory limitations.
    Workaround: Choose between the following workarounds:

    • (Recommended) Install 64-bit Node.js.
    • Run the fetch and find operations using the following alternative syntax:

      node --max-old-space-size=2000 <Path to .../bin/appbuilder.js> <fetch OR find>
      
  • 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 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.

  • On macOS systems with Node.js 0.12.x, appbuilder create <Name> and appbuilder create screenbuilder <Name> operations might not release the console after the app is created.
    Workaround: Press Ctrl+C to release the console manually.

  • On macOS and Linux systems, you might not be able to install the command-line interface or run it using sudo, if you have installed Node.js from http://nodejs.org/. You might experience gyp WARN EACCES user "root" does not have permission to access the dev dir "/ errors.
    The following known behavior of npm causes this issue.
    Workaround: Uninstall the command-line interface and install it again using sudo npm install appbuilder -g --unsafe-perm.

  • 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 apps on Android devices and emulators on macOS systems.
    Workaround: Debug your app in the classic Windows desktop client or the extension for Visual Studio.

  • You cannot debug your NativeScript app on multiple connected devices simultaneously.
    Workaround: Debug on one device 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.

  • In Sublime Text 2, you cannot work with apps whose names contain non-ASCII characters.
    Workaround: Rename your app to contain only ASCII characters or upgrade to Sublime Text 3.

  • On Windows systems, 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 run appbuilder simulate, the command-line interface does not compile your TypeScript automatically.
    Workaround: Before running your app in the device simulator, run appbuilder build <Platform> first to trigger the TypeScript compilation.

  • When you run appbuilder simulate, the command-line interface does not LiveSync changes to your TypeScript automatically.
    Workaround: Close the device simulator, run appbuilder build <Platform> to trigger the TypeScript compilation and appbuilder simulate to run the app in the simulator again.

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

  • The command-line interface does not automatically compile TypeScript to JavaScript when you run the livesync command with the --watch option.
    Workaround: You can choose between the following workarounds.

    • Deploy your app via QR code and LiveSync your changes with the three-finger refresh gesture. Note that you need to run appbuilder livesync cloud before using the three-finger refresh gesture on device.
    • Re-build and re-deploy your app via cable connection to reflect changes to your TypeScript code.
  • 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 on Windows systems, the command-line interface does not show the contents of index.html in the Sources tab.
    Workaround: In the main menu bar of the simulator, click Refresh.

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

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