This may happen due to a known ChromeDriver issue that occurs on Android 13 when the Chrome version is earlier than 110. The issue can be resolved by upgrading to Chrome version 110 or later.

Making and receiving phone calls during tests is currently not supported on Android devices and may cause the device to disconnect.

The Network Security Services (NSS) libraries, which are needed to run ChromeDriver, are not included by default in Linux OS 8.x versions. As a result, ChromeDriver is unable to start, and the session fails. Install the nss package using the following commands: 

sudo yum makecache –refresh
sudo yum -y install nss

If you do not have internet access on your Linux machine, an offline RPM  should be downloaded and installed separately.

This issue can be resolved by enabling ART support.

1. Open the ApkInufser properties file in the following location:
   <Path to Digital Lab Server installation >/server/AndroidTools/ApkInfuser/ApkInfuser.properties

2. Change the line [globle.enableART=false] to [globle.enableART=true].

3. Save the file

4. Upload the app again.

5. Restart the connector.

1. Locate the connector.properties file. Change the value of the following line to false:
   android.javavnc.useMinicap=false
2. Restart the connector.

Note that you str not able to use apps with secure layout.

In the device’s keyboard settings, select QWERTY layout.

If the English language letters are not converted to Japanese, use one of the following workarounds:

• For typing directly from the computer keyboard:

  1. Install Google Japanese Input from Google Play on the device, or upload the apk to Digital Lab, and install it on the device from Digital Lab.

  2. On the device select the Google Japanese Input keyboard. In the Google Japanese Input settings , set the keyboard layout to QWERTY.

• Type using the Send Text option in the device control panel.

• Type by clicking on the device’s on-screen keyboard.

Some device managers, such as the HTC Sync Manager and Samsung Kies, launch automatically when connecting a device, and start their ADB server. When the ADB server is launched, it detects that there is already an ADB server running (Digital Lab’s) and stops it. This causes all the Android devices to disconnect.
Workaround: Uninstall the device manager, or make sure that it is not launched automatically when using Android devices with Digital Lab.

For Samsung devices running an Android version below 7.0, perform the following steps to allow access via the remote device view.

1. Locate the connector.properties file.

   Server and Connector: ${Digital Lab_Install_Path}/server/conf

   Remote Connector: ${Digital Lab_Install_Path}/connector/conf

2. Open the file and add the device models, separated by commas, to the android.javavnc.model.enable property. For example:

   android.javavnc.model.enable=LG-H990,Nexus 5X,Nexus 4,LG-H961N,Nexus 9,LG-H870,ONEPLUS A5000,LG-D855,ONEPLUS A3000,SM-N950F,SM-N960F,SM-G960F,SM-G965F

3. Restart the Server/Connector for the changes to take effect.

In certain cases, you may you receive the following error when trying to confirm "Allow USB debugging". The error message is "Because an app is obscuring a permission request, Settings can't verify your response."

As a workaround, perform the following:

1. Disconnect the USB cable from the device.
2. Restart the device in SAFE mode. To do this, hold down the low volume button while restarting the device or check your manufacturer's guidelines. You should see SAFE MODE in the bottom left corner of the screen.
3. Connect the USB cable to the device.
4. In the Developer options, enable USB debugging.
5. Restart the device in normal mode.

For apps that were obfuscated by Proguard and automatically packaged by Digital Lab, record and replay may not function properly.
Workaround: Package the app manually using the APKInfuser tool.

1. Go to the AppDelivery Marketplace. Select the current version of Digital Lab and download the APKInfuser tool.
2. Unzip the archive file and locate the ApkInfuser.bat file in the ApkInfuser folder.
3. Locate the mapping.txt file generated by Proguard when you built the application in Android studio.

4. Run APKInfuser on your app using the native, hybrid, and mappingFile command line options.

   ApkInfuser.bat -native -hybrid -mappingFile <FULL_PATH_TO_MAPPING_FILE> <FULL_PATH_TO_APK>

   The result is a debug-signed APK file with web instrumentation code.

   For Example:

   ApkInfuser.bat –native –hybrid -mappingFile c:\mapping.txt my-android-app.apk

   The above command generates the file: my-android-app.apk.signed.debug.apk in the same folder as the original APK.

   Tip: For help about the APKInfuser tool, see the Usage.txt file in the ApkInfuser folder.

5. Upload the generated *.signed.debug.apk file to Digital Lab.

