Skip to content

Releases: Futurae-Technologies/ios-sdk-beta

3.1.7-beta

09 May 00:14
31beae1
Compare
Choose a tag to compare
  • [Updated] Include required keys in privacy manifest file

3.1.6-beta

25 Apr 16:10
2418535
Compare
Choose a tag to compare

This release focuses on resolving Apple's requirements for usage of private APIs.

  • [Removed] Removed usage of APIs that track disk space. Those were not used by SDK, but the dependency of the SDK.
  • [Updated] Added .xcprivacy declaration for UserPreferences API usage.

3.1.5-beta

05 Apr 10:11
9aa6a40
Compare
Choose a tag to compare
  • [Added] Trusted Session Binding for account migration

3.1.4-beta

29 Mar 19:03
1b90da5
Compare
Choose a tag to compare
  • [Added] Flow binding implementation for enrollment

3.1.3-beta

27 Mar 15:45
0db427f
Compare
Choose a tag to compare
  • [Fixed] Reject push authentication issue

3.1.2-beta

14 Mar 12:14
f4103ab
Compare
Choose a tag to compare
  • [Added] Authentication type in dictionary data provided via notification delegate method approveAuthenticationReceived
  • [Added] Expose SDK state to clients (not launched, launching, launched)
  • [Changed] Ensure sequential execution of asynchronous operations in the SDK
  • [Changed] Ensure public key is sent to backend before calling operations that depend on it
  • [Changed] SDKLockConfigStatus is removed and no longer available.
  • [Added] Add FTRUtils class with convenience methods to retrieve user id or session token from QR code or URI.
  • [Changed] Internal improvements

3.1.1-beta

12 Feb 11:05
641d375
Compare
Choose a tag to compare
  • Fixed issue where account status does not include extra info.
  • Internal changes related to Usernameless QR.

3.1.0-beta

31 Jan 15:25
0cbad4a
Compare
Choose a tag to compare
  • Added qrCodeScanRequested method to the FTRNotificationDelegate. It is called when online QR authentication is requested and feature is enabled on the backend side.
  • Added transparent approveInfo decryption, when it comes encrypted from the backend, in the getAccountsStatus and getSessionInfo methods. The feature needs to be enabled on the backend side.
  • decryptExtraInfo method now returns FTRExtraInfo array instead of dictionary array

3.0.1-beta

05 Jan 11:02
2f75823
Compare
Choose a tag to compare
  • Removed version tag from the binary marketing version to comply with appstore requirements.

v3.0.0-beta

13 Dec 12:33
2b98622
Compare
Choose a tag to compare

Added

  • Swift Rewrite with Objective-C Compatibility: Complete rewrite in Swift, offering modern language features while ensuring backward compatibility with Objective-C.
  • New Data Models: Introduction of strongly typed data models, replacing loosely defined or dictionary-type data for enhanced type safety and predictability.
  • AsyncTask and AsyncTaskResult Classes: New classes introduced to handle asynchronous operations in Swift, providing an efficient alternative to traditional callback patterns.
  • Enhanced Error Handling: Robust and informative error handling system implemented. Errors can now be cast to SDKBaseError or its subclasses for detailed context and understanding.

Changed

  • Method Names and Signatures: Comprehensive update of method names and signatures to align with the Swift codebase. Developers should update their code to match these changes.
  • Consolidated Methods: Optimization of similar methods, such as merging approve and reject into a single replyAuth method.

Migration Guide

Users migrating from SDK v2.x.x can follow the detailed step-by-step guide provided. This guide covers acquiring the beta version of the SDK, refactoring application code, and adapting to the significant changes in this version. For more details, check the online iOS SDK guide notes for migrating from SDK v2.x.x to v3.x.x.

Notes

This beta release marks a significant update, focusing on enhancing both performance and the development experience. It is recommended for users to migrate to this version to leverage the latest features and improvements. As this is a beta release, feedback and reports on any issues are highly encouraged to refine the SDK for its final release.