Fingerprint and Face ID simulation

Digital Lab's authentication simulation feature lets you simulate fingerprint and Face ID authentications on mobile devices.

About fingerprint and Face ID authentication

Fingerprints and Face IDs are often used for security authentication on mobile devices. Apps may utilize these authentications to secure sensitive features such as sign-on and payments

If the device you are testing is not physically available, you are not able to authenticate with a fingerprint or Face ID during your test. This feature simulates the entering of a fingerprint or a face ID on the device’s screen.

When you run an app that prompts you for authentication, Digital Lab opens the Simulation Authentication dialog box. This dialog box lets you select an authentication result: Success, Failure, or Cancel.

Note: Fingerprint authentication simulation is supported on both Android and iOS devices. Cryptography and Face ID are not supported on Android.

Back to top

Prepare for simulation

To prepare for authentication simulation:

  1. If you are doing a fingerprint simulation on Android, make sure you have enabled fingerprint authentication on the device. On most devices, this only requires enabling screen lock, using a PIN for example.
  2. Create a packaged version of the app that utilizes the authentication.
  3. Upload the packaged app to the lab. For details, see Manage apps.

Back to top

Perform the simulation in idle mode

You can simulate fingerprint or face ID authentication in idle mode from the Digital Lab or from within UFT One.

  1. Begin interacting with the device. Navigate to the screen in the app that requires fingerprint authentication.
  2. Wait for Digital Lab to open the Simulate Authentication dialog box.

  3. Select an authentication result: Success, Failure, or Cancel.
  4. For Failure or Cancel, select a reason.
  5. Click OK. A status bar in the lower section of the window, indicates if the simulation succeeded. A successful simulation is when it recognizes your specified result: Success, Failure, or Cancel.
  6. To add more simulations, refresh or re-navigate to the page in your app that requires these authentications, and repeat the above steps.

Back to top

Authentication results and reasons

When your app requires fingerprint or Face ID authentication, Digital Lab opens the Simulation Authentication dialog box. This dialog box lets you select an authentication result: Success, Failure, or Cancel.

For Failure and Cancel, you specify a reason for the result.


  • Too many failed attempts
  • Authentication was not recognized
  • No authentication method was registered (iOS only)
  • Finger moving too fast (Android only)
  • Fingerprint sensor is dirty (Android only)


  • Canceled by the user (on Android, OS version 8.1 or higher is required)
  • Canceled by the system

If you are running the app from a testing tool or using a REST API call, Digital Lab generates a response indicating the reason that you specified for the failure or cancellation.

Back to top

Tips and Guidelines

  • The native API is not supported for this simulation.

  • When working with fingerprint simulation, the fingerprint authentication dialog box may not trigger on certain Samsung 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 are prompted for a password.

    The touch sensor on Samsung Note 4 devices is not detected through the Android SDK API call isHardwareDetected. If your custom app requires isHardwareDetected=true to trigger fingerprint authentication, the fingerprint authentication is not triggered and the Fingerprint Simulation dialog box does not open in the remote view.

  • Fingerprint and Face ID authentication is implemented by developers in different ways. As a result, the behavior of apps may vary when you set the response to Failure.

See also: