3.1.0-beta2

⚠ IMPORTANT

• Please talk to your Iterable Customer Success Manager if you want to try the beta version of the SDK, as we'll need to enable certain settings on the server for it to work as expected.

Terms of Service

• This beta SDK is subject to Iterable's Beta SDK Terms of Service.

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.

• Custom in-app JSON payload has been moved from IterableInAppMessage.Content.payload to IterableInAppMessage.customPayload

• 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.
  • itbl:// URL scheme is now reserved for actions handled by the SDK (i.e. future versions of the SDK may define itbl://delete as an action to delete the in-app message)
  • 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

Fixed

• Fixed the URL parameter in inAppClick event

More Information

• Please see the 3.1.0-beta2 README file.
  • Specifically, take a look at the Migrating in-app messages from the previous version of the SDK section for information about how to update your app to work with this SDK.

3.0.8

3.0.8

Added

• Added an option to specify notification channel name via manifest metadata (iterable_notification_channel_name)
• Added support for color resource references in iterable_notification_color manifest metadata parameter

Changed

• updateEmail can now be used if the user is identified with userId
• Connection timeout is now 3 seconds

Fixed

• Fixed a NullPointerException when the app has a plain-text label in AndroidManifest.xml instead of a string resource reference

3.1.0-beta1

⚠ IMPORTANT

• Please talk to your Iterable Customer Success Manager if you want to try the beta version of the SDK, as we'll need to enable certain settings on the server for it to work as expected.

Terms of Service

• This beta SDK is subject to Iterable's Beta SDK Terms of Service.

Added

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
• More information:
  • 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

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

Removed

• BREAKING CHANGE: spawnInAppNotification has been removed. Please refer to the in-app migration guide.

More information

• Please see the 3.1.0-beta1 README file.
  • Specifically, take a look at the Migrating in-app messages from the previous version of the SDK section for information about how to update your app to work with this SDK.

3.0.7

3.0.7

Added

• Added updateEmail method with success & failure callbacks

3.0.6

3.0.6

Added

• Added public methods to IterableFirebaseMessagingService and IterableFirebaseInstanceIDService that can be called from a custom FirebaseMessagingService subclass

3.0.5

3.0.5

Added

• Added a new field to IterableConfig - logLevel - to specify the log level for Iterable SDK log messages

Changed

• The SDK now uses preferUserId flag to create a user by userId instead of the deprecated createUserForUserId API

Fixed

• The SDK now catches any RuntimeExceptions that may sometimes happen when calling getAdvertisingIdInfo
• registerDeviceToken and disableToken now use the email/userId that was set at the time of the call, to handle login/logout correctly

3.0.4

3.0.4

Added

• Added support for user registration with userId. The SDK will now create a new user for userId if it does not exist before registering the device on the user's profile.

3.0.3

3.0.3

Added

• Added new device fields (Iterable SDK version, app version, app package name) to registerDeviceToken call
• Deferred Deep Linking support

Fixed

• Fixed a NullPointerException when an in-app was resized after being dismissed

3.0.2

3.0.2

Added

• The SDK now registers the token when a new email/userId is set and disables the old device if email/userId was previously set and then changed. This can be disabled by setting autoPushRegistration to false in IterableConfig.

Fixed

• Fixed a NullPointerException when SDK isn't initialized in Application#onCreate and the app is opened from a push notification

3.0.1

3.0.1

Released on 2018-08-10

Fixed

• The new email is now persisted when updateEmail is called
• SDK now ensures that only one in-app message can be shown at a time