1.3.0

Added

This version of the SDK provides a mobile inbox implementation. To learn more, read Using a Mobile Inbox with Iterable's React Native SDK.

1.2.3

Updated to point to Android SDK 3.4.5 and iOS SDK 6.4.2

1.2.2

Changed

• Dependency update. The SDK now relies on version 3.4.4 of Iterable’s Android SDK.

1.2.1

This release points to the same versions of Iterable’s iOS and Android SDKs as version 1.2.0.

Changed

• Updated the podspec, setting the minimum deployment target to iOS 10.0. (Thank you, @jgrana!)

1.2.0

This version of the SDK replaces for version 1.1.4, which has been removed to avoid version number confusion.

Added

• Added the allowedProtocols field to IterableConfig.

  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 tel links:

  const config = new IterableConfig()
  config.allowedProtocols = ["tel", "http"]

  By default, the 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.

Changed

• Dependency updates. This SDK now relies on:
  • Version 3.4.3 of Iterable’s Android SDK (which includes fixes from version 3.4.1 to handle Android 12's notification trampoline restrictions).
  • Version 6.4.1 of Iterable's iOS SDK.

1.1.3

• Points to Android SDK 3.3.8 and Swift SDK 6.3.4
• Android now supports Deep Links via React's Linking Library
• trackEvent now does not crash in the Android bridge

1.1.2

• Points to iOS SDK 6.3.3 and Android SDK 3.3.5
• Fixes the bug on Android where in-app messages were not synced on the first launch

1.1.1

• Updated iOS and Android SDK bindings to 6.3.2 and 3.3.4 respectively; updateCart has been added as an SDK call, and IterableCommerceItem has been updated to have dataFields as an optional field.
• Fixed setAutoDisplayPaused not being properly threaded (thanks, @prsauer!)

1.1.0

Added

• Offline events processing

  This feature 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.

  Offline events processing is off by default, and we're rolling it out on a customer-by-customer basis. After you start using this version of the SDK, we'll send you a message before we enable the feature on your account (unfortunately, we can't give you an exact timeline for when this will happen). If you have any questions, talk to your Iterable customer success manager.

  To use this feature, you must follow the SDK upgrade instructions.

Updated

• New properties on the IterableCommerceItem class

  The IterableCommerceItem class (which you can pass to the trackPurchase method on the Iterable class) now includes additional properties (all optional):

  • sku (string) - The item's SKU
  • description (string) - A description of the item
  • url (string) - A URL associated with the item
  • imageUrl (string) - A URL that points to an image of the item
  • categories (string) - Categories to associate with the item

Upgrade instructions for version 1.1.0

To use this version of Iterable's React Native SDK, you'll need to update your native Android application's Application class:

• Add this import:

  import com.iterable.iterableapi.IterableApi;

• At the end of the onCreate method, add this line of code:

  IterableApi.setContext(this);

1.0.28

• Points to Android SDK version 3.2.14