Support Matrix
Micro Focus UFT Mobile

Software Version: 2021, 2021 R1, 2021 R2, 2022

This document, also known as a Product Availability Matrix (PAM), provides information on system requirements, supported operating systems, technologies, and integrations.
Note: UFTM in this document means UFT Mobile unless specifically stated otherwise.

In this topic:

• Server requirements
• Connector requirements
• Apple signing and packaging
• Android support matrix
• iOS support matrix
• Chrome support matrix
• Supported devices
• Micro Focus products
• Integrations
• Additional information
• Limitations

Server requirements

This topic includes list of Server requirements when working with UFT Mobile:

Linux

Name	Version	2021	2021 R1	2021 R2	2022	Remarks
RedHat	8.4	✘	✔	✔	✔
RedHat	8.3	✔	✔	✔	✔
RedHat	8.2	✔	✔	✔	✔
RedHat	8.1	✔	✔	✔	✔
RedHat	8.0	✔	✔	✔	✔
RedHat	7.9	✘	✔	✔	✔
RedHat	7.8	✔	✔	✔	✔
RedHat	7.7	✔	✔	✔	✔
RedHat	7.6	✔	✔	✔	✔
RedHat	7.5	✔	✔	✘	✘
RedHat	7.4	✔	✔	✘	✘
RedHat	7.3	✔	✔	✘	✘
RedHat	7.2	✔	✔	✘	✘
RedHat	7.1	✔	✔	✘	✘
RedHat	7.0	✔	✔	✘	✘
RedHat	6.10	✘	✘	✘	✘
RedHat	6.9	✘	✘	✘	✘
RedHat	6.8	✘	✘	✘	✘
RedHat	6.7	✘	✘	✘	✘
RedHat	6.6	✘	✘	✘	✘
CentOS	8.4	✘	✔	✘	✘
CentOS	8.3	✔	✔	✘	✘
CentOS	8.2	✔	✔	✘	✘
CentOS	8.1	✔	✔	✘	✘
CentOS	8.0	✔	✔	✘	✘
CentOS	7.9	✘	✔	✔	✔
CentOS	7.8	✔	✔	✔	✔
CentOS	7.7	✔	✔	✔	✔
CentOS	7.6	✔	✔	✔	✔
CentOS	7.5	✔	✔	✘	✘
CentOS	7.4	✔	✔	✘	✘
CentOS	7.3	✔	✔	✘	✘
CentOS	7.2	✔	✔	✘	✘
CentOS	7.1	✔	✔	✘	✘
CentOS	7.0	✔	✔	✘	✘
CentOS	6.10	✘	✘	✘	✘
CentOS	6.9	✘	✘	✘	✘
CentOS	6.8	✘	✘	✘	✘
CentOS	6.7	✘	✘	✘	✘
CentOS	6.6	✘	✘	✘	✘
AWS	CentOS 7 (x86_64)	✔	✔	✔	✔	CentOS images published by Centos.org
Azure	CentOS-based 7.5	✔	✔	✔	✔	CentOS images published by Rogue Wave Software

Windows

Name	Version	2021	2021 R1	2021 R2	2022	Remarks
Windows	2022	✘	✘	✘	✔
Windows	2019	✘	✔	✔	✔
Windows	2016	✔	✔	✔	✔
Windows	2012 R2	✔	✔	✔	✔
Windows	2012 R1	✘	✘	✘	✘
Windows	2012	✘	✘	✘	✘
Windows	2008 R2	✘	✘	✘	✘
Windows	11	✘	✘	✔	✔
Windows	10	✔	✔	✔	✔
Windows	8.1	✔	✔	✔	✔
Windows	8	✘	✘	✘	✘
AWS	Microsoft Windows Server 2016 Base	✔	✔	✔	✔	Windows images published by AWS
Azure	Windows Server 2016 Datacenter	✔	✔	✔	✔	Windows images published by Microsoft

Database

Name	Version	2021	2021 R1	2021 R2	2022	Remarks
Postgres	14.x	✘	✘	✘	✔
Postgres	13.x	✔	✔	✔	✔
Postgres	12.x	✔	✔	✔	✔
Postgres	11.x	✔	✔	✔	✔
Postgres	10.x	✔	✔	✔	✔
Postgres	9.6.x	✔	✔	✘	✘

Additional requirements

Requirement	Details
Computer Processor	2.2 GHz or higher dual core processor (Quad core recommended)
Memory	8 GB RAM
Free Hard Disk Space	Installation: 6 GB Database: 5 GB (PostgreSQL installation and data; PostgreSQL can be installed locally or on a different server) Apps storage: For UFT Mobile apps - 200 MB For apps - This will depend on the number of apps being used. For details, see File storage settings. (The apps can be stored locally or in a different location) Cache: This will depend on the number of apps being used. The connector caches every app installed on a device connected to it for 14 days. (Relevant only when using the embedded connector) Temp files: 5 GB
Database	The database come with the installation package. You can also install UFT Mobile by connecting to an external PostgreSQL database instead.
Maximum number of devices connected by USB to server machine	25 devices connected by USB directly to the server machine. Note: Using standalone connectors, you can connect hundreds of devices to UFT Mobile. The maximum number of devices per standalone connector is 25.
Hosted virtualization hypervisors	Hypervisors are supported only for the UFTM server installation. Devices should not be connected directly to the UFTM server but to a UFTM connector which is not installed on the hypervisor.
Protocols & Ports (On-premise)	Server ports are configurable during installation: HTTPS/ WSS (Default. 8443) HTTP/ WS (Default. 8080) Linux only: If you are going to connect iOS devices to this machine via USB, make sure that IPV6 is enabled.
Protocols & Ports (SaaS)	HTTPS/ WSS 443
Protocols & Ports (Devices)	Internal only: Remote access: 5900 Android-specific: 5000 iOS-specific: 12345, 5901

↑Back to top

Connector requirements

You can choose to install the embedded connector, together with the server installation. You can also install the connector as a standalone component, on either a Linux, Windows, or macOS machine. You can install a standalone connector on your testing-tool machine or on multiple machines in distributed locations.

When installing the connector, make sure that the connector machine meets the following requirements:

Linux