Certain Samsung devices running Android 7.0, use a battery optimization tool that causes this issue. If you encounter disconnection issues, perform the following:

1. Open Settings > Apps.
2. Click the More button (three vertical dots) and select Special Access.
3. In the Special Access area, choose Optimize battery usage.
4. In the Optimize battery usage area, choose All apps.
5. Scroll to the Digital Lab Agent app and switch it to Off.

Certain Android devices, primarily those manufactured by Chinese vendors, use a security tool that affects the memory and battery usage. If you encounter disconnection issues, perform the following:

1. Enable Autostart for the Digital Lab Agent: Open the device’s Security app from the Home page, and click Permissions. Select Autostart, find the Digital Lab Agent app, and enable it.
2. Turn off the battery saver: Open the device’s Security app from the Home page, and click Battery. Set Battery saver to Off. Alternatively, to work with the battery saver on, select App battery saver and find the Digital Lab Agent app. Select No Restrictions.

Certain LG devices disconnect after changing the orientation from the control panel in the remote view. The log file contains an exception message. If this occurs, perform the following:

1. Check the device card of the disconnected device on the DEVICES tab and determine its model number. This is usually the manufacturer name "LG" followed by a hyphen and a short string. For example, LG-D855.

2. Open the Connector.properties file in C:\Program Files\UFT Digital Lab Server\server\conf (by default).
3. Add the model of the disconnected device to the “VNC_USE_64ARTIFACT_MODELS” row. Save and close the file.
4. Restart the connector service (Start > Digital Lab Connector > Restart Digital Lab service) , and verify that the connection is stable after you change the orientation.

If an app crashes or is terminated forcefully during a recording session, your actions are no longer be recorded even if you restart the app. You must re-record your session from the beginning.

You can work with Dexguard security by compiling your app in Dexguard. Follow these steps:

1. Upload your original, packaged or non-packaged app to Digital Lab.
2. Record a test on the original app.

3. Recompile the app in Dexguard with the following options:

   "-keepresourcexmlattributenames **/id -keepresources id/*"

4. Upload the Dexguard-wrapped version of the app to Digital Lab.
5. Replay the testing using the Dexguard-wrapped version of the app.

Cross-domain iframe calls are not supported. For example, if your test uses an iframe that points to a web page in another domain, it fails.

An Android limitation may cause a device to issue the message INSTALL_FAILED_INSUFFICIENT_STORAGE while installing certain apps. This limitation may also cause some connected devices to disappear from the Devices page, after having been connected for some time.
Workaround: Restart the device.

When working with hybrid non-packaged apps, make sure that remote content debugging is enabled. For details, see Enable remote content debugging of Android apps.

In order to work in the remote view on a device with a Good Connect client, you must set the Prevent Android Screen Capture policy to Off. The release version of 2.3.18.687.117 and above is required for the policy to take effect. For details, see the Blackberry Knowledge Base article.

To support input method editor (IME) actions on Android, the application under test must be customized by the app developer, using the android:imeOptions attribute. Failure to do so results in some IME actions, such as Previous and Done, not working as expected.

If you have no SIM card installed, when running XCUITEST, you may experience a crash from your device’s plug & play because of the No-SIM popup. To avoid this crash, you can use a dummy SIM card (recommended) or follow these guidelines for iOS 11.1 and higher:

1. In device's system settings, configure the auto-lock of the device to 30 seconds.
2. On the iOS Agent, tap two times on theDigital Lab icon.

3. Select the VNC tab.

