iOS SDK: Swift concurrency breaking changes for iOS 9.0.0
Released on 31 July
This announcement was made on the 28 July.
We expect to release these changes into production on approximately the 31 July.
There are several updates with our iOS SDK release that are considered breaking due to the migration from BrightFutures to Swift’s native concurrency.
Action
Read the following for an overview of the changes.
Swift concurrency or Reach5Future SDK
-
The main ReachFive iOS SDK now uses
async throwsfor asynchronous operations.See Migrating from BrightFutures to Swift Concurrency for details on migrating from BrightFutures to Swift’s native concurrency.
-
We have introduced the Reach5Future SDK compatibility bridge to maintain support for BrightFutures-based methods, allowing customers to continue using
Futurewithout immediate migration.See Migrating to the Reach5Future SDK compatibility bridge for details on using the Reach5Future SDK.
Why did we do this?
We migrated to Swift’s native concurrency model to enhance performance, reliability, and maintainability of our iOS SDK. This change aligns with modern Swift development practices and ensures a more robust and efficient SDK for our users. The introduction of the Reach5Future SDK allows for a smoother transition for existing users while they adapt to the new concurrency model.