Releases: Iterable/iterable-swift-sdk
Releases · Iterable/iterable-swift-sdk
6.6.5
Fixed
- Fixed an issue where concurrent API requests failing with JWT-related 401 errors could be dropped instead of retried after a new token was obtained, ensuring all affected calls are executed once authentication succeeds.
Added
- Added optional Embedded Messaging sync callbacks via the
IterableEmbeddedUpdateDelegateprotocol, allowing apps to react when an embedded sync succeeds or fails. - Added an optional
placementIdsparameter tosyncMessagesonIterableEmbeddedManager, so apps can fetch and update embedded messages only for specific placements, bringing iOS to parity with the Android SDK.
6.6.4
6.6.3
6.5.15
6.6.2
6.5.4.1
6.6.1
6.6.0
Added
- Introduces support for Unknown user activation, a feature that allows marketers to convert valuable visitors into customers. With this feature, the SDK can:
- Fetch unknown user profile creation criteria from your Iterable project, and then automatically create Iterable user profiles for Unknown users who meet these criteria.
- Save information about a user's previous interactions with your application to their unknown user profile, after it's created.
- Display personalized messages for Unknown users (in-app, push, and embedded messages).
- Merge unknown user profiles into existing, known user profiles (when needed).
IterableConfigis updated with anenableUnknownUserActivationflag that needs to be set to true to allow use of the unknown user activation functionality- Unknown user activation is currently in public beta. If you'd like to learn more about it or discuss using it, talk to your Iterable customer success manager (who can also provide detailed documentation).
- To learn more, read Unknown User Activation: Developer Docs.
6.5.14
6.5.13
- Fixed in-app messages displaying in wrong window when using Stage Manager or multi-window scenarios on iPad.
- Fixed redirect handling issue with deep links that was preventing proper URL following.
- Improved action runner logic to properly validate allowed protocols before processing URL actions, ensuring better security and reliability.