Known Issues

Micro Focus Mobile Center

Software Version: 3.2


Publication date: August 2019

Software release: August 2019


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

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.

Saving filter preferences: In Windows 8.1, if you are using Internet Explorer version 11.0.23 as a non-admin user:

These limitations result from Internet Explorer not allowing local storage access. These limitations do not apply if you launch the browser as an administrator.


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

Whitelisted on-premises server

The following items apply when working with an on-premises server with a whitelisted connector:

Native browsers

ALM Mobile Center extension

The following are additional limitations when using the ALM Mobile Center extension:

Multi-project feature

The following are additional limitations when using Mobile Center's multi-project feature. The multi-project capability is part of the Early access features.

UFT with Mobile Center

The following are additional limitations when using Unified Functional Testing (UFT) with Mobile Center.

Getting started
Editing tests
Web testing
Specific types of apps

Working with UFT 14.00

If you have upgraded your version of Mobile Center and continuing to work with UFT 14.00, you may need to re-select your apps in the Record and Run Settings dialog box.

To do this, clear your app selections and either refresh the drop-down to show the updated options, or use the Mobile Center wizard to re-select your apps.

UFT also has newer versions available. For details, see Unified Functional Testing (UFT) and What's New in UFT.

Connecting to Mobile Center

If either your UFT or Mobile Center sessions are invalid, due to license issues or timeout from the Mobile Center server, when pressing the Test Connection in the Mobile pane of the Options dialog in UFT gives you an operation timeout.

Workaround: Exit from UFT and Mobile Center as necessary and make sure your licenses are correctly installed for the correct products. Then reconnect to UFT and Mobile Center.

UFT and multiple Mobile Center workspaces

The following known issues exist for selecting mobile apps and working with multiple workspaces:

Running UFT tests with Mobile Center

Parallel testing. Additional known issues for parallel testing are listed in the UFT Help Center. For details, see Known issues - Run sessions.

Switching back from StormRunner Functional

If your Record and Run Settings are defined to use StormRunner Functional on the Mobile tab, UFT may show an error when selecting the Open Application in Mobile Center option.

If this occurs, update your Record and Run Settings to use Mobile Center, and try again.

Selecting devices and launching browsers

To avoid errors, ensure that the methods used to lock your device and launch a browser on the same device are consistent between your Record and Run Settings and your test steps.

Record and Run Settings Test Step Method
Specific device selected Use the same device ID in your test step with the LaunchMobileBrowserWithID method.
Device capabilities defined to lock any matching device Use the same device capability parameters in your test step with the LaunchBrowser method.

For more details, see the LaunchBrowser and LaunchMobileBrowserWithID method documentation in the UFT Object Model Reference.

Fingerprint simulations

Step results for failed fingerprint simulations may show differently, depending on the app's configured behavior.

Switching between the Device Capabilities and Specific Device tabs

Sometimes, when configuring the Record and Run Settings in UFT, if you switch between the Device Capabilities and the Specific Device tab, and then click the Open in MC button to open the Mobile Center wizard, the Mobile Center wizard opens the Device capabilities tab.

Workaround: Do one of the following:

Multiple devices in test runs

Unexpected issues may occur when you are running a test with a MobileWebView test object on multiple devices.

If so, remove the accessibilityid description property from the test object and run the test again.

Device filtering in test runs: Testing multiple devices

If you have multiple steps in your test that use the same device filtering criteria defined by description properties, and also have multiple devices connected to Mobile Center that match the filtering criteria, all relevant steps use the same device used by the first step in your test.

To use a different device in a specific step, modify the filter for that step.

Device filtering in test runs: Modifying your filter

If your device filter is defined by description properties, and you modify those properties before running the test a second time, the device remains locked from the first run, and the second test run will fail.

Unlock the device in Mobile Center before running the test a second time.

Device filtering in test runs: Multiple steps with different device filters

If your test has separate steps with different device filters for each step, where the device filters do not conflict (the same device matches each filter), and:

To use the same device, modify the filter so that the properties match in all relevant steps.

For example, if you have a single device connected that matches the filters in both of the following steps, the test will fail on the second step.

Device("osversion:=8.4","ostype:=iOS").App("name:=MC Browser","identifier:=com.hp.HPMobileWebBrowserINJ").MobileEdit("nativeclass:=UITextField","mcindex:=0","ispassword:=False","class:=Input","accessibilityid:=url").Set "AAA"
Device("ostype:=iOS").App("name:=MC Browser","identifier:=com.hp.HPMobileWebBrowserINJ").MobileEdit("nativeclass:=UITextField","mcindex:=0","ispassword:=False","class:=Input","accessibilityid:=url").Set "BBB"

Modify the steps as follows to run the test:

