6.4.6

Fixed

• Added Objective-C access to IterableInboxViewController and IterableInboxNavigationViewController

6.4.5

Added

• This release makes offline events processing available to all Iterable customers who'd like to use it — just ask your customer success manager to enable it for your account. Offline events processing saves a local copy of events triggered in your app while the device is offline (up to 1000 events). When a connection is re-established and your app is in the foreground, the events will be sent to Iterable. For more information, read Offline events processing.

6.4.4

Fixed

• Core data issues.

6.4.3

Added

• Retry request on JWT token obtained.

Fixed

• Core data multithreading issue.
• Update email with JWT token.

6.4.2

Added

• Added support for apps built using Mac Catalyst.
  ​

Fixed

• Fixed a couple of problems related to Swift Package Manager and the creation of release builds and simulator artifacts.
• Fixed a problem with the SDK’s Carthage integration.
• Fixed a problem that prevented the SDK from properly tracking inbox sessions when a mobile inbox is displayed in popup mode.
• In-app delete events are now correctly associated with inbox session IDs.
• Fixed some problems in a script that generates XCFramework binaries.

6.4.1

Fixed

• Fix archiving issue. There was an issue when archiving for projects with deployment target set to iOS 10. This release fixes the issue.

6.4.0

Fixed

• Prevented in-app messages from executing any JavaScript code included in their
  HTML templates.

Changed

• Removed support for iOS 9.

Added

• Added an allowedProtocols field to the IterableConfig class.

  Use this array to declare the specific URL protocols that the SDK can expect to see
  on incoming links (and that it should therefore handle). Doing this will prevent the
  SDK from opening links that use unexpected URL protocols.

  For example, this code allows the SDK to handle http and custom links:

  Swift

  let config = IterableConfig()
  config.allowedProtocols = ["http", "custom"]
  IterableAPI.initialize(apiKey: "<YOUR_API_KEY>", launchOptions: launchOptions, config: config)

  Objective-C

  IterableConfig *config = [[IterableConfig alloc] init];
  config allowedProtocols = @["http", "custom"];
  [IterableAPI initializeWithApiKey:@"<YOUR_API_KEY>" launchOptions:launchOptions config:config]

  Iterable's iOS SDK handles https, action, itbl, and iterable links,
  regardless of the contents of this array. However, you must explicitly declare any
  other types of URL protocols you'd like the SDK to handle (otherwise, the SDK won't
  open them in the web browser or as deep links).

6.3.4

Fixed

• When syncing in-app queues, new messages that already have read set to true will not spawn an InAppDelivery event
• Fixed the alignment of the no messages title on the inbox empty state

Changed

• Wrapped various app extension unsafe classes for Xcode 13 compatibility

Added

• Added ability to not show the unread count badge

6.3.3

6.3.3

Changed

• CocoaPods targets adding this SDK do not require use_frameworks! anymore

Fixed

• Inline comments will not show anymore warnings in Objective-C projects

6.3.2

Added

• updateCart has been added to the SDK
• dataFields have been added as a field to CommerceItem

Removed

• The following calls that were previously marked as deprecated have been removed:
  • IterableAPI.track(inAppOpen messageId: String)
  • IterableAPI.track(inAppClick messageId: String, buttonURL: String)
  • IterableAPI.inAppConsume(messageId: String)
  • IterableAPI.getAndTrack(deeplink webpageURL: URL, callbackBlock: @escaping ITEActionBlock)
  • IterableAPI.showSystemNotification(withTitle title: String, body: String, button: String?, callbackBlock: ITEActionBlock?)
  • IterableAPI.showSystemNotification(withTitle title: String, body: String, buttonLeft: String?, buttonRight: String?, callbackBlock: ITEActionBlock?)