Release Notes Version 5.6.0

The sample app has been updated to support edge-to-edge display for Android 15 (API level 35) and later. For more information about edge-to-edge display, refer to the Android Developer Documentation.

As of this version, the SDK now supports Kotlin version 1.9.25 and Dokka version 1.9.20.

The Secure Storage SDK now supports using the accessGroup parameter. This allows you to

• control scoping by creating a storage in a specific access group (AppPrivate vs. AppGroup)

• move an existing storage between access groups

• delete a storage within a targeted access group

• check the existence of a storage in a given access group

The accessGroup parameter has been added to

• initializeInstance(fileName:fingerprint:accessGroup:)

• delete(fileName:accessGroup:)

The following new interfaces have been created:

• storageExists(fileName:accessGroup:)

• move(to:fingerprint:protection:) in SecureStorage protocol

During the implementation, the initalizeInstance and delete legacy overloads without accessGroup have been deprecated.

To ensure backward compatibility, passing nil for accessGroup preserves the previous default behavior, and the deprecated methods remain functional. However, we recommend to migrate to the new methods.

We recommend integrating the new interface to standardize on explicit accessGroup usage for clarity and future compatibility.

Description: The following new error codes had been added incorrectly to the SDK:

• BIOMETRIC_CRYPTO_OBJECT_MISSING: -4335

• INVALID_STORAGE_VERSION: -4336

• SECURE_KEY_CORRUPTED: -4338

• STORAGE_NOT_LOADED: -4339

Status: This issue has been fixed. The error codes have been removed from the SDK.

Description: In version 5.5.0, the async keyword was removed from the method to delete a Secure Storage or storage instance, delete(fileName:), which means, this method is no longer asynchronous. Also, the method signature changed from public static func delete(fileName: String) async throws to public static func delete(fileName: String) throws, and you do not have to use the await keyword when calling this method.
This simplifies usage in synchronous contexts and aligns with updated concurrency requirements in Swift 6. This API change was not described in the user documents.

Status: This issue has been fixed. The integration guides for versions 5.5.0 and 5.6.0 have been updated accordingly. For more information, see Available methods in the Secure Storage SDK (5.5.0) and Available methods in the Secure Storage SDK (5.6.0).