Releases: Iterable/iterable-swift-sdk
Releases · Iterable/iterable-swift-sdk
6.6.0-beta1
- This release includes initial support for Anonymous user activation, a feature that allows marketers to convert valuable visitors into customers. With this feature, the SDK can:
- Fetch anonymous profile creation criteria from your Iterable project, and then automatically create Iterable user profiles for anonymous users who meet these criteria.
- Save information about a user's previous interactions with your application to their anonymous profile, after it's created.
- Display personalized messages for anonymous users (in-app, push, and embedded messages).
- Merge anonymous profiles into an existing, known user profiles (when needed).
- Anonymous user activation is currently in private 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).
6.5.7
6.5.6
6.5.5
Added
This version of Iterable's iOS SDK provides more insight into JWT refresh failures, so you can take appropriate action in your application code.
-
When a JWT refresh fails (for any of various reasons), the SDK calls
onAuthFailure(_ authFailure: AuthFailure)
on theIterableAuthDelegate
instance you provided to the SDK at initialization. TheAuthFailure
object provides more information about the failure. This method replacesonTokenRegistrationFailed(_ reason: String?)
. -
To set a retry policy for JWT refreshes, you can set the
retryPolicy
property onIterableConfig
to aRetryPolicy
object. Use this object to specify:- The maximum number of consecutive JWT-related request failures the SDK should allow before giving up, Defaults to 10.
- The interval between each JWT refresh attempt. Defaults to 6 seconds.
- A backoff strategy: linear or exponential. Defaults to linear.
-
You manually pause JWT refresh attempts by calling
IterableAPI.pauseAuthRetries(true)
Changed
onAuthFailure(_ authFailure: AuthFailure)
replacesonTokenRegistrationFailed(_ reason: String?)
. If you've implementedonTokenRegistrationFailed
, you'll need to update your application code.
6.5.4
6.5.3
6.5.2
Fixed
- The Privacy Manifest has been relocated to the resources folder within the SDK. This adjustment facilitates the inclusion of the SDK's privacy manifest in the generation process.
- Resolved a bug where a scheduled authentication token refresh would occur even if the user had logged out in the interim.
Changed
- Improved the Out Of The Box (OOTB) Embedded CardView image content view by setting it to aspect fill. This change ensures a consistent appearance across web, iOS, and Android platforms.
6.5.1
Added
- iOS SDK now includes a new privacy policy file indicating SDK's usage of user data
Fixed
- Fixed an issue where AuthManager's onTokenRequested would get called without user logged in
- Updates logic for notificationsEnabled flag to be more inclusive in case of failures for fetching the current settings
6.5.0
Added
- Introduces support for embedded messaging: an eligibility–based, personalized messages sent from Iterable to your mobile and web apps, which can display them inline, using native interface components
- To display embedded messages, you can use customizable, out-of-the-box components provided by the SDK (cards, notifications, banners), or you can build fully custom components of your own design.
- To learn more, read Embedded Messages with Iterable's iOS SDK.
Changed
IterableConfig
is updated with anenableEmbeddedMessaging
flag that needs to be set to true to allow use of embedded messaging functionality