Limitations of the Device Simulator

When possible, run your app on a physical device in addition to running it in the simulator. Running on device provides the most accurate test results but running in the simulator is essential for debugging.

When you run apps in the device simulator, keep in mind the following limitations.

Apache Cordova Core Plugins in the Device Simulator

This table shows the core plugins that the device simulator supports across the AppBuilder clients.

Plugin Windows macOS
In-Browser Client Windows Client Extension for Visual Studio Command-Line Interface In-Browser Client Command-Line Interface
Device Motion (Accelerometer)
Battery Status
Camera
Media Capture (Capture)
Device Orientation (Compass)
Network Information (Connection)
Console
Contacts
Device
File (FileSystem)
File Transfer
Geolocation
Globalization
InAppBrowser  *  *  *  *  *
Keyboard
Media  **  **  **  **
Dialogs (Notification)
SplashScreen
StatusBar
Vibration
Whitelist

* You cannot test different targets for window.open('url','_target'). The device simulator always opens links in an external window.

** You can test only media.play, media.stop and media.pause in the device simulator.

Apache Cordova Integrated Plugins in the Device Simulator

This table shows the integrated plugins that the device simulator supports across the AppBuilder clients.

Plugin Windows macOS
In-Browser Client Windows Client Extension for Visual Studio Command-Line Interface In-Browser Client Command-Line Interface
BarcodeScanner
ChildBrowser
PushPlugin
SQLite Plugin
Whitelist

Telerik Verified Plugins in the Device Simulator

You can test the following plugins from the Telerik Verified Plugins Marketplace in the device simulator. Telerik Verified Plugins Marketplace plugins which are not listed here are not supported.

Plugin iOS Android Windows Phone
Progress Analytics

Custom Plugins in the Device Simulator

You cannot test custom plugins in the device simulator.

Mobile Platforms in the Device Simulator

Android in the Device Simulator

You cannot test changes in AndroidManifest.xml and config.xml for Android.

iOS in the Device Simulator

  • You cannot test changes in Info.plist and config.xml for iOS.
  • You cannot test Apple Watch bundles.

Windows Phone in the Device Simulator

  • You cannot test changes in WMAppManifest.xml and config.xml for Windows Phone.
  • In the device simulator, the Windows Phone user interface appears different than the Windows Phone user interface on device.

Other Limitations

  • The device simulator does not simulate iOS, Android and Windows Phone accurately in Mozilla Firefox.
  • The device simulator does not simulate iOS and Android accurately in Internet Explorer.
  • The device simulator does not simulate touchend events correctly.
  • In the in-browser client, the simulator runs in the browser and might be affected by its cross-origin limitations.
    When you send a request from the app to a service in a different domain, the cross-origin limitations of the browser apply to the target URL if the URL is not CORS compliant. This is a security limitation of the browser.
    When you run the in-browser client in Chrome and the device simulator encounters a possible CORS error, it will prompt you to install the AppBuilder Helper for Chrome. This extension enables CORS for the device simulator in the in-browser client to let you test network requests to non-CORS-compliant URLs.
  • In the in-browser client, you cannot create your own custom devices.
  • On macOS systems, the device simulator does not respect the device orientation limitations set in the app properties or the configuration files.
  • On macOS systems, you cannot take screenshots in the device simulator.
  • On macOS systems, you cannot test 9-patch images in the device simulator.

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.