Skip to content

v3.3.2

Choose a tag to compare

View all tags
@nasiaFuturae nasiaFuturae released this 05 May 12:54
v3.3.2
210f529

Changelog

New Features

  • Universal Links: Enable handling of universal links via SDK URI methods. The following methods now also works with associated verified app links:
    • FuturaeOperationsApi.handleUri,
    • EnrollmentInput.URI,
    • FTUriUtils.isEnrollUri and
    • FTUriUtils.isAuthUri.
  • Custom in-app Messaging: Support for custom-payload FCM push notifications. To receive them, the SDK will send a local broadcast with Intent action FTNotificationUtils.INTENT_CUSTOM_NOTIFICATION. In case of your own custom FirebaseService implementation, call FuturaeOperationsApi.handlePushNotification to trigger the broadcast. In case of using the default FTRFcmMessagingService, the intent broadcast happens automatically upon receiving the notification.

Behavior changes

  • Update all system authentication errors (e.g. Biometric auth) to return FTLockAuthenticationFailedException(@BiometricPrompt.AuthenticationError val authenticationError : Int?, throwable: Throwable) which now also contains the error code returned by the system authentication.
  • Increase read timeout in OkHttpClient from 15 to 30 seconds.

Bug Fixes

  • Catch any exceptions on QR code type detection. Instead of throwing an error the FTQRCodeUtils.getQrcodeType will now return QRType.Invalid.
  • Fix FuturaeSDK.reset bug throwing error when used prior to SDK initialization.
  • Fix FuturaeSDK.launchAccountRecovery bug regarding FCM token not being registered during SDK Recovery, leading to user being unable to receive a push notification, unless he/she reopens the app.
  • Fix FuturaeSDK.launchAccountRecovery bug regarding success callback not being triggered on healthy / non-corrupted SDKs.
  • Fix FuturaeSDK.launch and FuturaeSDK.launchAccountRecovery bug making migration from v1 impossible.
  • Fix FuturaeSDK.launchAccountRecovery() bug that was making re-attemptAccountRecovery unavailable after a failed attempt.
  • Fix FTUriUtils.isEnrollUri() and FTUriUtils.isAuthUri() bug that did not recognize URIs with scheme other than futurae. This means that now both enroll and auth URIs are supported regardless of the scheme.

Note

  • Maintenance: Bump third-party dependencies to their latest stable version
Assets 2
Loading