3.4.8

Removed

• Removed collection of advertising ID.

Fixed

• Fixed an issue where disableDevice would get called with no device token.

3.4.7

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.

3.4.6

Fixed

• Fixed an issue where configurations would not be loaded. config in IterableApi is now accessed through sharedInstance.

Changed

• trackPushOpen in IterableApi is now public.

3.4.5

Fixed

• Fixed an issue that sometimes prevented in-app messages from displaying.

3.4.4

Fixed

• Fixed a bug that caused in-app messages to always use a top layout (making them display at the top of the screen). This issue was introduced in version 3.4.0 of this SDK. If you’re using versions 3.4.0 - 3.4.3, please upgrade to this version (3.4.4) or later.

3.4.3

Added

• Notification badges and dots can now be explicitly enabled or disabled by setting iterable_notification_badging (in AndroidManifest.xml) to true or false. For more information, check out our support docs.

Fixed

• Fixed a device registration failure impacting users in JWT-enabled projects.
• Fixed an issue related to the app switcher and deep links in push notifications.

3.4.2

Fixed

• Fixed a regression related to the immutability of pending intents, which caused issues on Android 12. (Thanks, @scaires!)

3.4.1

Fixed

• Push notification handling now accounts for Android 12's notification trampoline restrictions.

3.4.0

Breaking changes

• On IterableApi, changed two static methods—handleAppLink and getAndTrackDeepLink—to instance methods. To call them, first grab an instance of IterableApi by calling IterableApi.getInstance(). For example, IterableApi.getInstance().handleAppLink(...).

Added

• Added the 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:

  Java

  IterableConfig.Builder configBuilder = new IterableConfig.Builder()
    .setAllowedProtocols(new String[]{"http", "custom"});
  IterableApi.initialize(context, "<YOUR_API_KEY>", config);

  Kotlin

  val configBuilder = IterableConfig.Builder()
    .setAllowedProtocols(arrayOf("http","custom"))
  IterableApi.initialize(context, "<YOUR_API_KEY>", configBuilder.build());

  Iterable's Android 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).

Fixed

• Prevented in-app messages from executing JavaScript code included in their HTML templates.
• Prevented web views from accessing local files.

3.3.9

Changed

• Auth keys and API keys will no more be logged in Android Logcat for security reasons.

Fixed

• Crash on closing system dialog is now addressed for Android 12+.