Releases: Iterable/iterable-swift-sdk
Releases · Iterable/iterable-swift-sdk
6.2.2
6.2.1
6.2.0
Added
- Moved Mobile Inbox support to GA (no longer in beta), and:
- Added support for various ways to customize the default interface for a mobile inbox
- Added a sample project that demonstrates how to customize the default interface for a mobile inbox
- Added tracking for inbox sessions (when the inbox is visible in the app) and inbox message impressions (when a individual message's item is visible in the mobile inbox message list)
- Added support for Swift Package Manager
Deprecated
Please see each method's source code documentation for details.
IterableAPI.track(inAppOpen messageId: String)
IterableAPI.track(inAppClick messageId: String, buttonURL: String)
6.1.5
Fixed
- Fixed in-apps where display types that were not
fullScreen
were not displaying properly or becoming unresponsive.
6.1.4
6.1.3
- Converted a log message variable to be interpreted as an UTF8 String (thanks, @chunkyguy !)
- Enabled BUILD_LIBRARY_FOR_DISTRIBUTION for better compatibility across development environments
6.2.0-beta1
⚠ IMPORTANT
- This feature must be enabled for your project before you can use it. Please contact your CSM if you want to use this beta version.
- Beta versions of this SDK are subject to Iterable's
Beta Mobile SDK Terms of Service.
Installation
Beta installation instructions
Added
Removed
IterableAPI.spawnInAppNotification(_:)
- In-app messages are automatically shown by SDK now. Please check our migration guide.
IterableAPI.get(inAppMessages:)
- Use
IterableAPI.inAppManager.getMessages()
instead
- Use
Changed
- There is no need to set
IterableConfig.pushIntegrationName
for new projects.
Deprecated
Please see method documentation for details about how to replace them.
IterableAPI.inAppConsume(messageId:)
IterableAPI.showSystemNotification(..)
IterableAPI.getAndTrack(deeplink:callbackBlock:)
6.1.2
Fixed
- Fixed a bug in token to hex conversion code.
6.1.0
Changed
- In this version we have changed the way we use in-app notifications. In-app messages are now being sent asynchronously and your code can control the order and time in which an in-app notification will be shown. There is no need to poll for new in-app messages. Please refer to the in-app messages section of README file for how to use in-app messages. If you are already using in-app messages, please refer to migration guide section of README file.