6.6.0-beta3

• This release includes fixes for the Anonymous user activation private beta:
  • Criteria is now fetched on foregrounding the app by default. This feature can be turned off setting enableForegroundCriteriaFetch flag to false.
  • anonymous user ids are only generated once when multiple track calls are made.
• 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.11

Fixed

• Added missing constructor for IterableAPIMobileFrameworkInfo

6.5.10

Added

• Added mobileFrameworkInfo configuration option to IterableConfig to identify the mobile framework (Flutter, React Native, or Native) being used with the SDK.

Fixed

• Fixed notification tracking bug that prevents SDK from receiving push notifications when system notification settings are turned off.

6.5.9 (Deprecated)

Deprecation notice

This version of the SDK is deprecated. Do not use it.

This version of Iterable's iOS SDK include changes to help keep a user's Iterable profile in sync with their physical device's push settings for your app (by keeping the device's notificationsEnabled flag up-to-date in Iterable).

However, it also includes a bug that can prevent the SDK from receiving silent push notifications, which in turn can prevent end users from receiving expected in-app and embedded messages.

If you've started building on this version of the SDK, please roll back to a previous version while we work on a fix.

Added

• Support for JSON-only in-app messages. JSON-only messages are now handled by the onNew handler and consumed after retrieval.
• Enhanced notification state tracking, to align with system notification permissions changes.

Changed

• Reorganized files and updated documentation URL in podspec.

6.5.8

Fixed

• Fixed incorrect tracking of pushOpen for push notifications with Wake App enabled. Tracking now happens only when users tap to open the app.
• Fixed the default notificationsEnabled value returned when autoPushRegistration is set to false.

Changed

• Updated repository name on Fastline script and podspec files.
• Comments out outdated tests that need to be revisited.
• Updated sample app to use generic URLs.

6.5.8-beta1

Added

• introduces ThreadSafeOrderedDictionary which is a wrapper around the OrderedDictionary to ensure thread safety. Thanks to @Rspoon3

Fixed

• Prevents crashes relating to the Core Data's persistent store failing to load. Thanks to @bfahey :)
• Fixed incorrect tracking of pushOpen for push notifications with Wake App enabled. Tracking now happens only when users tap to open the app.

6.6.0-beta2

• This release fixes beta1 release which was released from the wrong branch.

6.5.7

Fixed

• Fixed deeplink re-routing issue where delegate would only return false value. Thanks to @scottasoutherland :)

6.5.6

Fixed

• Fixed an issue where push notification were not being delivered in iOS 18 beta Sandbox builds.

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 the IterableAuthDelegate instance you provided to the SDK at initialization. The AuthFailure object provides more information about the failure. This method replaces onTokenRegistrationFailed(_ reason: String?).

• To set a retry policy for JWT refreshes, you can set the retryPolicy property on IterableConfig to a RetryPolicy 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) replaces onTokenRegistrationFailed(_ reason: String?). If you've implemented onTokenRegistrationFailed, you'll need to update your application code.