3.3.2

Added

• Added a new static method - setContext to IterableAPI. Use this method in your ReactNative project to pass context to IterableSDK from Application - onCreate method.

3.3.1

Added

• The following properties have been added to the CommerceItem class:

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

  Set these values on CommerceItem objects passed to the IterableApi.trackPurchase method.

Changed

• To resolve a breaking change introduced in Firebase Cloud Messaging version 22.0.0, version 3.3.1 of Iterable's Android SDK bumps the minimum required version of its Firebase Android dependency to 20.3.0.

  If upgrading to version 3.3.1 causes your app to crash on launch, or your build to fail, add the following lines to your app's build.gradle file:

  android {
      ...
      compileOptions {
          sourceCompatibility JavaVersion.VERSION_1_8
          targetCompatibility JavaVersion.VERSION_1_8
      }
      ...
  }

• Updated minimum version for firebase-messaging to 20.3.0 to use FirebaseMessaging.getToken() instead of deprecated FirebaseInstanceId.getToken().

• Notifications will now show timestamp.

3.3.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.

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

Removed

• Removed legacyGCMSenderId from IterableConfig.
• Removed deprecated functions spawnInAppNotification and redirected getInAppMessages to be called from IterableInAppManager.

Changed

• Updated minimum version for firebase-messaging to 19.0.0.
• Added dependency on Kotlin standard library.

3.2.14

3.2.14

Fixed

• Non-silent inbox messages will now properly account for the read state.

3.2.13

Added

• In-app message prioritization - Ordering the display of in-app messages based on a priority you select in Iterable when creating in-app campaigns

3.3.0-beta3

Added

• Support for the display of a custom message (title and body) in an empty mobile inbox.
  For more details, see Customizing Mobile Inbox on Android

• Support for syncing in-app message read state across multiple devices:

  • When the SDK fetches in-app messages from Iterable, it examines each message's read field to determine if it has already been read.
  • The SDK's default implementation no longer automatically displays in-app messages that have already been seen on another device (even if those messages were not configured to go directly to the inbox).

  If you'd like to try out these beta features, talk with your Iterable customer success manager.

3.2.12

• Support for the display of a custom message (title and body) in an empty mobile inbox.
  For more details, see Customizing Mobile Inbox on Android
• Support for syncing in-app message read state across multiple devices:
  • When the SDK fetches in-app messages from Iterable, it examines each message's read field to determine if it has already been read.
  • The SDK's default implementation no longer automatically displays in-app messages that have already been seen on another device (even if those messages were not configured to go directly to the inbox).

3.2.11

Changed

• Changed the timeout for GET calls (/inApp/getMessages in particular) from 3 to 10 seconds.

Fixed

• Fixed a crash that would sometimes happen when dismissing an in-app message while the app is in background.

3.3.0-beta1

Added

• This beta SDK release includes support for two new Iterable features (both of which are in beta):

  • Offline events processing - Capturing engagement events when a device is offline and sending them to Iterable when a network connection is reestablished
  • In-app message prioritization - Ordering the display of in-app messages based on a priority you select in Iterable when creating in-app campaigns

  If you'd like to try out these beta features, talk with your Iterable customer success manager.

3.2.10

Fixed

• Fixed Firebase check to work without a Firebase database URL in google-services.json that may not be present in some recently created Firebase projects.