v3.2.0

Changelog

New Features

• FuturaeSDK.launchAccountRecovery available for all SDK LockConfigurationTypes.
• NEW API: FuturaeAdaptiveAPI to wrap all adaptive SDK related operations. Includes new operation collectAndSubmitObservations.
• Adaptive Learning Mode: Fine tune adaptive SDK configuration.
  You can now configure adaptive SDK to:
  • only gather adaptive observations to train a profile
  • include adaptive observations in authentications
  • include adaptive observations for account migration.
    For more info please refer to our documentation.
• QRType.Invalid: Added QRType.Invalid for scanned QR codes that are invalid.
• NEW API: SDKConfiguration now supports flag allowChangePinCodeWithBiometricUnlock that allows calling FuturaeLockApi.changeSDKPin under LockConfigurationType.SDK_PIN_WITH_BIOMETRICS_OPTIONAL while unlocked with Biometrics. This flag can be enabled/disabled without switching SDK configuration.

Behavior changes

• When updating to this SDK version, biometrics will remain enabled for users that had it enabled before the SDK version update. Related to bug fix below.
• Removed blocking behavior from SDK to backend sync. This will eliminate random FTSDKBlockedException occurrences when trying to approve sessions immediately after calling getAccountsStatus
• The SDK will automatically trim and replace empty spaces " " from enrollment activation short-code inputs.
• Method FTQRCodeUtils.getQrcodeType returns QRType.Invalid instead of throwing FTMalformedQRCodeException or defaulting to an Enrollment type. Note: This can potentially lead to breaking change if exhaustive when statement is being used.
• FTQRCodeUtils.getUserIdFromQrcode now supports extracting user-id from Enrollment QR codes.
• FuturaeAccountApi.registerFirebasePushToken can be called even without enrolled accounts in the SDK. It will ensure that the SDK uploads the FCM token as soon as possible (at least one account is enrolled).
• FuturaeLockApi.changeSDKPin: Allow configuring whether Biometric unlock is sufficient in order to change SDK PIN while lock configuration is SDK_PIN_WITH_BIOMETRICS_OPTIONAL. 
In order to configure it, use the newly introduced method SDKConfiguration.lockConfigurationType.setAllowChangePinCodeWithBiometricUnlock. This configuration option is allowed only for LockConfigurationType.SDK_PIN_WITH_BIOMETRICS_OPTIONAL.
• The SDK will perform a URL whitelist validation for SDK base_url and activation_code enrollment urls.
That means that the SDK will throw FTInvalidArgumentException if the ftr_base_url is not a valid futurae domain in the following cases:
  • FuturaeSDK.launch
  • FuturaeSDK.launchAccountRecovery
  • FuturaeSDK.reset
  • any enrollment with QR code.

Bug Fixes

• Fix bug that automatically disables biometrics for SDK LockConfigurationType.SDK_PIN_WITH_BIOMETRICS_OPTIONAL when migrating from SDK v2.3.0 or earlier to a later version.
• Fix Usernameless QR bug crashing when used with Adaptive authentication on a background thread.
• Fix bug not updating SDK's account username and service-name from accountsStatus operation.
• Fix AccountsStatus model having empty messages: List<ApiMessage> field.
• Fix a bug responsible for submitting null adaptive collections from SDK.
• Fix FuturaeOperationsApi.handleURI and FTUriUtils.isEnrollUri crashing from invalid URIs.
• Fix SDK not recognizing available “Device credentials” on older Android Devices (Android 10 and below)
• Make sure SDK Pin is zeroed out in memory after unlock duration expired.