Device("ostype:=iOS").App("name:=MC Browser","identifier:=com.hp.HPMobileWebBrowserINJ").MobileEdit("nativeclass:=UITextField","mcindex:=0","ispassword:=False","class:=Input","accessibilityid:=url").Set "AAA"
Device("ostype:=iOS").App("name:=MC Browser","identifier:=com.hp.HPMobileWebBrowserINJ").MobileEdit("nativeclass:=UITextField","mcindex:=0","ispassword:=False","class:=Input","accessibilityid:=url").Set "BBB"

Run results

Browser steps

Device information is not included in the HTML run results for Browser steps run on specific devices.

Local system monitoring If both Device Metrics and Local System Monitor are enabled for your UFT test or component, the run results show mobile device metrics only.

Device logs

If you start recording with the Logs option cleared in the Device Metrics and then stop recording, but resume recording with the option selected, the Download device logs button (in the device Options panel) is not available.

Workaround: Press the Refresh button in the remote access window.

Visual Relation Identifier steps

If the first step in your test uses Visual Relation Identifiers (VRI) to identify an object, your app is not launched, installed, or restarted, even if defined to do so otherwise.

Workaround: Ensure that your app is launched, installed, or restarted before using VRI to identify a test object.

Back to UFT

Spying and highlighting with Mobile Center

Back to UFT

UFT text recognition and Mobile Center

Back to UFT


If you use wildcards in your WebUtil.LaunchBrowser steps to perform a fuzzy search for devices, you must also provide an operating system.

For example, the following step may generate errors:

WebUtil.LaunchBrowser "MOBILE_SAFARI","iPhone","",""

Prevent errors by providing an operating system. For example:

WebUtil.LaunchBrowser "MOBILE_SAFARI","iPhone","","iOS"

Back to UFT

Sensor simulation operations

Back to UFT

Business Process Testing and Mobile Center

Back to UFT

Recording with UFT

MobileView object

The MobileView object is not recorded on Android apps.

Instead, you can create it manually in the object repository and do the following:

  • Set the isscrollable property to true.
  • Set the mcindex property.
  • Set the class property according to the actual type of scrollable control. (You can use the Object Spy to verify the class.)
  • Remove all other properties (remove the properties—do not leave them blank).

Scroll and horizontal scroll on Android is not recorded on UFT.

Bitmap checkpoints

When recording on iOS and the native browser, bitmap checkpoints placed after scrolling down to the next page in the browser, will always fail when playing the test.

Workaround: After recording, update the tolerance for the bitmap checkpoint to a value between 5% and 10%.

Back to UFT

Non-packaged apps and UFT

Mobile Stepper test objects

The Mobile Stepper test object is not supported for non-packaged apps on iOS devices.

On Android devices, these objects are recognized as MobileButton or MobileLabel objects.

MobileList.Delete method

The MobileList.Delete method is not supported for non-packaged apps.

Instead, swipe left on the list item and tap the Delete button to perform this step.

MobileDropdown.Select method Replay is not supported for the MobileDropdown.Select method on non-packaged apps.
ChildObjects method

The Container property is not supported for non-packaged apps on iOS.

The NativeClass and hint properties are not supported for non-packaged apps on Android.

Required object description filter When testing non-packaged apps using the ChildObjects method, you must add a filter to the object description before the ChildObjects step. For example, see Object description filter - example.
Standard checkpoints, iOS devices

Existing tests with standard checkpoints may fail if the following properties are included in the checkpoint properties:

  • isFocused
  • isChecked
  • isFocusable
  • isCheckable

If you have these properties in tests created before UFT 14.02, and are running your test on iOS non-packaged apps, avoid errors as follows:

Update your test to include a Boolean value (True/False) for these properties instead of a Null value.

Object description filter - example

Set oDesc = Description.Create()
	oDesc("class").Value = "Button"

Set Buttons = Device("Device").App("UICatalog_2").ChildObjects(oDesc)
NumberOfButtons = Labels.Count()

For i = 0 To NumberOfButtons - 1

Back to UFT

Testing SAP Fiori apps with Mobile Center

If your test was created for a desktop version of a Fiori application, you may need to modify the test to ensure it runs correctly on the mobile version.

Additionally, different resolutions on different devices may cause differences in an object's properties and behavior. You may need to manually edit the test script to support multiple devices.

The following versions of the Microsoft Edge browser are supported:

Tip: Add an Exist statement to ensure that an object is completely loaded on a page in a Fiori mobile application before running steps on that object.

Specific SAP objects and methods


The SAPUIRadioGroup test object is not supported for Fiori applications.

SAPUITextEdit / SAPUIButton

Sometimes, when using SAPUITextEdit and SAPUIButton objects, the test steps are recorded in the incorrect order.

If this happens, change the order of the steps manually.


