--- title: "Fingerprints: additional considerations" slug: "device-binding-sdk-ig-fingerprints-additional-considerations-5-8-0" updated: 2026-08-27T13:57:51Z published: 2026-08-27T13:57:51Z canonical: "docs.onespan.com/device-binding-sdk-ig-fingerprints-additional-considerations-5-8-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # Fingerprints: additional considerations ## Migration of fingerprint generation types > Currently, the Device Binding SDK does not provide a migration path between the different fingerprint generation types. ## New fingerprint needed after backup or restores The Device Binding SDK does not support the backup/restore features available on the iOS and Android platforms. In the past, on iOS, it was possible to generate the same fingerprint when data was restored on the same device. But since the introduction of highly-secured key generation using native hardware capabilities (Secure Enclave), this is no longer possible. Now, after a backup and restore function, all Keychain items are securely deleted and a new fingerprint is generated and stored on your device. This process is completely handled by the Device Binding SDK. ## Considerations for Android ### Generate fingerprints when HARDWARE parameter cannot be used 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. ### Fallback mechanism for Keystore exception Depending on the OEM and their specific implementation of HARDWARE-backed keystores (Strongbox and TEE), some device models — including devices from Sony, Honor, and other manufacturers — may throw low-level exceptions (mapped to error codes `4409` or `4400`) during fingerprint generation using the Hardware options (`HARDWARE` and/or `HARDWARE_WITH_TEE`). The stack trace points to an underlying Keystore exception originating below the application/SDK layer. Since this behavior is tied to the OEM's Strongbox/TEE implementation, it cannot be handled by or worked around from the SDK. This issue is often triggered after a device receives a security or Android update, and may similarly be resolved by a future update, though this cannot be guaranteed. To mitigate this risk, you can implement a fallback mechanism based on your specific requirements and how you are handling fingerprint continuity and security: - **Falling back between** `HARDWARE` **and** `HARDWARE_WITH_TEE`: the fingerprint value remains unchanged. - **Falling back to** `ANDROID_ID` (if both hardware options are throwing exceptions): the fingerprint value will be different from the one previously generated. ## Considerations for iOS ### Migrating the fingerprint on iOS 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. #### Migration from Device Binding SDK 5.0.0 or earlier: If your application has access to the "*" Keychain access group, you can re-use the same fingerprint. For instructions on how to reuse a fingerprint, refer to the technical documentation included in the product package. #### Migrating from Device Binding SDK 4.27.1: If you are migrating from version 4.27.1 specifically, the fingerprint can not be migrated to a different access group and can only be obtained from the access group in which it was created. #### Migrating from Device Binding SDK 4.26.0 or earlier: If you are migrating from version 4.26.0 or earlier, the fingerprint will be migrated to the access group passed in the first call after the migration.