3.1.0

Added

BREAKING CHANGES

The in-app messaging implementation has been significantly improved:

• The SDK now maintains a local queue and keep it in sync with the server-side queue automatically
• Iterable servers now notify apps via silent push messages whenever the in-app message queue is updated
• In-app messages are shown by default whenever they arrive

Check the In-app messages documentation for more details.

Please refer to the Migration guide if you've been using in-app messages in your app and updating a newer version of the SDK.

Changed

• BREAKING CHANGE: Added IterableContext argument to IterableCustomActionHandler

  The new method signature is:

  boolean handleIterableCustomAction(IterableAction action, IterableActionContext actionContext)

  actionContext can be used to determine where the call is calling from - push message, in-app message, or a deep link.

• The SDK now sets notificationsEnabled flag on the device to indicate whether notifications are enabled for the app

• Changes to in-app links:

  • action:// URL scheme is now reserved for app-specific custom actions.
    When a user clicks on a link with href = action://myCustomAction, the SDK calls IterableCustomActionHandler.handleIterableCustomAction with action type set to myCustomAction.
  • iterable:// URL scheme is now reserved for actions handled by the SDK (i.e. future versions of the SDK may define iterable://delete as an action to delete the in-app message)
  • itbl:// links will keep working as custom actions (similar to action:// URLs) for backwards compatibility, but itbl:// namespace is deprecated in favor of action://.
  • Migration: if you've been using itbl:// links in the past, please update your templates with action:// instead

• Connect timeout for deeplink resolution is now 3 seconds

Removed

• spawnInAppNotification has been removed. Please refer to the in-app migration guide (above)

Fixed

• Fixed the URL parameter in inAppClick event