Name	Version	2021	2021 R1	2021 R2	2022	Remarks
RedHat	8.3	✔	✔	✔	✔
RedHat	8.2	✔	✔	✔	✔
RedHat	8.1	✔	✔	✔	✔
RedHat	8.0	✔	✔	✔	✔
RedHat	7.9	✘	✔	✔	✔
RedHat	7.8	✔	✔	✔	✔
RedHat	7.7	✔	✔	✔	✔
RedHat	7.6	✔	✔	✔	✔
RedHat	7.5	✔	✔	✘	✘
RedHat	7.4	✔	✔	✘	✘
RedHat	7.3	✔	✔	✘	✘
RedHat	7.2	✔	✔	✘	✘
RedHat	7.1	✔	✔	✘	✘
RedHat	7.0	✔	✔	✘	✘
RedHat	6.10	✘	✘	✘	✘
RedHat	6.9	✘	✘	✘	✘
RedHat	6.8	✘	✘	✘	✘
RedHat	6.7	✘	✘	✘	✘
RedHat	6.6	✘	✘	✘	✘
CentOS	8.4	✘	✔	✘	✘
CentOS	8.3	✔	✔	✘	✘
CentOS	8.2	✔	✔	✘	✘
CentOS	8.1	✔	✔	✘	✘
CentOS	8.0	✔	✔	✘	✘
CentOS	7.9	✘	✔	✔	✔
CentOS	7.8	✔	✔	✔	✔
CentOS	7.7	✔	✔	✔	✔
CentOS	7.6	✔	✔	✔	✔
CentOS	7.5	✔	✔	✘	✘
CentOS	7.4	✔	✔	✘	✘
CentOS	7.3	✔	✔	✘	✘
CentOS	7.2	✔	✔	✘	✘
CentOS	7.1	✔	✔	✘	✘
CentOS	7.0	✔	✔	✘	✘
CentOS	6.10	✘	✘	✘	✘
CentOS	6.9	✘	✘	✘	✘
CentOS	6.8	✘	✘	✘	✘
CentOS	6.7	✘	✘	✘	✘
CentOS	6.6	✘	✘	✘	✘

Windows

Name	Version	2021	2021 R1	2021 R2	2022	Remarks
Windows	2022	✘	✘	✘	✔
Windows	2019	✘	✔	✔	✔
Windows	2016	✔	✔	✔	✔
Windows	2012 R2	✔	✔	✔	✔
Windows	2012 R1	✘	✘	✘	✘
Windows	2012	✘	✘	✘	✘
Windows	2008 R2	✘	✘	✘	✘
Windows	11	✘	✘	✔	✔
Windows	10	✔	✔	✔	✔
Windows	8.1	✔	✔	✔	✔
Windows	8	✘	✘	✘	✘

MacOS

Name	Version	2021	2021 R1	2021 R2	2022	Remarks
MacOS	12.4	✘	✘	✘	✔
MacOS	12.0	✔	✔	✔	✔
MacOS	11.6	✔	✔	✔	✔
MacOS	11.5	✔	✔	✔	✔
MacOS	11.4	✔	✔	✔	✔
MacOS	11.3	✔	✔	✔	✔
MacOS	11.2	✔	✔	✔	✔
MacOS	11.1	✔	✔	✔	✔
MacOS	11.0	✔	✔	✔	✔
MacOS	10.15	✔	✔	✔	✔
MacOS	10.14	✔	✔	✔	✔
MacOS	10.13	✘	✘	✘	✘
MacOS	10.12	✘	✘	✘	✘
MacOS	10.9	✘	✘	✘	✘
MacOS	10.8	✘	✘	✘	✘

Additional requirements

Requirement	Details
Computer Processor	2.2 GHz or higher dual core processor (Quad core recommended)
Memory	4 GB RAM
Free Hard Disk Space	Installation: 6 GB Cache: This will depend on the number of apps being used. The connector caches every app installed on a device connected to it for 14 days. Temp files: 5 GB
Maximum number of devices connected by USB to connector machine	25 devices connected by USB directly to the server machine. Note: Using standalone connectors, you can connect hundreds of devices to UFT Mobile. The maximum number of devices per standalone connector is 25.
Protocols & Ports (On-premise)	Connector ports are configurable during installation: HTTPS/ WSS (Default. 8443) HTTP/ WS (Default. 8080) Linux only: If you are going to connect iOS devices to this machine via USB, make sure that IPV6 is enabled.
Protocols & Ports (SaaS)	Connector ports are configurable during installation: HTTPS/ WSS (Default. 8443) Linux only: If you are going to connect iOS devices to this machine via USB, make sure that IPV6 is enabled.
Protocols & Ports (Devices)	Internal only: Remote access: 5900 Android-specific: 5000 iOS-specific: 12345, 5901

↑Back to top

Apple signing and packaging

The following software is supported for the packaging service / iOS enabler machine:

MacOS

Name	Version	2021	2021 R1	2021 R2	2022	Remarks
MacOS	12.5	✘	✘	✘	✘
MacOS	12.4	✘	✘	✘	✔
MacOS	12.0	✔	✔	✔	✔
MacOS	11.5	✔	✔	✔	✔	Not compatible with Xcode 13.3 or later
MacOS	11.4	✔	✔	✔	✔	Not compatible with Xcode 13.3 or later
MacOS	11.3	✔	✔	✔	✔	Not compatible with Xcode 13.3 or later
MacOS	11.2	✔	✔	✔	✔	Not compatible with Xcode 13 or later
MacOS	11.1	✔	✔	✔	✔	Not compatible with Xcode 13 or later
MacOS	11.0	✔	✔	✔	✔	Not compatible with Xcode 13 or later
MacOS	10.15	✔	✔	✔	✔	Not compatible with Xcode 13 or later
MacOS	10.14	✔	✔	✔	✔	Not compatible with Xcode 13 or later
MacOS	10.13	✘	✘	✘	✘	Not compatible with Xcode 13 or later
MacOS	10.12	✘	✘	✘	✘	Not compatible with Xcode 13 or later
MacOS	10.9	✘	✘	✘	✘	Not compatible with Xcode 13 or later
MacOS	10.8	✘	✘	✘	✘	Not compatible with Xcode 13 or later

Additional requirements

Requirement	Details
Xcode	Version 13 or later. Note: Full installation of Xcode (install from App Store) is needed for the iOS packager. For the minimum OS version required for Xcode, see the Apple developer documentation.

↑Back to top

Android support matrix

The table below shows the Android versions supported by each UFT Mobile version:

