2.2.3

Now reinitialising URLSession on non-http-errors, before throwing an error

2.2.2

Now reinitialising URLSession on non-http-errors, before throwing an error

2.2.1

Added missing public init to TIMKeyModel.

2.2.0

Adds a new willBeginNetworkRequests closure to the following calls:

• storeViaBiometric
• getViaBiometric

This will come in handy when showing a loading indicator when the actual network requests begin. Before this change you had to start the indicator before the FaceID/TouchID operation was completed.

2.1.4

Work around for issue in Xcode 13.0.
GCM encryption now contains a dummy implementation, which never will be invoked, but it fixes the build issue that occurred in Xcode 13.0.

2.1.3

The following two error cases now contains an associated value (Error) to provide more information about what failed when encryption/decryption fails:
TIMEncryptedStorageError.failedToEncryptData
TIMEncryptedStorageError.failedToDecryptData

2.1.2

Constructor of TIMESKeyCreationResult is now public.

2.1.1

• Fixes issue where OSStatus mapping in TIMKeychain was hardcoded to the description of errSecNoStorageModule. This is now fixed to match the actual OSStatus. The error number was correct, though.
• Now maps OSStatus.errSecInteractionNotAllowed statuses to TIMSecureStorageError.authenticationFailedForData since Apple reports that error when the app is sent to background whlie biometric dialog is open. This is an uncritical error and should not be handled as a failedToLoadData as it was before.

2.1.0

TIMSecureStorageError now has associated values which contain an error message to give a more clear description on what failed.
The following cases are affected:

• TIMSecureStorageError.failedToStoreData
• TIMSecureStorageError.failedToLoadData

The TIMKeychain implementation will report descriptions for the OSStatus from the keychain operation.

2.0.0

We have restructured the inner architecture of TIMEncryptedStorage to make it more testable. The goal has been to implement a lot of tests to ensure a more stable framework, but also to make it more testable for the developers using it.
The framework is now heavily based on protocols and internal implementations instead of static implementations.

The following changes are needed to migrate from 1.*.* to 2.0.0:

• TIMEncryptedStorageError.keychainFailed is now known as TIMEncryptedStorageError.secureStorageFailed
• TIMKeychainError is now known as SecureStorageError
• TIMEncryptedStorage is not longer static, so you will have to create an instance which is configured through the constructor instead of the old configure method.

We are bumping to 2.0.0 because this is a huge step forward for TIMEncryptedStorage in terms of testability.