For the complete documentation index, see llms.txt. You can also append .md to any page URL to get its markdown version.
Skip to main content
For the complete documentation index, see llms.txt.

Fixed start after deactivate and BiometricPrompt callback issues

· 2 min read

We have released new patch versions 3.20.10 and 3.21.7 for the Android SDK.

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().
Breaking change

If you are using state EncapController.State.PROCESSING_DEACTIVATION, then this update introduces a breaking change and you need to replace all occurrences with the following in your code:

  • EncapController.State.PROCESSING_START_DEACTIVATION
  • EncapController.State.PROCESSING_FINISH_DEACTIVATION

To learn more, see the Deactivation states section in our Controller states documentation.

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:

Affected versionsPatched version
3.21.6 and earlier3.21.7
3.20.9 and earlier3.20.10

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.