Android version	2021	2021 R1	2021 R2	2022	Remarks
13	✘	Patch 3	Patch 2	✔
12	Patch 1	✔	✔	✔
11	✔	✔	✔	✔
10	✔	✔	✔	✔
9	✔	✔	✔	✔
8.x	✔	✔	✔	✔
7.x	✔	✔	✔	✔
6.x	✔	✔	✔	✔
5.x	✔	✔	✔	✘
4.4.4	✔	✘	✘	✘

↑Back to top

iOS support matrix

The table below shows the iOS versions supported by each UFT Mobile version:

iOS version	2021	2021 R1	2021 R2	2022	Remarks
17.0	✘	✘	✘	✘	Due to important technical changes by Apple, iOS 17 support is currently not available for previous releases of Digital Lab. Initial support for macOS connector will be available in the next release, with support for Linux/Windows to follow in a later release. It is highly recommended NOT to perform the upgrade to iOS 17 for devices connected to Digital Lab until official support is available.
16.6	✘	✘	Patch 3 (*)	Patch 3 (*)	(*)Developer Mode should be enabled. For details, see the Apple Developer documentation. (**) Developer image to be deployed
16.5.1	✘	✘	Patch 3 (*)	Patch 2 (*)(**)	(*)Developer Mode should be enabled. For details, see the Apple Developer documentation. (**) Developer image to be deployed
16.5	✘	✘	Patch 3 (*)	Patch 2 (*)(**)	(*)Developer Mode should be enabled. For details, see the Apple Developer documentation. (**) Developer image to be deployed
16.4	✘	✘	Patch 3 (*)	Patch 2 (*)(**)	(*)Developer Mode should be enabled. For details, see the Apple Developer documentation. (**) Developer image to be deployed
16.3.1	✘	Patch 3 (*)(**)	Patch 2 (*)(**)	Patch 2 (*)	(*)Developer Mode should be enabled. For details, see the Apple Developer documentation. (**) Developer image to be deployed
16.3	✘	Patch 3 (*)(**)	Patch 2 (*)(**)	Patch 1 (*)(**)	(*)Developer Mode should be enabled. For details, see the Apple Developer documentation. (**) Developer image to be deployed
16.2	✘	Patch 3 (*)(**)	Patch 2 (*)(**)	Patch 1 (*)(**)	(*)Developer Mode should be enabled. For details, see the Apple Developer documentation. (**) Developer image to be deployed
16.1.2	✘	Patch 3 (*)(**)	Patch 2 (*)(**)	Patch 1 (*)(**)	(*)Developer Mode should be enabled. For details, see the Apple Developer documentation. (**) Developer image to be deployed
16.1.1	✘	Patch 3 (*)(**)	Patch 2 (*)	Patch 1 (*)	(*)Developer Mode should be enabled. For details, see the Apple Developer documentation. (**) Developer image to be deployed
16.1	✘	Patch 3 (*)	Patch 2 (*)	Patch 1 (*)	(*)Developer Mode should be enabled. For details, see the Apple Developer documentation.
16.0.3	Patch 4(*)	Patch 3 (*)	Patch 2 (*)	Yes(*)	(*)Developer Mode should be enabled. For details, see the Apple Developer documentation.
16.0.2	Patch 4(*)	Patch 3 (*)	Patch 2 (*)	Yes(*)	(*)Developer Mode should be enabled. For details, see the Apple Developer documentation.
16.0	Patch 4(*)	Patch 3 (*)	Patch 2 (*)	Yes(*)	(*)Developer Mode should be enabled. For details, see the Apple Developer documentation.
15.7.8	✘	Patch 3 (*)	Patch2 (*)	Patch 3	(*) Developer image to be deployed
15.7.2	✘	Patch 3 (*)	Patch2 (*)	Patch 1	(*) Developer image to be deployed
15.7.1	✘	Patch 3 (*)	Patch2 (*)	Patch 1	(*) Developer image to be deployed
15.7	Patch 4 (*)(**)	Patch 3 (*)	Patch2 (*)	Yes (*)	(*) Developer image to be deployed (**)Small offset for spy & highlight in Safari on iPad.
15.6.1	Patch 3 (*)(**)	Patch 3 (*)	Patch1 (*)	✔	(*) Developer image to be deployed (**)Small offset for spy & highlight in Safari on iPad.
15.6	Patch 3 (*)(**)	Patch 3 (*)	Patch1 (*)	✔	(*) Developer image to be deployed (**)Small offset for spy & highlight in Safari on iPad.
15.5	Patch 3 (*)(**)	Patch 2 (*)	Yes (*)	✔	(*) Developer image to be deployed (**)Small offset for spy & highlight in Safari on iPad.
15.4.1	Patch 3 (*)(**)	Patch 1 (*)(**)	✔	✔	(*) Developer image to be deployed (**)Small offset for spy & highlight in Safari on iPad.
15.4	Patch 3 (*)(**)	Patch 1 (*)(**)	✔	✔	(*) Developer image to be deployed (**)Small offset for spy & highlight in Safari on iPad.
15.3	Patch 3 (*)	Yes (*)	✔	✔	(*) Developer image to be deployed
15.2.1	Patch 2 (*)	Yes (*)	✔	✔	(*) Developer image to be deployed
15.2	Patch 1 (*)	✔	✔	✔	(*) Developer image to be deployed
15.1.1	Patch 1 (*)	✔	✔	✔	(*) Developer image to be deployed
15.1	Patch 1 (*)	✔	✔	✔	(*) Developer image to be deployed
15.0.2	Patch 1	✔	✔	✔
15.0.1	Patch 1	✔	✔	✔
15.0	✔	✔	✔	✔
14.8	✔	✔	✔	✔
14.7.1	✔	✔	✔	✔
14.7	✔	✔	✔	✔
14.6	✔	✔	✔	✔
14.5.1	✔	✔	✔	✔	(*) Developer image to be deployed
14.5	✔	✔	✔	✔	Xcode 12.5 or later is required for iOS Packager from iOS 14.5+. (*) Developer image to be deployed
14.4.2	✔	✔	✔	✔	(*) Developer image to be deployed
14.4.1	✔	✔	✔	✔	(*) Developer image to be deployed
14.4	✔	✔	✔	✔	UIWebView is not supported on iOS 14.4+. It was deprecated by Apple. (*) Developer image to be deployed
14.3	✔	✔	✔	✔
14.2	✔	✔	✔	✔
14.1	✔	✔	✔	✔
14.0.1	✔	✔	✔	✔
14.0	✔	✔	✔	✔
13.7	✔	✔	✔	✔
13.6	✔	✔	✔	✔
13.5.1	✔	✔	✔	✔
13.5	✔	✔	✔	✔
13.4.1	✔	✔	✔	✔
13.4	✔	✔	✔	✔
13.3.1	✔	✔	✔	✔
13.3	✔	✔	✔	✔
13.2.3	✔	✔	✔	✔
13.2.2	✔	✔	✔	✔
13.2	✔	✔	✔	✔
13.1.2	✔	✔	✔	✔
13.1.1	✔	✔	✔	✔
13.1	✔	✔	✔	✔
13.0	✔	✔	✔	✔
12.5.4	✔	✔	✔	✔
12.5.3	✔	✔	✔	✔
12.5.2	✔	✔	✔	✔	(*) Developer image to be deployed
12.5.1	✔	✔	✔	✔	(*) Developer image to be deployed
12.5	✔	✔	✔	✔	(*) Developer image to be deployed
12.4.9	✔	✔	✔	✔
12.4.3	✔	✔	✔	✔
12.4.1	✔	✔	✔	✔
12.4	✔	✔	✔	✔
12.3.2	✔	✔	✔	✔
12.3.1	✔	✔	✔	✔
12.3	✔	✔	✔	✔
12.2.1	✔	✔	✔	✔
12.2	✔	✔	✔	✔
12.1.4	✔	✔	✔	✔
12.1.3	✔	✔	✔	✔
12.1.2	✔	✔	✔	✔
12.1.1	✔	✔	✔	✔
12.1	✔	✔	✔	✔
12.0	✔	✔	✔	✔
11.4	✔	✔	✔	✔
11.3	✔	✔	✔	✔
11.2	✔	✔	✔	✔
11.1	✔	✔	✔	✔
11.0	✔	✔	✔	✔
10.3	✔	✔	✔	✘
10.2	✔	✔	✔	✘
10.1	✔	✔	✔	✘
10.0	✔	✔	✔	✘
9.3	✔	✔	✔	✘
9.2	✔	✔	✔	✘
9.1	✔	✔	✔	✘
9.0	✔	✔	✔	✘

