Skip to main content

Android Secure Components v3.10.0

· One min read

Improved reliability for PSA (push step-up authentication) user journeys when SDK configuration and Play Integrity checks are still being prepared, and clearer failure messages when those steps do not complete in time.

Changed

  • Error messages on failure—when a security-sensitive user journey (for example, enrolment, biometric login, or step-up approval) fails because configuration or Play Integrity could not be ready in time, listeners and callbacks may receive a more specific ErrorResponse.message (including a short reason such as timeout or token failure) instead of a generic network error.

Fixed

  • Timing around config and PSA flows—fixed cases where enrolment, biometric login, or step-up approval could start before Play Integrity was fully ready, which could lead to missing integrity data or a poor user experience.