Android Secure Components v3.10.0

Improved reliability for PSAPSA Push Step-up Authentication - the mechanism in our mobile SDKs that delivers a step-up challenge to an enrolled device as a push notification and verifies it with the user's device biometrics. PSA covers device enrollment, biometric login, and biometric verification of SCA challenges for sensitive operations such as outgoing wire transfers or accessing card details. Exposed as `UXComponents.psa` on iOS and Android and via `initializePSA` on React Native. (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, enrollment, 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 PSAPSA Push Step-up Authentication - the mechanism in our mobile SDKs that delivers a step-up challenge to an enrolled device as a push notification and verifies it with the user's device biometrics. PSA covers device enrollment, biometric login, and biometric verification of SCA challenges for sensitive operations such as outgoing wire transfers or accessing card details. Exposed as `UXComponents.psa` on iOS and Android and via `initializePSA` on React Native. flows-fixed cases where enrollment, 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.