↑Back to top

Android Chrome support matrix

The table below shows the Android Chrome versions supported by each UFT Mobile version:

Chrome version	2021	2021 R1	2021 R2	2022	Remarks
104	✘	✘	✘	✔
103	✘	✘	✘	✔
102	✘	Patch 2	Patch 1	✔
101	✘	Patch 2	Patch 1	✔
100	✘	Patch 2	Patch 1	✔
99	✘	Patch 2	✔	✔
98	✘	Patch 2	✔	✔
97	Patch 2	Patch 1	✔	✔
96	Patch 2	✔	✔	✔
95	Patch 1	✔	✔	✔
94	Patch 1	✔	✔	✔
93	Patch 1	✔	✔	✔
92	Patch 1	✔	✔	✔
91	✔	✔	✔	✔
90	✔	✔	✔	✔
89	✔	✔	✔	✔
88	✔	✔	✔	✔
87	✔	✔	✔	✔
86	✔	✔	✔	✔
85	✔	✔	✔	✔
84	✔	✔	✔	✔
83	✔	✔	✔	✔
81	✔	✔	✔	✔
80	✔	✔	✔	✔
79	✔	✔	✔	✔
78	✔	✔	✔	✔
77	✔	✔	✔	✔
76	✔	✔	✔	✔
75	✔	✔	✔	✔
74	✔	✔	✔	✔
73	✔	✔	✔	✔
72	✔	✔	✔	✔
71	✔	✔	✔	✔
70	✔	✔	✔	✔
69	✔	✔	✔	✔
68	✔	✔	✔	✔
67	✔	✔	✔	✔
66	✔	✔	✔	✔
65	✔	✔	✔	✔
64	✔	✔	✔	✔
63	✔	✔	✔	✔
62	✔	✔	✔	✔
61	✔	✔	✔	✔
60	✔	✔	✔	✔
59	✔	✔	✔	✔
58	✔	✔	✔	✔
57	✔	✔	✔	✔
56	✔	✔	✔	✔
55	✔	✔	✔	✔
54	✔	✔	✔	✔
53	✔	✔	✔	✔
52	✔	✔	✔	✔
51	✔	✔	✔	✔
50	✔	✔	✔	✔
49	✔	✔	✔	✔
48	✔	✔	✔	✔
47	✔	✔	✔	✔
46	✔	✔	✔	✔
45	✔	✔	✔	✔
44	✔	✔	✔	✔
43	✔	✔	✔	✔

↑Back to top

Supported devices

UFT Mobile supports any device that meets the minimum required OS.
In addition, the most popular devices have been tested and verified with UFT Mobile as follows:

