3.9.3-beta

Exchange Token Support (QR codes & URLs)

• Exchange token validation & redemption via FTRClient
  Added new FTRClient APIs to redeem exchange tokens obtained from QR codes or URLs:

  • exchangeTokenForSessionToken(_:)
    Validates an authentication exchange token and returns a session token.

  • exchangeTokenForEnrollmentActivationCode(_:)
    Validates an activation exchange token and returns an enrollment activation code.

  Both APIs are available as:

  • Objective-C compatible callback-based methods
  • Swift-native AsyncTaskResult variants for async/await or task chaining

• Exchange token parsing utilities
  Added new FTRUtils helpers to extract authentication and activation exchange token data from QR codes, URLs, and URIs, eliminating the need for manual parsing:

  • authTokenExchangeFromQR(_:)
  • activationTokenExchangeFromQR(_:)
  • authTokenExchangeFromURL(_:)
  • activationTokenExchangeFromURL(_:)

  These methods return strongly typed exchange-token data objects, including the exchange token value and expiration timestamp.

• Extended QR code type support
  Added new FTRQRCodeType cases to explicitly represent exchange-token flows:

  • activationTokenExchange
  • authTokenExchange

• Extended URL type support
  Added new FTRURLType cases for exchange-token URLs:

  • activationExchangeToken
  • authenticationExchangeToken

These additions enable a complete exchange-token flow, allowing apps to:

1. Extract an exchange token from a QR code or URL
2. Redeem it via FTRClient
3. Receive a valid session token or enrollment activation code

3.9.2-beta

• Add new getPendingSessions method and corresponding FTRPendingSessions model.

3.9.1-beta

• Add new enrollAndGetAccount method
• Various internal improvements

3.9.0-beta

New Features

• Application Integrity Check Embedded into Enrollment and Authentication flow: Expose new feature which automatically transmits integrity check results, based on Apple's App Attest and Risk Assessment to the backend.
  To enable automatic transmission of Application Integrity Check information to the backend during enrollment and authentication, provide an instance of IntegrityVerdictConfiguration to the FTRConfig initalizer during the SDK launch.

Please contact Futurae Support at support@futurae.com to enable it for your service.Application Integrity Check Embedded into Enrollment and Authentication flow

Fixes

• Resolved an issue with the SDK method haveBiometricsChanged, which could return inconsistent results when called from an app extension (e.g., Notification Service Extension).
  The method has been reimplemented to ensure consistent behavior across both the main app and app extensions.

3.8.1-beta

• [Changed] SDK will track biometrics changes only under biometrics lock configuration or in SDK PIN lock configuration when biometrics are activated

3.8.0-beta

• Added new supported URI FTRURLType.usernamelessAuth to handle usernameless authentication and transaction confirmation. FTRUtils has been enhanced to support this new URI.

3.7.1-beta

• [Changed] Added method getSessionInfoWithoutUnlock for retrieving session information without prior unlocking and deprecated getSessionInfoUnprotected. Please note that this functionality needs to be enabled for the respective Futurae Service(s) which this SDK is associated with. For further details contact the Futurae support at support@futurae.com.

3.7.0-beta

• [Added] Support fetching extra info of an authentication session without prior unlocking the SDK, by exposing a new method getSessionInfoUnprotected. Please note that this functionality needs to be enabled for the respective Futurae Service(s) which this SDK is associated with. For further details contact the Futurae support at support@futurae.com.
• [Added] Added new methods in FTRUtils class for extracting information from a push notification payload

3.4.1-beta

Changelog

New Features

• Universal Links: Enable handling of universal links.
• Custom in-app Messaging: Support for custom-payload push notifications.

3.1.7-beta

• [Updated] Include required keys in privacy manifest file