The SAPUITextEdit test object html tag identification property now uses the parent DIV element (instead of the INPUT element).

You must update any:

  • Tests that include checkpoints, output values or GetROProperty("html tag") steps on the SAPUITextEdit test object.
  • SAPUITextEdit objects you have in your object repositories.


The SAPUIDialog.Close button works only when a dialog contains a X close button.

Standard checkpoints and output values in SAP Fiori apps

When inserting standard checkpoints and output values to an already recorded test, and running standard checkpoint and output value steps on Fiori mobile applications, the test object must be fully visible in the Mobile Center remote access window.

This is relevant when editing the test, and not when recording it.

Fiori 1.6x client freezes

The remote access display does not support apps using the Android FLAG_SECURE window flag. For details, see WindowManager.LayoutParams.html. To use such apps with Mobile Center you need to remove the flag. See the Mobile Center help for details.

Back to UFT

Using the MC Browser app with UFT

Run Results Viewer

When tests are run on the MC Browser app, CSS elements may be displayed erroneously in the Captured Data pane of the Run Results Viewer (not relevant for HTML report).

Network virtualization and the MC Browser app

When using Network Virtualization and testing the Mobile Web app without enabling mobile testing on the Mobile tab of the Record and Run Settings dialog box, you must add the device ID in the object repository, or use descriptive programming to identify a device.

This limitation does not apply when testing is enabled on the Mobile tab.

Running Web tests using the MC Browser app
  • Ensure that the MC Browser app is installed on the test's devices before running the test.
  • Some Browser methods are not supported.

    Test steps that include unsupported commands are skipped, and do not cause the test to fail. Instead, relevant warnings are displayed in the run results.

    Unsupported methods include:

    • .ClearCache
    • .Close
    • .CloseAllTabs
    • .DeleteCookies
    • .DialogExists
    • .FullScreen
    • .GetDialogText
    • HandleDialog
    • .Home
    • .IsSiblingTab
    • .OpenNewTab

Back to UFT

Shadow Dom support

Running mobile tests on Shadow Dom web apps and iOS devices is only supported for:

Back to UFT

Using the Chrome emulator with UFT

Multiple tabs

Multiple tabs are not supported, as well as the Browser.OpenNewTab and Browser.CloseAllTabs methods.

Unsupported methods may cause unexpected behavior when run in the emulator.

Object Spy

The Object Spy and Highlight in Application (from the Object Spy) are not supported for the emulator.

Test objects added while recording using the emulator cannot later be highlighted from the object repository.

Checkpoints and output values

Checkpoints and output values cannot be added during recording and must be added manually when editing test steps.

Maintenance mode

Maintenance mode is not supported.

Test objects
  • The WebFile object is not supported.
  • Adding objects from the object repository is not supported.

Back to UFT

Native browsers and UFT

UFT on Windows Server 2012 R2

Native browsers are not supported when running UFT on Windows Server 2012 R2.

Test object description properties

Native browsers, including Chrome on Android and Safari on iOS, do not relate to test object description properties.

Therefore, data driving on native browsers relates to data defined in the Data table or test parameters only, and will not search for test objects with matching test object property values.

Device logs

When running a test via UFT on a native browser or the MC Browser app, device logs are generated only when users:

  • Enable the Device Metrics Logs in the Mobile tab of the Record and Run Settings in UFT for the specific device, and
  • Select the Use settings in Mobile tab option in the Web tab of the Record and Run Settings dialog box
WebAudio / Web Video objects
  • When running a test on a Chrome browser, ensure that you disable the Chrome setting Gesture requirement for media playback before running tests containing WebVideo and WebAudio objects.
  • The .Play method is not supported for WebVideo and WebAudio objects on iOS devices.

Define an initial URL

Test runs may fail if the same script is run multiple times without an initial URL to start the test with.

To avoid errors, define a URL for your test in the Record and Run Settings dialog.

iframe objects

UFT cannot record on iframe objects in iOS devices when the code of objects inside the iframe use document.write().

Bitmap checkpoints

On iOS native browsers, bitmap checkpoints inserted while recording, and after having scrolled to a following page, are not supported. Such checkpoints will fail.

Switching devices

UFT cannot switch devices while running a single native browser script.

Native apps and UFT

UFT cannot record or run steps on native mobile controls, such as a native date picker when working in a native browser or the MC Browser.

Workaround: Add the native mobile control to the object repository manually, and then manually add a step to operate the control.

For example:

  1. Spy on a date picker control, and add the corresponding WebEdit object to the Object Repository.

  2. Then add a step similar to the following to your test:

    Browser(“Reservations”).Page(“Your Reservation”).WebEdit(“check-in-date”).Click

iOS, native, packaged apps and the ChildObjects method