Model	Manufacturer	OS	Type
iPhone5	Apple	iOS	Phone
iPhone5c	Apple	iOS	Phone
iPhone5s	Apple	iOS	Phone
iPhone5se	Apple	iOS	Phone
iPhone6	Apple	iOS	Phone
iPhone6 Plus	Apple	iOS	Phone
iPhone6s	Apple	iOS	Phone
iPhone6s Plus	Apple	iOS	Phone
iPhone7	Apple	iOS	Phone
iPhone7 Plus	Apple	iOS	Phone
iPhone8	Apple	iOS	Phone
iPhone8 Plus	Apple	iOS	Phone
iPhone X	Apple	iOS	Phone
iPhone XS	Apple	iOS	Phone
iPhone XS Max	Apple	iOS	Phone
iPhone XR	Apple	iOS	Phone
iPhone 11	Apple	iOS	Phone
iPhone 11 Pro	Apple	iOS	Phone
iPhone 11 Pro Max	Apple	iOS	Phone
iPhone 12	Apple	iOS	Phone
iPhone 12 Pro	Apple	iOS	Phone
iPhone 12 mini	Apple	iOS	Phone
iPhone 13 Pro Max	Apple	iOS	Phone
iPhone 13	Apple	iOS	Phone
iPhone 13 Pro	Apple	iOS	Phone
iPhone 13 mini	Apple	iOS	Phone
iPhone SE2	Apple	iOS	Phone
iPad Air	Apple	iOS	Tablet
iPad Air 2	Apple	iOS	Tablet
iPad Air 4th Gen	Apple	iOS	Tablet
iPad Air 5th Gen	Apple	iOS	Tablet
iPad mini2 Retina	Apple	iOS	Tablet
iPad mini3	Apple	iOS	Tablet
iPad mini4	Apple	iOS	Tablet
iPad mini5	Apple	iOS	Tablet
iPad mini2021	Apple	iOS	Tablet
iPad 3	Apple	iOS	Tablet
iPad 4	Apple	iOS	Tablet
iPad 2017	Apple	iOS	Tablet
iPad 2018	Apple	iOS	Tablet
iPad 2021	Apple	iOS	Tablet
iPad 2021 Mini	Apple	iOS	Tablet
iPad Pro 9.7 inch	Apple	iOS	Tablet
iPad Pro 10.5 inch	Apple	iOS	Tablet
iPad Pro 12.9 inch	Apple	iOS	Tablet
FireHD 8	Amazon	Android	Tablet
Nexus 7	Asus	Android	Phone
Arrows U	Fujitsu	Android	Phone
Nexus 6	Google	Android	Phone
Nexus 5X	Google	Android	Phone
Pixel	Google	Android	Phone
Pixel 2	Google	Android	Phone
Pixel 3	Google	Android	Phone
Pixel 4 XL	Google	Android	Phone
Pixel XL	Google	Android	Phone
Pixel XL 2	Google	Android	Phone
Pixel XL 3	Google	Android	Tablet
Android One X2/U11 life	HTC	Android	Phone
P8	Huawei	Android	Phone
P9	Huawei	Android	Phone
P10	Huawei	Android	Phone
P20	Huawei	Android	Phone
Huawei P20 Pro	Huawei	Android	Phone
Mate 30	Huawei	Android	Phone
HUAWEI ALE-UL00	Huawei	Android	Phone
HUAWEI MT7-CL00	Huawei	Android	Phone
HUAWEI Nova 3	Huawei	Android	Phone
Huawei Nova 3e	Huawei	Android	Phone
Nexus 6P	Huawei	Android	Phone
HUAWEI Y7 2nd	Huawei	Android	Phone
Lenovo TAB 2	Lenovo	Android	Tablet
G3	LG	Android	Phone
Nexus 5X	LG	Android	Phone
G8 ThinQ	LG	Android	Phone
G8 Play	Motorola	Android	Phone
Moto Z Play	Motorola Mobility	Android	Phone
Moto G4	Motorola Mobility	Android	Phone
Moto G7	Motorola Mobility	Android	Phone
Nokia 7 Plus	Nokia	Android	Phone
Nokia N1	Nokia	Android	Phone
OnePlus X	OnePlus	Android	Phone
OnePlus 3T	OnePlus	Android	Phone
OnePlus 5T	OnePlus	Android	Phone
OnePlus 6	OnePlus	Android	Phone
Oppo Reno3	Oppo	Android	Phone
Oppo R9s	Oppo	Android	Phone
Oppo R15 Pro	Oppo	Android	Phone
Toughpad FZ-N1	Panasonic	Android	Phone
Qiku 8681-A01	Qiku	Android	Phone
Galaxy Note 4	Samsung	Android	Phone
Galaxy Note 8	Samsung	Android	Phone
Galaxy Note 9	Samsung	Android	Phone
Galaxy Note 10	Samsung	Android	Phone
Galaxy Note 20	Samsung	Android	Phone
Galaxy S4	Samsung	Android	Phone
Galaxy S6	Samsung	Android	Phone
Galaxy S10	Samsung	Android	Phone
Galaxy S8 Plus	Samsung	Android	Phone
Galaxy S20	Samsung	Android	Phone
Galaxy S21	Samsung	Android	Phone
Galaxy S21 Plus	Samsung	Android	Phone
Galaxy Tab 4	Samsung	Android	Tablet
Galaxy Tab S3	Samsung	Android	Tablet
Galaxy A12	Samsung	Android	Phone
Galaxy A51	Samsung	Android	Phone
Galaxy A52	Samsung	Android	Phone
Galaxy A72 2nd	Samsung	Android	Phone
Galaxy A21S	Samsung	Android	Phone
Galaxy M31	Samsung	Android	Phone
Galaxy J3 2nd	Samsung	Android	Phone
Aquos Sense4	Sharp	Android	Phone
Xperia XZs (G8232)	Sony	Android	Phone
SONY Xperia 10 II	Sony	Android	Phone
Sony Xperia ZX3	Sony	Android	Phone
Vivo X6S	Vivo	Android	Phone
Vivo X21	Vivo	Android	Phone
Mi5	Xiaomi	Android	Phone
Mi Max 3	Xiaomi	Android	Phone
Mi 6	Xiaomi	Android	Phone
Mi 8 UD	Xiaomi	Android	Phone
MI 10	Xiaomi	Android	Phone
MI 11 Lite	Xiaomi	Android	Phone
Redmi Note9	Xiaomi	Android	Phone
Redmi Note8 Pro	Xiaomi	Android	Phone
Redmi 6	Xiaomi	Android	Phone
MI Pad	Xiaomi	Android	Phone
ZTE Axon 10 Pro 5G	ZTE	Android	Phone

↑Back to top

Micro Focus products

This topic includes the list of Micro Focus products supported with UFT Mobile:

UFT One

Version	2021	2021 R1	2021 R2	2022	Remarks
UFT One 2022	✘	✘	✘	✔
UFT One 2021 R1	✘	✔	✔	✔
UFT One 2021	✔	✔	✔	✔
UFT One 15.0.2	✔	✔	✘	✘
UFT One 15.0.1	✔	✔	✘	✘
UFT One 15.0	✔	✔	✘	✘
UFT One 14.53	✔	✔	✘	✘
UFT One 14.52	✔	✔	✘	✘
UFT One 14.51	✔	✔	✘	✘
UFT One 14.50	✔	✔	✘	✘
UFT One 14.03	✘	✘	✘	✘
UFT One 14.02	✘	✘	✘	✘
UFT One 14.01	✘	✘	✘	✘
UFT One 14.0	✘	✘	✘	✘
UFT One 12.54	✘	✘	✘	✘

UFT Developer

