This document contains limitations and known issues when working with UFT Mobile.

Installation and upgrade


SSO: When switching to SSO mode to non-SSO mode and vice versa, the browser cache needs to be cleared to allow a proper workflow.

Exploratory testing (iOS): A screenshot of the Start Record command is not recorded and not saved to the report log.

iOS Agent signing API:  Plug and play will fail if a device UDID  exists in two different profiles, and one of these profiles has expired.
Workaround: Delete the expired profile.

Auto-dismiss system alerts: When the auto-dismiss system alerts when idle option is enabled on older iOS device models (devices released three years ago or more), there is a one minute delay before the alert is automatically dismissed. This is due to reduced performance on these devices as a result of running new iOS versions on old hardware.

Multi-workspace mode: Links to the URL of a specific device are not supported when using MSP mode.

Genymotion Cloud devices: Genymotion virtual devices that are powered on again after a UFTM server restart, constantly show a status of connecting and are not created in the Genymotion cloud.

DexGuard/ ProGuard: Security tools which are used to protect apps against different risks, for example those of Guardsquare, may interfere with the UFTM app packaging, as expected.

To avoid such issues you can use the non-packaged app. If the packaged app is required, ask developers to provide builds for testing without the protection, or look for a workaround for the issue you encountered in the Troubleshooting section of the online help.

Record and replay - general

Record and Replay: Android specific

Record and Replay: iOS specific

Packaged apps

Non-packaged apps

Android non packaged apps:

iOS non-packaged apps:

AWS server and Amazon Device Farm

  • Device logs are not available for ADF devices.
  • Amazon fire devices are not supported.
  • Test duration on AWS is limited to 150 minutes. To extend this time, contact Amazon.
  • You cannot set a reservation for an ADF device.
  • For UFT integration, you cannot run a test in which a single script uses multiple ADF devices. You can however, run iterations of a single test, using parameters to specify a different capability set for each iteration.
  • If you chose a device based on capabilities, but did not specify an exact operating system, the device will not appear in the UFT Mobile console until after the device initialization is complete.
  • The execution status of the test as displayed in Amazon does not match the actual functional execution status of the test. The execution status of the test should be monitored in UFT test report.
  • When viewing the UFT Mobile console located on an AWS machine, you may experience a delay in the refreshing of the data.

  • On some applications, native alerts are not recognized.

Native browsers

Micro Focus Testing Tools

For known issues when using UFT Mobile with a Micro Focus Testing tool, refer to the help center of the tool that you are using.