If a ChildObject step is run on an iOS, native, packaged app (Device().App().MobileObject().childobjects()), and the MobileObject is not found, the step returns all childobjects on the current page being tested.

Hybrid apps and UFT

The following features are not supported when testing hybrid applications:

Certain hybrid apps may issue an error "This test was created using an earlier version of UFT and therefore requires a different JavaScript engine".

This can happen if the app is launched by another app or from HOME.

Workaround: Have the app launched by the testing tool. Stop the recording, restart the app, but do not reinstall. Begin recording again. Alternatively you can use this Javascript code:

Device("<Device>").App("<appname>").Launch DoNotInstall,Restart

Note: Some features not supported for mobile in general are supported when working with hybrid applications. For details, see Unsupported features, test objects, and methods.

Additional limitations:

Keyword View

In the Keyword View, you may not be able to use the Insert run-time object option in the Select Test Object dialog box to insert a .Object statement for a selected test object.

Workaround: Enter the .Object statement manually.

Text checkpoint and output value steps

When recording and running text checkpoint and output value steps, the test object must be fully visible in the remote access window.

WebList steps

Sometimes, when recording a WebList test object step, steps are added for both MobileDropDown and WebList test objects.

This may cause the MobileDropDown step to fail. To avoid this, delete the extra MobileDropDown step.

Recording date and time

Sometimes, when recording the date and time on MobileWeb test objects, native application steps are added in addition to hybrid application steps. This may cause the step to fail during a run session.

Workaround: Delete the extra native application steps.

Run results

CSS elements may be displayed erroneously in the Captured Data pane of the Run Results Viewer (not relevant for HTML report).

Using the Spy If your application does not have a view port defined for the application, if you scroll the page in your application, the area that the Object Spy highlights is offset.

Back to UFT

Working with ALM and Mobile Center

Asset Comparison tool

The Asset Comparison tool does not compare changes in the Record and Run Settings for Mobile tests.

Test object icons

Test object icons for Mobile objects are not displayed in the Test Plan module or for object repositories saved in ALM.

Back to UFT

Using Proxy servers and UFT

Back to UFT


Commas as decimal points

Your localized operating system may use commas as decimal points. This is not supported by UFT, and you may need to manually fix recorded steps to use periods as decimal points instead.

It is recommended to always use the period character as a decimal point, regardless of the locale of your operating system.

Suggested characters

Steps that include Japanese/Chinese characters that were added from the suggested characters line above the keyboard may not run correctly.

Tests created in earlier versions of UFT

Tests created prior to UFT 12.51

For tests that were created on hybrid applications prior to UFT 12.51, only the text, isEnabled, and isFocused properties are supported for checkpoints and output values.

Additionally, you must make sure that UFT re-installs or restarts the app before running steps on the app.

You can:

Tests created in UFT 12.02 Patch 1 or earlier

When working with an object repository in a test created in UFT 12.02 Patch 1 or earlier, the following commands are not supported:

Instead, update the test object descriptions from the application (select the test object and click Update from Application).

Caution: If you are working with MobileLabel test objects that are part of a MobileList test object, updating the description from the application can cause your test to behave unexpectedly.

To update the description of a MobileLabel test object from the application, replace it with a MobileList test object.

In the relevant test steps, replace the steps containing MobileLabel.MakeVisible and MobileLabel.Tap with a single step containing MobileList.Select <index>.

For example, replace:



Device("Device").App("UICatalog").MobileList("list").Select 5

Tests created with Mobile Center versions prior to 1.51

If you have a test of containing steps on hybrid application which was created using Mobile Center versions prior to 1.51, this test is not supported on Mobile Center version 2.01 and later.

Back to UFT

Unsupported features, test objects, and methods

The UFT Mobile Add-in only supports recording and running steps on mobile applications.

When working with mobile objects, the following UFT abilities are not supported, or are only partially supported:

Back to UFT

Amazon Web Services (AWS)

The following known issues exist when using Mobile Center with UFT on AWS:

Back to UFT

LeanFT with Mobile Center

General issues

User interface issues

Test object and method issues

TruClient with Mobile Center

The following are additional limitations when using TruClient with Mobile Center:




Certain versions of software and/or documents (“Material”) accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company.  As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company.  Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.


The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.

Restricted Rights Legend

Contains Confidential Information. Except as specifically indicated otherwise, a valid license is required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Comodo Code Signing Certificate

The code signing certificate for Mobile Center was changed from Verisign to Comodo starting on January 1, 2017.

If you are installing this product on a computer with an older version of Windows, or on a computer without automatic Windows updates, the Comodo root certificate may not automatically be included as a trusted root certificate.

In such cases, we recommend manually configuring Comodo as a trusted root certificate.

For more details, see:

Copyright Notice

© Copyright 2014-2019 Micro Focus or one of its affiliates

Send documentation feedback