Version	2021	2021 R1	2021 R2	2022	Remarks
UFT Developer 2022	✘	✘	✘	✔
UFT Developer 2021 R1	✘	✔	✔	✔
UFT Developer 2021	✔	✔	✔	✔
UFT Developer 15.0.2	✔	✔	✘	✘
UFT Developer 15.0.1	✔	✔	✘	✘
UFT Developer 15.0	✔	✔	✘	✘
UFT Developer 14.53	✔	✔	✘	✘
UFT Developer 14.52	✔	✔	✘	✘
UFT Developer 14.51	✔	✔	✘	✘
UFT Developer 14.50	✔	✔	✘	✘
UFT Developer 14.03	✘	✘	✘	✘
UFT Developer 14.02	✘	✘	✘	✘
UFT Developer 14.01	✘	✘	✘	✘

BPT

Version	2021	2021 R1	2021 R2	2022	Remarks
BPT 16.0.1	✘	✔	✔	✔
BPT 16.0	✔	✔	✔	✔
BPT 15.5.1	✔	✔	✔	✔
BPT 15.5	✔	✔	✔	✔
BPT 15.0.1	✔	✔	✘	✘
BPT 15.0	✔	✔	✘	✘
BPT 14.01 SaaS	✔	✔	✘	✘
BPT 12.60	✔	✔	✘	✘
BPT 12.55	✔	✔	✘	✘
BPT 12.53	✔	✔	✘	✘
BPT 12.21	✔	✔	✘	✘

LoadRunner Professional / TruClient

Version	2021	2021 R1	2021 R2	2022	Remarks
LRP/TC 2022 R1	✘	✘	✔	✔
LRP/TC 2022	✘	✔	✔	✘
LRP/TC 2021 R2	✔	✔	✔	✘
LRP/TC 2021 R1	✘	✘	✘	✘
LRP/TC 2020 SP3	✘	✘	✘	✘
LRP/TC 2020 SP2	✘	✘	✘	✘
LRP/TC 2020 SP1	✘	✘	✘	✘
LRP/TC 2020	✘	✘	✘	✘
LRP/TC 12.63	✘	✘	✘	✘
LRP/TC 12.62	✘	✘	✘	✘
LRP/TC 12.61	✘	✘	✘	✘
LRP/TC 12.60	✘	✘	✘	✘
LRP/TC 12.57	✘	✘	✘	✘
LRP/TC 12.56	✘	✘	✘	✘

LoadRunner Enterprise

Version	2021	2021 R1	2021 R2	2022	Remarks
LRE 2022 R1	✘	✘	✔	✔
LRE 2022	✘	✔	✔	✘
LRE 2021 R2	✔	✔	✔	✘
LRE 2021 R1	✘	✘	✘	✘
LRE 2020 SP3	✘	✘	✘	✘
LRE 2020 SP2	✘	✘	✘	✘
LRE 2020 SP1	✘	✘	✘	✘
LRE 2020	✘	✘	✘	✘
LRE 12.62	✘	✘	✘	✘
LRE 12.61	✘	✘	✘	✘
LRE 12.60	✘	✘	✘	✘
LRE 12.57	✘	✘	✘	✘
LRE 12.56	✘	✘	✘	✘

ALM

Version	2021	2021 R1	2021 R2	2022	Remarks
ALM 16.0.1	✔	✔	✔	✔
ALM 16.0	✔	✔	✔	✔
ALM 15.5.1	✔	✔	✔	✔
ALM 15.5	✔	✔	✔	✔
ALM 15.0.1	✔	✔	✘	✘
ALM 15.0	✔	✔	✘	✘
ALM 12.60	✔	✔	✘	✘
ALM 12.55	✔	✔	✘	✘
ALM 12.53	✔	✔	✘	✘
ALM 12.21	✘	✘	✘	✘

Sprinter

Version	2021	2021 R1	2021 R2	2022	Remarks
Sprinter 2022	✘	✘	✘	✔
Sprinter 2021 R1	✘	✘	✔	✘
Sprinter 2021	✘	✔	✘	✘
Sprinter 15.0.2	✔	✘	✘	✘
Sprinter 15.0.1	✔	✘	✘	✘
Sprinter 15.0	✘	✘	✘	✘
Sprinter 14.53	✔	✘	✘	✘
Sprinter 14.52	✔	✘	✘	✘
Sprinter 14.51	✔	✘	✘	✘
Sprinter 14.50	✔	✘	✘	✘
Sprinter 14.03	✘	✘	✘	✘
Sprinter 14.02	✘	✘	✘	✘
Sprinter 14.01	✘	✘	✘	✘

NV

Version	2021	2021 R1	2021 R2	2022	Remarks
NV 9.14.0.1607	✔	✔	✔	✔

Silk

Version	2021	2021 R1	2021 R2	2022	Remarks
Silk 21.0.1	✔	✔	✔	✔
Silk 21.0	✘	✘	✘	✘
Silk 20.50	✘	✘	✘	✘
Silk 19.50	✘	✘	✘	✘

AutoPass License Server

Version	2021	2021 R1	2021 R2	2022	Remarks
APLS 2022.05	✘	✘	✘	✔
APLS 12.1.3	✘	✔	✔	✔
APLS 11.9.0	✔	✔	✔	✔
APLS 11.6.1	✘	✘	✘	✘
APLS 11.5.0	✘	✘	✘	✘

↑Back to top

Integrations

This topic includes list of technical integrations when working with UFT Mobile:

Framework

Integration	Version	Android	iOS	2021	2021 R1	2021 R2	2022	Remarks
Flutter	2.2.0	✔	✔	✔	✔	✔	✔
Flutter	1.22.5	✔	✔	✔	✔	✔	✔

Camera

Integration	Version	Android	iOS	2021	2021 R1	2021 R2	2022	Remarks
AVFoundation	Not applicable	✘	✔	✔	✔	✔	✔	Part of iOS system
Vision.framework	Not applicable	✘	✔	✔	✔	✔	✔	Part of iOS system
Android X	Not applicable	✔	✘	✔	✔	✔	✔	Part of Android system.
Camera 1	Not applicable	✔	✘	✔	✔	✔	✔	Part of Android system.
Camera 2	Not applicable	✔	✘	✘	✘	✘	✔	Part of Android system.
Camera NDK	Not applicable	✔	✘	✘	✘	✘	✔	Part of Android system.

QR/Bar code

Integration	Version	Android	iOS	2021	2021 R1	2021 R2	2022	Remarks
ZXing	3.4.0	✔	✘	✔	✔	✔	✔	See https://github.com/zxing/zxing
Scandit Barcode Scanner SDK	1.38.0	✔	✘	✔	✔	✔	✔
Google Mobile Vision	Not applicable	✔	✘	✔	✔	✔	✔	Part of Android system. Deprecated since December 2020.
MLKit	Not applicable	✔	✘	✔	✔	✔	✔	Part of Android system.
AVFoundation	Not applicable	✘	✔	✔	✔	✔	✔	Part of iOS system
Vision.framework	Not applicable	✘	✔	✔	✔	✔	✔	Part of iOS system

