Releases: Iterable/iterable-swift-sdk
Releases · Iterable/iterable-swift-sdk
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.
6.5.12
- Made
IterableDataRegion
an@objc
class for better Objective-C compatibility. - Improved robustness of the SDK by adding more internal initialization checks before executing certain operations.
- Enhanced thread safety for embedded message data handling, leading to increased stability.
- Improved
IterableEmbeddedView
by makingimgView
andcardImageView
optional, leading to more robust view handling, particularly for.card
and.banner
types when images might not be present. - Minor refinements to authentication and token refresh logic for increased stability.
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
6.5.10
Added
- Added
mobileFrameworkInfo
configuration option toIterableConfig
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 whenautoPushRegistration
is set tofalse
.
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 :)