--- title: "Release Notes Version 5.3.0" slug: "fas-5x-release-notes-version-5-3-0" updated: 2026-11-11T09:27:28Z published: 2026-11-11T09:27:28Z canonical: "docs.onespan.com/fas-5x-release-notes-version-5-3-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. # Release Notes Version 5.3.0 ## New features and enhancements ### Android #### Support for Kotlin 2.2.21 The SDK has been updated and now supports Kotlin version 2.2.21. #### Target API level increased to Android 16 (API 36) The target version of the SDK has been increased to Android 16 with API level 36. ### iOS #### Minimum supported version increased to iOS 16 The minimum supported version of the SDK has been increased to iOS 16. ## Fixes and other updates ### All Platforms MSS-12585 (Support case INC0015898): Improve server error handling for UAF **Description**: The behavior of the `notifyUAFResult()` API and how the UAF status codes were handled with `uafStatusCode` was not consistent on Android and iOS, and the behavior for key deletion differed slightly between registration and authentication flows. The SDK deleted keys for specific failure status codes differently. During authentication, keys were only deleted if the status code explicitly indicates invalidity and not for codes that indicate content issues. **Status**: This issue has been fixed. The behavior on iOS and Android was aligned to ensure consistent behavior across platforms and compliance with FIDO standards. Now, keys are only deleted if the server status code is one of the following (regardless of the operation type): - Unknown Key ID (`1481`) - Unacceptable Authenticator (`1492`) - Revoked Authenticator (`1493`) - Unacceptable Key (`1494`) - Unacceptable Algorithm (`1495`) For registration operations only, keys are deleted even if `statusCode` is nil, i.e., no status code is provided. And for authentication operations, keys are only deleted if a status code is provided and it matches one of the above failure/clearance codes. If `statusCode` is nil, no key is deleted for authentication operations. ### Android MSS-12652 (Support case INC0015944): App terminated unexpectedly during biometric authentication **Description**: During biometric authentication using the FIDO Authentication Solution, when the user launched the Android sample app and clicked FIDOCLIENT EXAMPLE, the app terminated unexpectedly, and the SDK did not handle the `BIOMETRY_UNAVAILABLE` (`-9100`) error. This termination was related to the Verify it’s you in the Fingerprint Authentication settings in Android. This setting is by default enabled but when the user disables it, the app terminates unexpectedly on some devices. **Status**: As this issue was caused by system behavior, it could not be fixed. The error that the SDK receives is correct, as it is not possible to process the identification fully because the Android setting has been disabled, and the SDK is not handling any exceptions during the initialisation of the FIDO client. However, the sample app has been enhanced to handle the exception gracefully. Now, the app does not terminate unexpectedly. Instead, only the PIN Authenticator is available. ## Supported platforms For information on the supported operating systems and platforms supported by Mobile Security Suite and the affiliated SDKs, see [Supported platforms.](/mobile/docs/mss-rn-supported-platforms-4-39-0) ## Known issues For information on issues that have not yet been resolved in this release of Mobile Security Suite, see [Known issues](/mobile/docs/mss-rn-known-issues-4-39-0). ## API reference documentation and sample applications To learn more about the public APIs and their functions, exceptions, and error codes, refer to the technical documentation that is included in the product package for each SDK and each platform. In the product package, you can also find the sample applications provided for each platform to see examples of how the SDKs can be used. > These sample apps are intended only to demonstrate basic scenarios and SDK usage. They are not designed to be copied directly into production projects! ## Third party licenses For information on third party dependencies associated with Mobile Security Suite and the affiliated SDKs in this release, see [Third party licenses](/mobile/docs/mss-rn-third-party-licenses-4-39-0).