Share this page

# Connect iOS mobile devices

You can connect iOS devices to the OpenText Functional Testing Lab server, or to a connector machine.

In this topic:

## Before you start

Before connecting devices, check that your devices are supported, and remove all apps that were installed using a previous version of OpenText Functional Testing Lab.

Back to top

## Considerations for iOS 17 and later

To connect devices running on iOS 17 and later, internet access is required to fetch a signature key from Apple from time to time. The server machine must have access to the following:

- http://gs.apple.com
  OpenText recommends allowing access to all *.apple domains.

If the server machine accesses the internet via a proxy server, configure the proxy server details in in the Administration settings. For details, see Proxy settings in Administration settings.

If access to the internet is not permitted on the server machine, make sure that the connector can access the Apple servers. If the connector uses a proxy server, configure the following proxy server details in the connector.properties file located in <installation_dir>/connector or server/conf/:

- APPLE_HTTP_PROXY_HOST=<proxy host name>

- APPLE_HTTP_PROXY_PORT=<proxy port number>

- APPLE_HTTP_PROXY_USERNAME= <username for connecting to the proxy server>

- APPLE_HTTP_PROXY_PASSWORD= <password for connecting to the proxy server>

See the Support matrix for supported operating systems and additional considerations that should also be taken into account.

Back to top

## Re-sign the Agent apps

The Agent apps are standard iOS applications that need to be installed on each device that you want to use with OpenText Functional Testing Lab. These provide a communication channel between the device and the lab.

The Agent apps must be re-signed with a development certificate of an Apple Developer Account, and a development provisioning profile belonging to the same account. These provide the identity of the developer, and the list of devices on which distribution of the app is allowed.

For details on how to re-sign these apps, see Re-sign the Agent apps.

Back to top

## Initial device configuration

The first time that you connect a device, perform the following steps on each device you intend to connect to the lab. These are one-time settings. After the initial connection has been set up, the device is "plug-and-play".

1. In Settings > Display & Brightness > Auto-lock set the maximum time.

2. Turn off automatic updates in Settings > General > Software Update.

3. For Safari browser support: Enable JavaScript and Web Inspector in Settings > Safari > Advanced.
4. Make sure that the Display Zoom, under the Display and Brightness settings, is set to Standard, and not Zoomed
5. Make sure that there is an active Internet connection.

6. Set your preferences (such as iCloud) to avoid unnecessary pop-ups.

7. Additional steps for specific iOS versions:

Version | Details
--- | ---
iOS 15 and later | We recommend not setting a passcode/ TouchID/ FaceID for iOS 15 and later unless it is necessary. If the passcode, TouchID or FaceID is not turned off on the device, when the WebdriverAgent-runner is launched, iOS requires the user to authenticate through the security mechanism configured. This requires manual intervention with the device.
iOS 16 and later | Developer mode must be enabled. Developer mode is enabled automatically for devices running on iOS 16 and later. Developer mode can only be enabled automatically if there is no passcode set on the device. We recommend not setting a passcode on devices used for testing. If the device has a passcode, enable the Developer mode option in Settings > Privacy & Security > Developer Mode. For more details on developer mode, see the Apple Developer documentation.

Back to top

## Connect devices

If you have not already done so, make sure that you have re-signed the Agent apps with your development certificate. For details, see Re-sign the Agent apps.

Using a USB cable, you can connect devices to the OpenText Functional Testing Lab server or to a connector machine. To connect devices directly to the server, the server must be installed with the embedded connector. For details, see Windows Installation or Linux Installation. If you are connecting devices to a connector machine, see Install the connector on a Linux machine, Install the connector on a Windows machine or Install the connector on a Mac machine.

To connect a device to the server:

1. Connect the device to the server machine using a USB cable.

Note: On some devices, when you connect the device, there may be notification, trust, or location pop-ups. Accept these pop-ups.

2. Wait until the Agent is running on the device.

If the agent does not start up on the device, verify that the devices are recognized:

Linux

To verify that devices are recognized on a Linux machine:

1. Navigate to the linux folder:
   Server machine:`<path to you server installation folder>/server/libimobiledevice/linux/` Default: `/opt/FunctionalTestingLabForMobileAndWeb/server/libimobiledevice/linux/`
2. Run `idevice_id –l`

The result of this command should be a list of devices IDs (UDID). If the command returns an empty result or ERROR message, try the following:

1. Log in as root on the OpenText Functional Testing Lab server machine.
2. Locate the process ID of “usbmuxd”"
   `ps aux | grep '[u]sbmuxd'`
3. Kill the process:
   `kill –9 <processID>`
4. Start usbmuxd again:
   `usbmuxd`
5. Run `idevice_id –l` again to see if the server recognizes the device.

Windows

To verify that devices are recognized on a Windows machine:

1. Open a command prompt window and navigate to the following folder:
   Devices connected to server machine:`<Path to your Windows server folder>server\libimobiledevice\win` or
2. Run the following command: `idevice_id –l`

The result of this command should be a list of devices IDs (UDID). If there are no devices listed when a device is connected to USB port, this may mean that:

- The USB port is not working (hardware problem)
- iTunes is not installed, or you are not using the most up-to-date version of iTunes on the Connector computer. In this case, you should download the latest version of iTunes.

## Additional considerations for iOS devices

If you have not already done so, enable UI Automation on the device in Settings > Developer > Enable UI Automation. Disconnect the device, wait 5 seconds, and then reconnect it.

Important note for Enterprise certificates

If an app signed with an Enterprise certificate is installed without using a Mobile Device Management (MDM) solution, trust for the enterprise developer must be established the first time the app is installed. To trust the profile, go to Settings > General > Device Management, select the enterprise developer profile, and trust it. These actions can be performed remotely on the device with OpenText Functional Testing Lab.
All users who install your enterprise-signed app for the first time also need an internet connection. After an enterprise developer profile has been trusted on a device, additional apps with the same profile do not need to be trusted again, provided that the devices on which they are opened are connected to the internet. If the enterprise Developer profile of the application under test is not trusted, the Agent is not be able to open the app and a 1009 Error: "Cannot communicate with AUT" results.

Back to top

## Troubleshooting iOS devices

For help with troubleshooting iOS devices see iOS devices.

Back to top

See also:

- Manage devices
- iOS options
- Workflow to connect a device
- Troubleshooting the Windows connector
- Troubleshoot

https://admhelp.microfocus.com/Functional Testing Lab 8942
Tips to improve your search results... OpenText™ Functional Testing Lab for Mobile and Web Help Center OpenText™ Functional Testing Lab Help 25.2 All View Local Help Center View Online Help Center Version: