Additional considerations for Android

Migrations

We only support migration from an older version to a newer version of the SDK. If you need to run test scenarios with an older version, it is mandatory that you clear all fingerprints before running those test scenarios.

Fingerprints

We primarily recommend using the HARDWARE parameter to generate the device fingerprint except when the Device Binding SDK is not able to generate the fingerprint.

For example, there are known issues with:

• devices with Mediatek Chipset MT6737 (and variants) running Android 7

• Xiaomi Redmi Note 8 Pro devices running Android 11

In these cases, the SDK terminates unexpectedly while attempting to generate the fingerprint. As an exception, when the HARDWARE parameter cannot be used, we recommend using the ANDROID_ID option as a fallback mechanism.

Shared functionalities of the Device Binding SDK and other Device Binding SDK SDKs

The following features are included in the Device Binding SDK but a better practice is to integrate them with other Device Binding SDK SDKs

• New activations using the fingerprint method

  For more information, refer to the Digipass SDK  [%Global.GuideName.IntegrationGuide%].

• Managing the fingerprint as the unique identifier for the device

  For more information, refer to the Client Device Data Collector SDK Integration Guide.