Testing

Integration	Version	Android	iOS	2021	2021 R1	2021 R2	2022	Remarks
Appium	2.0.0-Beta40	✔	✔	✘	✘	✘	✔
Appium	2.0.0-Beta24	✔	✔	✘	✘	✔	✘
Appium	1.22.2	✔	✔	Patch 3	Patch 1	✔	✔
Appium	1.22	✔	✔	Patch 1	✔	✘	✘
Appium	1.21	✔	✔	✔	✘	✘	✘
Appium	1.20.1	✔	✔	✘	✘	✘	✘
Appium	1.19	✔	✔	✘	✘	✘	✘
Appium	1.18.3	✔	✔	✘	✘	✘	✘
Appium	1.17	✔	✔	✘	✘	✘	✘
Appium	1.16	✔	✔	✘	✘	✘	✘
Appium	1.14.2	✔	✔	✘	✘	✘	✘
Appium	1.13	✔	✔	✘	✘	✘	✘

↑Back to top

Additional information

This topic includes additional information when working with UFT Mobile:

Topic	Details
Supported browsers	The following browsers are supported on clients connecting to UFT Mobile's Lab console: Chrome Firefox Microsoft Edge Safari
Screen resolutions	UFT Mobile supports the following screen resolutions: Windows: 1920 x 1200 1920 x 1080 1600 x 1200 1366 x 728 MacOS: 1440 x 900 2880 x 1800 2560 x 1600
Language support	Non-English operating systems are supported, provided that the date settings are configured to the Gregorian calendar. Non-English apps are supported by UFT Mobile. Only English language physical keyboards are supported. UFT Mobile's user interface supports 8 languages (L10N) - English, Chinese, French, German, Italian, Japanese, Russian, and Spanish. When accessing the lab console without a testing tool, the language used in the user interface is determined by the display language set in the web browser. When connecting to UFT Mobile through a testing tool, the displayed language is determined by the language used for the testing tool. Device OS is supported for 8 languages (L10N) - English, Chinese, French, German, Italian, Japanese, Russian, and Spanish. Translated help: When using the Japanese version of the UFT Mobile Help Center, the search functionality does not support Japanese characters. Workaround: Enter search strings in English. Results are shown in English, but the links open the relevant Japanese help pages.

↑Back to top

Limitations

This topic includes known issues and limitations when working with UFT Mobile:

Installation and upgrade

• A fully qualified domain name (FQDN) that starts with a number is not supported.

General

• 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.
• In App interactions, when installing a different upload of an app with the same version and build number, comments are not displayed correctly on refresh.

Record and replay

• If your replay includes the installation of an app, the installation may fail if a system app pops up before or during replay.
• Recording of the Left and Right arrow keys within apps is not supported. The recorded Up and Down arrow keys are translated into a scroll during replay. In addition, when working with the MC Browser, none of the arrows are recorded.
• Record and replay are only supported in the active browser tab. If you click back to a previous tab and perform actions, they will not be detected for record, replay, spy, or highlighting.
• 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.
  Workaround:Stop the recording, restart the app, but do not reinstall. Begin recording again.
• When recording a packaged hybrid app that is not designated as the Startup app, make sure that the hybrid app is included as one of the extra apps. This same guideline applies to the MC Browser.
• When recording a complex web page through a non-packaged hybrid app or native browser, the first step may be not be recorded.
  Workaround: Wait several seconds and repeat the first step.
• Using packaged and non-packaged versions of the same app in the same test on a single device, is not supported.
  Workaround: Use different devices.
• Record and replay is not supported for Cocos2d-x frameworks apps.
• The Device.EnterKeys method is only supported when entering values from a physical keyboard, but not when values are entered on the soft keyboard from the device's remote access screen.
• When uploading apps specifying an icon in their xml file (instead of png): if the apps were obfuscated by DexGuard or other similar tools, the icon may not appear correctly in UFT Mobile .
• The Kill method is only supported for apps that exist on the UFT Mobile server.
• For the remote display to have the same orientation as the device, the initial orientation of the device must be set to portrait when starting a recording session.
• When working with fingerprint simulation, the Fingerprint Authentication dialog box may not trigger on certain Samsung Galaxy Note devices, due to the unique location of the touch sensor.
  To check if there is a touch sensor on your device, run the Android SDK's custom application call isHardwareDetected(). If a touch sensor is present, and the Fingerprint Authentication dialog box is not triggered, this indicates that the device is not supported. Instead, you will be prompted for a password.
• When using the installPackagedApp capability in Appium, the app may be launched twice when starting an Appium test. This does not interfere with the running of the test.

Record and Replay - Android specific

• For Android 7 and above, if secure layout is not supported, a white screen with message will be shown. For details, see WindowManager.LayoutParams.html. To use such apps with UFT Mobile you need to remove the flag. For details on how to remove the flag, see the online help.
• Photo and video simulation require that the application under test be able to access external storage. In certain devices, you need to manually enable this capability. To enable it, select the app in the Settings section, and under Permissions, select Enable storage.
• Certain Samsung devices, such as the Galaxy and Note 4/5, may occasionally disconnect from the UFT Mobile server due to the SPCM service running on the devices.
• Record & replay of the Android app chooser system widget is not supported. An example is the selection of an email app when prompted by the device, if a default email app was not set.
• SMS simulations are not supported for Android 6 and above.
• Working with the Multi-Window feature (also know as split-view) is not supported for Android.
• Spying on the suggestion list of the SearchView widget is not supported.
• The NumberPicker widget is supported only in native packaged apps.
• Some Android devices (such as certain Google Pixel or OnePlus devices) may not react to input from the PC keyboard.
  Workaround: Restart the mobile device.
• Android 10: Due to changes to the permissions model, when running apps that target Android 5.1 (API level 22) or lower on Android 10 for the first time, a permissions screen is displayed. This screen prevents UFT Mobile from successfully launching the app.
• Input method editor (IME) actions:
  • UFT: To support IME actions on a text field in the device browser, the text field must still be in focus after entering several words or strings.
  • Appium: Running scripts containing IME actions on the device browser results in an error: "org.openqa.selenium.WebDriverException: An unknown server-side error occurred while processing the command. Original error: unknown error: performEditorAction is not defined."

