Overview​

We have identified an issue with version 3.22 of the iOS SDK that we recently released.

We are currently prioritising a fix and anticipate that it will be ready in a couple of weeks. In the meantime, we have removed this version of the SDK from our repository.

How to upgrade​

We will inform you when the fix has been rolled out, so that you can upgrade your iOS app to use the latest version.

What is new?​

For an overview of the changes, see the version notes for each platform:

• Android
• iOS

How to upgrade​

For the latest features and security improvements, you need to upgrade your mobile app to use the most recent version of the SDK.

To learn how to do this, see our Upgrade guide.

What is new?​

For an overview of the changes, see the version notes for each platform:

• Android
• iOS

How to upgrade​

For the latest features and security improvements, you need to upgrade your mobile app to use the most recent version of the SDK.

To learn how to do this, see our Upgrade guide.

Patch overview​

This patch enhances the stability and performance of biometric operations on Android.

To prevent potential Application Not Responding (ANR) errors, heavy cryptographic tasks are now processed on a background thread. This change ensures that client applications can now safely initiate biometric operations from either the Main thread or an I/O thread without risking UI freezes or StrictMode violations.

For integrations using the androidx.biometric library, the SDK is now lifecycle-aware. This ensures that the biometric prompt is automatically and safely cancelled in response to application lifecycle changes.

Affected versions​

If your app uses an affected version of the SDK, then you should upgrade it to use the latest, patched version:

How to upgrade​

For the latest features and security improvements, you need to upgrade your mobile app to use the most recent version of the SDK.

To learn how to do this, see our Upgrade guide.

Patch overview​

3.21.7, 3.20.10​

• Fixed an issue where AsyncCallback for finishAuthentication sends the result more than once for AndroidX BiometricPrompt.
• Fixed the race conditions in the BiometricPrompt cancellation logic.
• Fixed a crashing issue that would happen when running any start operation quickly after calling deactivate().

3.21.7​

• Fixed an issue where isActivated(DEVICE_ANDROID_BIOMETRIC_PROMPT) was true after removing all fingers.

Affected versions​

If your app uses an affected version of the SDK, then you should upgrade it to use the latest, patched version:

How to upgrade​

For the latest features and security improvements, you need to upgrade your mobile app to use the most recent version of the SDK.

To learn how to do this, see our Upgrade guide.

Patch overview​

Fixed an issue where the API could return clientErrorOperationInProgress for an AndroidX BiometricPrompt authentication, where the BiometricPrompt dialog had become dismissed due to app switching.

Affected versions​

If your app uses an affected version of the SDK, then you should upgrade it to use the latest, patched version:

How to upgrade​

For the latest features and security improvements, you need to upgrade your mobile app to use the most recent version of the SDK.

To learn how to do this, see our Upgrade guide.

Patch overview​

Fixed an issue that caused SDK operations to fail on devices running Android 11 (API 30) and below, with the error WifiService: Neither user … nor current process has android.permission.ACCESS_WIFI_STATE.

This error was present on apps lacking the permission required for collecting Wi-Fi information (SSID and BSSID), even if these risk parameters were disabled in the server configuration.

Affected versions​

If your app uses an affected version of the SDK, then you should upgrade it to use the latest, patched version:

How to upgrade​

For the latest features and security improvements, you need to upgrade your mobile app to use the most recent version of the SDK.

To learn how to do this, see our Upgrade guide.

Patch overview​

Introduced locationEnabled flag in EncapConfig. If you set this flag to false, then you prevent the SDK from requesting location updates.

Affected versions​

If your app both:

• Requests location permission.
• Has location, geofencing, and SSID/BSSID features disabled.

Then you can upgrade it to use the latest, patched version and set the locationEnabled flag to false:

How to upgrade​

For the latest features and security improvements, you need to upgrade your mobile app to use the most recent version of the SDK.

To learn how to do this, see our Upgrade guide.

Patch overview​

Fixed an issue that caused duplicate symbol errors during linking when Swift Protobuf was included as a dependency.

Affected versions​

If your app both:

• Has Swift Protobuf as dependency.
• Uses an affected version of the SDK.

Then you should upgrade it to use the latest, patched version:

How to upgrade​

For the latest features and security improvements, you need to upgrade your mobile app to use the most recent version of the SDK.

To learn how to do this, see our Upgrade guide.

Patch overview​

Fixed an issue where the location was being sent in Encap SDK operations, even if the location was disabled in the device's system settings.

Affected versions​

If your app has either location or geofencing features enabled, then you should upgrade it to use the latest, patched version:

How to upgrade​

For the latest features and security improvements, you need to upgrade your mobile app to use the most recent version of the SDK.

To learn how to do this, see our Upgrade guide.

What is new?​

For an overview of the changes, see the version notes for each platform:

• Android
• iOS

How to upgrade​

For the latest features and security improvements, you need to upgrade your mobile app to use the most recent version of the SDK.

To learn how to do this, see our Upgrade guide.

Patch overview​

Fixed an issue where the finishActivation operation or the startAuthentication operation terminated the app due to an uncaught exception.

Affected versions​

If your app both:

• Has either location, geofencing or app attestation features enabled.
• Uses an affected version of the SDK.

