This issue can be resolved by enabling ART support.

1. Open the ApkInufser properties file in the following location:
   <Path to UFT Mobile 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 will not be 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 UFT Mobile, and install it on the device from UFT Mobile.

  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 will detect that there is already an ADB server running (UFT Mobile’s) and will stop it. This will cause 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 UFT Mobile.

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: ${UFTM_Install_Path}/server/conf

   Remote Connector: ${UFTM_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 UFT Mobile, record and replay may not function properly.
Workaround: Package the app manually using the APKInfuser tool.

1. Go to the Micro Focus AppDelivery Marketplace. Select the current version of UFT Mobile 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 UFT Mobile.

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 UFTM 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 UFTM Agent: Open the device’s Security app from the Home page, and click Permissions. Select Autostart, find the UFTMAgent 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 UFTM 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 Mobile 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 > UFT Mobile Connector > Restart UFT Mobile 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 will 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 UFT Mobile.
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 UFT Mobile.
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 will fail.

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 will result in some IME actions, such as Previous and Done, not working as expected.