Record and Replay - iOS specific

• Safari navigation is not supported on iPad OS 15 for hybrid non-packaged apps .
• iOS 10.3 and above: For applications bigger than 50MB, there is a need to change the following configuration for a longer timeout - server\jetty\webapps\hp4m-connector\WEB-INF\classes\application.properties

  For Linux & Mac:
  

  connector.mac.ios10.timeWaitForInstall.in.millis=10000
  connector.mac.ios10.waitForInstall=true

  For Windows:
  

  connector.win.ios10.timeWaitForInstall.in.millis=5000

• Apps designed for iPhones are not supported by UFT Mobile when running in compatible mode on an iPad.
• Long browser scripts may fail to replay on the MC Browser app.
• The Pinch gesture is ignored in replay with XCTest. The test will continue with replay, but the recorded Pinch gesture will be ignored.
• iOS 13:UFT: Some sites are not supported for record and replay of hybrid non-packaged applications with the Safari web browser.
• The Send Text device interaction is only supported in iOS when using the XCUITest control. For iOS devices under 11.1, you must switch the control mode to use XCUITest by adding the device UDID to the configuration file, xcuitest.json, in the conf folder:
  

  {
       "devices": [ "YOUR_UDID" ]
  }

Packaged apps

• The MobileRadioGroup and MobileTabStrip objects support the selection of a radio button or tab only by index (not text).
• MobileSlider tap or swipes are rendered as SetProgress actions with the actual slider’s value.

Non-packaged apps

• Recording is only supported through the remote display.
• Replay of hybrid apps is not supported for multiple web views in a single session.
• Window.open is not supported for hybrid non-packaged apps.

Non-packaged apps - Android specific

• Toast notifications are not supported.
• Non-packaged apps built with Crosswalk projects framework are not supported.
• SAP hybrid non-packaged apps are not supported.
• Actions on date and time pickers are recorded as Tap actions and not as Set actions.
  Workaround: Manually modify the Tap actions to Set.
• For MobileList, Childobject only retrieves the child objects that are present on the screen.
• The MobileCalendar and MobileList objects are not recorded.
• When using the MobileRadioGroup object, you can select the object by index, but not by text.
• Steps that use a MobileObject with a View class will fail.
• MobileDropdown.select is not supported. Therefore, any test object method that uses an index for an argument value, is not supported for Android.
• Highlighting an object in the application on an Android device (which is based on an index of the specified object) may produce unexpected results. The MCindex will change from device to device or if the orientation changes, so in these cases highlighting might find another similar object (other properties of the object are the same, only the MCindex differs), or might not find the object. The look up mechanism uses the index only when the view provides no additional data (accessibility, resourceId, text, or hint).
• MobileEdit.setText will be recorded as an Enterkeys action.
• For testing tools: When a dialog box pops up in WebView, the JavaScript engine will pause until the dialog box is dismissed. As a result, when using non-packaged hybrid apps or the Chrome native browser, the fireEvent method will time out.
• When replaying a slide action on a SeekBar (such as your device’s brightness control), there may be a slight discrepancy between the actual value and the value used during replay. This discrepancy only exists on certain Android devices.
• Encrypted apps with a security framework are only supported in non-packaged mode.

Non-packaged apps - iOS specific

• Device metrics are not supported.
• Scroll to label in replay is only supported when the label is visible on the screen.
• Empty strings or NULL values are not supported for findElement. Make sure to specify a value such as a number, boolean, or string.
• Record and replay may fail for pages using dynamic URLs.
  Workaround: Begin recording the page again to get the right MobileWebView.
• Event simulation is not supported.
• iOS versions 10 - 10.3.2: WebView is not identified on non packaged hybrid applications on a device running iOS 10.0-10.3.2 using the XCUITest framework.
  Workaround: Add the UDID to the xcuitest.json file with prefix "UIA_" before the UDID.
  xcuitest.json file location:  /opt/UFTMobile/server or connector/conf
  For example:
  

  {
       "devices": [ "UIA_f172874b62cc5a7970df9fd9d2e9cadefe6955f7" ]
  }

• Hybrid non-packaged apps are not supported for iOS 10.2.x and 10.0.x. Recording will only capture native mobile actions.

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

• Only Chrome and Safari are supported as native browsers.
• Before recording or running tests, or spying/ highlighting objects, close all previously opened pages and tabs.
• Recording is not supported for auto-completed URLs. For example, if you begin typing a URL and an auto-complete drop-down list opens, your selection will not be recorded. On iOS devices, nothing will be recorded. On Android devices, it will record the previous selection.
  Workaround: Manually type in the whole URL or navigate via the drop-down list to the next page you want to test.
• Recording of popup windows is not supported for native or UFTM browsers.
• Cross origin iframe sites are not supported for native browsers.
• The following test object methods are not supported:
  • Browser.CloseAllTabs
  • Browser.ClearCache
  • Browser.DeleteCookies
  • Browser.OpenNewTab
  • Browser.HandleDialog
• The GWT webtab, weblist, and webtree operations are not recorded on native browsers.

Native browsers - Android specific

• If you are using Chrome as a native browser, make sure that it is installed and set as the default browser. For devices that do not enable you to set a default browser, disable the system browser.
• For Android native browsers used with non-packaged hybrid apps: The WebSocket connection may fail, preventing the steps from being recorded by testing tools. Once you reinstate the WebSocket connection, the recorded steps, which were stored by the agent, will be added to the script.
• On the Chrome native browser, the following test object methods are only supported for replay:
  • Browser.Back
  • Browser.Forward
  • Browser.Refresh

Native browsers - iOS specific

• For certain iOS devices running iOS 11.1 or later (XCUITest), the device may disconnect from the UFT Mobile server when recording active dialog messages with the native browser.
• Setting the URL is not recorded on Safari and the UFTM Browser app.
  Workaround: Update the script manually.
• iOS12.2 and later: All open tabs must be closed before recording and replaying with the Safari browser.
• Replay is not supported when a page is opened in a new tab in the Safari browser.
• For iOS devices running in XCUITest mode, you may experience object recognition issues with hybrid apps and the native browser. To avoid these issues, make sure to follow Apple's UI design rules.
• The URL of a navigation step is not recorded on iOS 12.5.x devices

↑Back to top