4. Set the Avoid device lock option to 1 minute, to avoid device locking (which may occur even with the device's system auto-lock settings).
   Note: To apply this setting to all connected iOS devices, configure the setting in Administration settings > iOS options. This eliminates the need to configure the setting manually on each connected device.

   

5. It is strongly advised to also enable Application Launch Alert Dismiss . If the setting is disabled and a system alert occurs, it may block the functionality of the Avoid Device Lock feature, causing the device to lock.
   Note: To apply this setting to all connected iOS devices, configure the setting in Administration settings > iOS options. This eliminates the need to configure the setting manually on each connected device.
   

When installing an app that is already installed on the device, be sure to use the same developer certificate as the installed app. If the certificates do not match, the installation fails. For example, if the app on the device is signed with Certificate A you cannot install the same app signed with Certificate B.

The same applies if an app on the device is signed with an Enterprise certificate and you want to install the same app signed with a Developer certificate.

Workaround: If the certificates do not match, first remove the app that is already installed on the device, and then reinstall the app with the other certificate onto your device.

When code-signing an app on a Macintosh, an Apple trusted authority certificate must be installed so that Apple can be recognized as a trusted authority by the Keychain Access app. If an Apple trusted authority certificate is not installed, any certificate issued by Apple is shown as invalid. For more details on software signing certificates, see the Apple Developer documentation.

If a certificate is shown as invalid (red) in the Keychain Access app, followed by an error “This certificate was signed by an unknown authority”, you need to download and install a new certificate from the Apple Worldwide Developer Relations Certificate Authority.

Install the certificate as follows:

1. Download the certificate from the Apple Developer support site.

2. Double-click the certificate.

3. Verify that it is valid (green) and does not display the following error: “This certificate was signed by an unknown authority”.

If the device was set up to lock its screen, or sleep, after a certain interval, this can affect your replay.

To prevent all connected iOS device from locking, configure the Prevent auto lock setting in Administration settings > iOS options. This eliminates the need to configure the setting manually on each connected device.

Alternatively, to manually prevent a device's screen from locking up, make sure that your Display Settings for Sleep are set to "Never".

If your device continues to sleep and lock its screen, you can apply a workaround to send a pseudo-action to the device to prevent it from sleeping, and to keep the device unlocked. The pseudo-action used by this workaround, is the Volume up and Volume down controls. It does not affect the steps in your test, but you can see the control briefly at certain intervals, on the device screen.

To set up this action:

1. On your device, open the Agent application.

2. On the Digital Lab icon, tap the screen two times. The advanced developer bar becomes visible at the bottom of the screen.

3. Click the bottom right button, VNC, to display the VNC server details settings.
4. Click in the right value column for the Avoid Device Lock feature.
5. Select an interval in which to send the pseudo-action to the device, from 1 to 5 minutes.

You can get crash logs for a device in a number of ways:

When you record the packaged version of an app on iOS, the recorder generates two orientation steps after the Home navigation step.

The time zone on your iOS device must match the time zone on the connector machine. If the time zones are not aligned, an empty text file is downloaded.

Certain elements, such as the soft keyboard, are visible on the physical device but not on the remote device display. This is due to Apple security enhancements. There may be cases where these "invisible" elements are placed on top of other elements and prevent users from interacting with them. For example, the soft keyboard may be placed over the Login button, thereby preventing users from clicking it.

Due to apple security enhancements, when typing a password on a device using the remote screen viewer, the virtual keyboard is not displayed and the text is not visible on secured password fields. On the physical device, both the keyboard and the visual indicators (dots) for the password show. Even though the text/keyboard is not displayed, the text is sent as expected.

The same behavior is observed when using the option Send text to device. The text is sent even though it is not displayed.

Record and replay of packaged iOS apps uses the accessibilityLabel property and value for object recognition, and not accessibilityId. If your test logic uses the accessibilityId property and value to distinguish a specific object and you plan on testing packaged apps, set up the device as follows:

1. On your device, open the Agent application.

2. On the agent logo, tap the screen two times. The advanced developer bar becomes visible at the bottom of the screen.

3. Click the VNC button on the bottom right of the screen, to display the settings.
4. Toggle use accessibilityId for packaged apps to on.

Insert a SIM card or dummy SIM card in the device.

Alternatively, manually configure the device and Agent app on the device as follows:

1. On the device, select Settings > Display & Brightness> Auto-lock and set the timing to 30 seconds.
2. Open the Agent app on the device.
3. Tap the Digital Lab icon 2 times. The developer options tab bar is displayed at the bottom.
4. Tap the VNC icon and set Avoid Device Lock to 1 minute.

Note: To apply this setting to all connected iOS devices, configure the setting in Administration settings > iOS options. This eliminates the need to configure the setting manually on each connected device.

If an app consistently crashes after a launch or Start Record, or if you cannot launch it with the Install application option (the actual option name may differ depending on the tool you are using) is selected, perform one of the following :

1. Run the tests with the uninstall or delete option.
   

   Tool	Option name
   UFT One	Select the Uninstall checkbox in the Record and Run Settings dialog box, in the Mobile tab.
   TruClient	Delete App After Execution in the TruClient General Settings dialog box, in the Digital Lab settings tab.
   Sprinter	UNINSTALL button in the APPLICATION tab of Digital Lab.

2. Install the repackaged AUT on the device, and only use the Restart option.

   Tool	Option name
   UFT One	Restart in the Record and Run Settings dialog box, in the Mobile tab.
   TruClient	Restart App in the TruClient General Settings dialog box, in the Digital Lab settings tab.
   Sprinter	RESTART button in the APPLICATION tab of Digital Lab.

If the Agent does not start up on the device, verify that the devices are recognized by the server or connector machines:

Linux

1. Navigate to:
   Devices connected to server machine
   /<path to server installation folder>/server/libimobiledevice/linux/
   or
   Devices connected to standalone connector
   /<path to connector installation folder>/connector/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 Digital Lab server or connector 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 device is recognized.

Windows

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
   Devices connected to standalone connector: <Path to your Windows Connector folder>\libimobiledevice\win
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. Download the latest version of iTunes.

When trying to launch an enterprise certified app through your test (for example UFT One), the launching may fail the first time you start the app, because Apple requires the user to manually approve the app on the device. The error message asking for approval is not visible in the testing tool's interface (e.g. UFT One). However, if you launch the app manually, it is visible.

Solution: Manually launch the app and approve its certificate. Then, launch it through your test.

When recording on XCUITest devices, URL navigation was not recorded.
Workaround: If the navigation to the URL is the first step in your test, wait at least 5 seconds to make sure the JavaScript injection is complete. Click once in the address bar to open the keyboard—do not perform a double-click or press the Clear button. Type in the complete URL using the PC keyboard (not the device's) and press Enter.

When using the date picker to select a date, make sure that you make your selection within 30 seconds. If the duration of the time selection exceeds 30 seconds, the agent times out. This issue only applies to non-packaged apps on iOS devices.

If a device doesn't work as expected, try to reset all settings. For example, if remote access doesn't work, taps don’t respond, apps don’t install, and so forth, revert to the original default settings:

For Mac Connectors connecting to iOS 11.1 devices: If your device cannot connect to Digital Lab, check the Connector log for an error when executing ./ideviceadddocument. This indicates a trust issue.

If the Agent stops working on the device, do the following:

If you're still having problems:

As a last resort:

The installation log files located in the installation/Logs folder under the Digital Lab installation. Even if an installation hangs, you can view the intermediate log, installation/Digital Lab_Server_install.log.

This error occurs due to constraints of the operating system. To resolve the error, perform these steps on all Windows based UFT Digital Lab servers and connectors being used by your tests:

1. Open the Registry Editor and add the following DWORD values under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters:
   

• MaxUserPort with decimal value of 65534
• TcpTimedWaitDelay with decimal value of 30

2. Restart the operating system.
   Alternatively, restart both ADB (Android Debug Bridge) and AMDS (Apple Mobile Device Service).
   
   To restart ADB:

   Run the following command under the Android SDK directory used by the server or connector (Path to UFT Digital Lab\server|connector\android-sdk-windows\platform-tools\):  adb.exe kill-server

   Note: Wait for 10 seconds before running any other adb commands. This is to avoid to automatically starting ADB with a different user. UFTDigital Lab will start it after a few seconds.

   To restart AMDS:

   1. Open the Run dialog (Windows + R).

   2. Enter services.msc to open the Services window.

   3. Locate Apple Mobile Device Service. Right-click on the service and select Restart from the context menu.

When the file storage and the Digital Lab server machines are not in the same domain, but are part of the same Windows workgroup, the same Windows admin username and password are required on both machines. After installation, you should run the Digital Lab server under the Windows admin user. For details, see Troubleshooting and tips .

To modify the server details, see Reconfigure the Digital Lab server .

• Navigate to C:\Program Files and delete the Digital Lab Connector folder (after you have tried to run an uninstall) if it exists.
• Delete the (hidden) Zero G Registry folder. If it is not visible, in the Windows Explorer, choose Organize > Folder and search options > View tab, and select Show hidden files, folders and drives.
• If you began the server installation and it failed, delete the Windows server installation folder, C:\Program Files\UFTDigital Lab Server, and restart the setup.
• If the installation was successful, but you cannot access the Digital Lab server, check that the port is not being blocked by a firewall or your antivirus program.
• Refer to the installation log file in the installation > Logs folder, and look for error messages.

If the Windows connector started successfully, but you don't see devices in the Digital Lab console:

• Verify that your machine can detect your device.
• Check the connector.log file located in <Windows connector folder>\connector\log folder and make sure that there are no "connection refused" messages or other errors.

• If the connector.log does not show any errors, check the service.log file on the Digital Lab server machine. The file is located here: 

  • Windows server: <Path to Digital Lab server installation folder>\server\log
  • Linux server:<Path to the Digital Lab server installation folder>/server/log

If, during installation, Windows issues the warning “Windows Firewall has blocked some features of this app”, click Allow access or contact your system administrator. When this message is issued, the current Connector installation is aborted.

If you cannot view a remote device in the Digital Lab device lab, this may be a result of the anti virus software installed on the machine. For example, McAfee Host Intrusion Prevention blocks access. Workaround: Disable the anti virus while running the test.

The Windows connector started successfully and the device is displayed in the Digital Lab device lab, but either remote access or recording are not working. Sometimes Digital Lab issues a message with the problematic IP address and port. In other instances, you may receive a "connection refused" message, indicating an IP address problem:

• Check the service.log file on the Digital Lab server machine and look for possible "connection refused" errors:

  • Windows server: <Path to Digital Lab server installation folder>\server\log
  • Linux server:<Path to the Digital Lab server installation folder>/server/log

• Check that the IP address (shown in the error message) that Digital Lab is trying to reach, is the correct one for your connector machine. To show the IP address of your machine, open a command line window and type ipconfig.

  If, for example, you were connected to a different network or IP when you installed the connector, you need to run the Modify configuration utility under Start > Digital Lab Connector and enter the new IP of the connector machine.

• Check that the port shown in the error message, is open for incoming traffic on the connector machine.

• If you indicate SSL during connector setup, proxy machines that require credentials are not supported.
• If you have a device connected when you install the connector for an SSL environment using a proxy server, the devices do not appear in Digital Lab. Workaround: Connect the devices after you install the connector software.

• While trying to connect to a secure SSL Digital Lab server: If you receive a message "Could not reach Digital Lab server", this may be due to a modified CA certificate on the server machine.
  Solution: Reconfigure or modify the connector and retrieve the new certificate.

When trying to run the installation, if the setup program issues a "connection refused" or "connection timed out" warning, it could mean that:

• The server is down. Check that you can ping the server.
• The IP address of the Digital Lab server is wrong.
• The port for the Digital Lab connector is wrong.
• The version of the connector that you are using is not compatible with the version of the Digital Lab server. Check Digital Lab on ADM Marketplace to see that you are using the most up-to-date version of the connector.

If the server details (IP address or port) have changed since you last installed the connector, modify the connector and specify the new information.

If an existing service running on your machine is claiming the port on which the connector runs, there is a conflict, and the connector does not start up.

To change the port, run the Modify configuration utility under the Start > Digital Lab Connector menu.

If you installed the Android SDK for a specific user (not the SYSTEM user), the Windows connector setup program may be unable to install the Agent, because the manually installed SDK is not accessible from the SYSTEM user.
Workaround: Reinstall the Android SDK as a SYSTEM user, and delete the ANDROID_HOME environment variable.

This may happen due to a corrupt registry file.

To resolve the issue:

1. Uninstall the existing installation.

2. Make sure that registry file /Library/Preferences/.com.zerog.registry.xml is removed. If not remove the file manually.

3. Install the Mac connector again.

The language of the user interface (UI) is determined by the language of the testing tool that is connecting to Digital Lab.

• Digital Lab's UI supports the following languages (L10N) - English, Chinese, French, German, Italian, Japanese, and Spanish.
• When accessing the lab console without a testing tool, the displayed language is determined by the browser language.
• For unsupported languages such as Korean: When you open the TruClient testing tool from a machine with the language pack, the Digital Lab interface is displayed in English.

Opening the Chrome browser in Appium Inspector using the capability browserName: chrome, causes the browser to go to the background immediately when opened. Appium Desktop remains looping, waiting for Chrome to open, resulting in an error: "call to 'getPageSource' failed... chrome not reachable."

Workaround: Add the capability appium:recreateChromeDriverSessions: false.

This error indicates a Chrome version mismatch. If the version of Chrome on your device is not compatible with the supported Digital Lab Chrome version, the following error is displayed "An unknown server-side error occurred while processing the command. Original error: unknown error: Chrome version must be >= 55.0.2883.0".

• On your device, navigate to https://www.whatismybrowser.com to check the Chrome version being used.

• To view the Chrome versions supported by Digital Lab, navigate to the ChromeDriver folder of the Digital Lab connector/ server to which the device is connected. For example: C:\Program Files\UFT Digital Lab Connector\connector\chromeDriver.