Releases: Futurae-Technologies/ios-sdk
3.7.1
- Added
error_type(raw value ofSDKErrorType) toNSError.userInfoto support Objective-C error classification.
Check the error section in the guides for more information: https://www.futurae.com/docs/guide/futurae-sdks/mobile-sdk-ios/#sdk-error-handling
3.7.0
-
[Changed] Improved internal database handling for more reliable and efficient access.
-
[Fixed] Made the
errorTypeproperty ofSDKBaseErroraccessible in Objective-C contexts. -
[Changed] SDK now tracks biometric configuration changes only if:
- the SDK is configured with biometrics-only lock, or
- the SDK PIN lock is used and biometrics are enabled.
-
[Added] New API method
getSessionInfoWithoutUnlockfor fetching session details without unlocking the SDK. Note: Must be enabled per service. Contact support@futurae.com for activation. -
[Added] Support for usernameless authentication and transaction approval via a new URI type:
FTRURLType.usernamelessAuth. TheFTRUtilsclass has been updated accordingly. -
[Added] Convenience methods in
FTRUtilsfor extracting authentication session data directly from push notification payloads.
v2.6.5
v2.6.4
3.6.6
-
[Changed] Add new method to retrieve SDK logs
FTRClient.logsReportwhich doesn't require SDK launch.
SDK logging is not enabled by default, to enable call FTRClient.enableLogging() before launching the SDK. -
[Changed] Improved threading behavior during public key submission to ensure more efficient execution.
v2.6.3
3.6.5
v2.6.2
v1.7.1
3.6.4
- [Fix] Issue where full device display name (iPhone instead of iPhone 11 Pro for example) is not shown in admin dashboard after account migration
- [Changed] Encrypt and exclude from backup local stored files related to SDK logs and adaptive collections
- [Added] Add comments for SDK error codes
- [Changed] SDK logging is not enabled by default anymore. To enable call
FTRClient.enableLogging()before launching the SDK and the SDK will log information about its operations.