Then you should upgrade it to use the latest, patched version:

How to upgrade​

For the latest features and security improvements, you need to upgrade your mobile app to use the most recent version of the SDK.

To learn how to do this, see our Upgrade guide.

Patch overview​

Fixed an issue where the startActivation operation does not trigger the location permission prompt. This patch also resolves a related bug that could cause subsequent operations to hang when location is disabled and enabled again.

Affected versions​

If your app both:

• Has the location or geofencing feature enabled.
• Uses an affected version of the SDK.

Then you should upgrade it to use the latest, patched version:

How to upgrade​

For the latest features and security improvements, you need to upgrade your mobile app to use the most recent version of the SDK.

To learn how to do this, see our Upgrade guide.

Patch overview​

Fixed an issue where clientErrorDowngradeDetected is not working as expected, possibly giving false positives.

Affected versions​

If your app uses an affected version of the SDK, then you should upgrade it to use the latest, patched version:

How to upgrade​

For the latest features and security improvements, you need to upgrade your mobile app to use the most recent version of the SDK.

To learn how to do this, see our Upgrade guide.

Patch overview​

Removed a workaround for older OnePlus devices that was causing issues for newer ones.

This fixes an issue where using the wrong fingerprint on a modern OnePlus device would sometimes result in BiometricPrompt dismissing itself.

Affected versions​

If your app uses an affected version of the SDK, then you should upgrade it to use the latest, patched version:

How to upgrade​

For the latest features and security improvements, you need to upgrade your mobile app to use the most recent version of the SDK.

To learn how to do this, see our Upgrade guide.

Patch overview​

• Adds support for Android 16 (targetSdkVersion 36).
  • This avoids potential build warnings for apps targeting Android 16.
• Improves performance.
  • SDK calls are now faster, with startAuthentication() calls now up to 2.5 times faster.
  • The AndroidLoggingController class that provides logging of API calls for development purposes now includes the logging time used by the call.
• Removes BiometricPrompt workaround for previous OnePlus phone bug.
  • This avoids a problem that could occur with wrong biometrics on newer or updated OnePlus phones, that would cause biometric authentication to abort with clientErrorAndroidBiometricPromptAuthenticationFailed instead of letting the user retry.

Affected versions​

If your app uses an affected version of the SDK, then you should upgrade it to use the latest, patched version:

How to upgrade​

For the latest features and security improvements, you need to upgrade your mobile app to use the most recent version of the SDK.

To learn how to do this, see our Upgrade guide.

What is new?​

For an overview of the changes, see the version notes for each platform:

• Android
• iOS

How to upgrade​

For the latest features and security improvements, you need to upgrade your mobile app to use the most recent version of the SDK.

To learn how to do this, see our Upgrade guide.

Upcoming changes​

In the next SDK version (3.21), we will make the following changes:

• For Android, RecoveryMethod.CLOUD_BACKUP will be renamed to RecoveryMethod.CLOUD_BACKUP_RECOVERY_CODE.
• For iOS, the RecoveryMethod.backup case will be renamed to RecoveryMethod.backupRecoveryCode.
• For iOS, the SDK minimum supported iOS version will be 15.

Patch overview​

• This patch sets the right storage name for the storage version during a storage upgrade.
• This means that in the rare occasion that a storage upgrade fails to read a specific file, we do not overwrite clientSaltKeyNextId the next time we try to upgrade, which causes the missingParameter error.

Affected versions​

If your app uses an affected version of the SDK, then you should upgrade it to use the latest, patched version:

How to upgrade​

For the latest features and security improvements, you need to upgrade your mobile app to use the most recent version of the SDK.

To learn how to do this, see our Upgrade guide.

Patch overview​

3.19.6, 3.18.20​

• Adds support for Android 15 (targetSdkVersion 35).
• This avoids potential build warnings for apps targeting Android 15.

3.19.6, 3.18.20, 3.17.13​

• Changes the JSONObject type of clientSaltNextKeyId to Long.
• This avoids potential errors in apps with a strict JSON parser, such as JSONObject["clientSaltNextKeyId"] is not a string.

3.19.6​

• Filters out DEVICE_BIOMETRIC_PROMPT on Android 9, when the app does not include AndroidX BiometricPromptEncap.
• This ensures that the Encap API supports BiometricPrompt in all apps.

Affected versions​

If your app uses an affected version of the SDK, then you should upgrade it to use the latest, patched version:

How to upgrade​

For the latest features and security improvements, you need to upgrade your mobile app to use the most recent version of the SDK.

To learn how to do this, see our Upgrade guide.

Patch overview​

• Fixed bug in the migration code for the extension support feature, when multiple Keychain groups are configured.
• This bug results in a missing deviceHash after migrating to extension support. It causes the SDK to generate a new value on the next authentication attempt, which results in a deviceHash mismatch. It is then not possible to authenticate with that registration.

Affected versions​

If your app both:

• Uses the extension support feature, in combination with multiple Keychain groups configured for the app.
• Uses an affected version of the SDK.

Then you should upgrade it to use the latest, patched version:

How to upgrade​

For the latest features and security improvements, you need to upgrade your mobile app to use the most recent version of the SDK.

To learn how to do this, see our Upgrade guide.