1.3.17

Fixes

• Points to Android SDK 3.4.16 which points to new crypto library. This should resolve crashes occurring due failure in EncryptedSharedPreferences object creation.

1.3.16

Updates

This release allows you to use projects hosted on Iterable's EU data center. If your project is hosted on Iterable's European data center (EUDC), configure the SDK to use Iterable's EU-based API endpoints:

const config = new IterableConfig();
// ... other configuration options ...
config.dataRegion = IterableDataRegion.EU;
Iterable.initialize('<YOUR_API_KEY>', config);

Fixed

• Addressed push notification deep linking issues on Android where the app would restart instead of resuming the last activity upon being backgrounded.
• Resolves an additional push notification problem on Android wherein the customActionHandler and urlHandler were not being invoked in specific scenarios, as documented in issue #470. (Credit to @tnortman-jabra for the report and the fix)

1.3.15

Updates

• Resolves Android build issues caused in 1.3.14
• Fixes a specific Android issue where custom action handlers were not invoked when tapping on push notification when the app is in background.

1.3.14

Warning
This version causes build failure on Android. Please use 1.3.15 which fixes this issue.

updates

• updates Iterable.setEmail and Iterable.setUserId to take in null parameter type
• fixes Iterable.updateUser on the Android side to merge nested objects in the user profile when mergeNestedObjects is set to true

1.3.13

This release points to new Android release 3.4.11 bringing new features and bug fixes for Android platform

• Custom push notification sounds
• Updated security library
• Fixes for inapp message

1.3.12

Fixed

• This release fixes an integration issue with iOS SDK 6.4.12 regarding the IterableAuthDelegate

1.3.11

This release points to the iOS SDK version 6.4.11, and adjusts the customPayload field data type on IterableInAppMessage to serialize properly.

1.3.10

This release points to the most updated version of the iOS SDK (6.4.10) and also includes several quality improvements such as

• providing descriptive comments to the Iterable.ts and IterableInAppManager.ts file
• adding instructions for implementation to the sample apps
• corrections to several unit tests
• addition of several unit tests
• updating eslint and enforcement of a consistent code style
• updating imports to prevent circular dependency issues
• fixing build.gradle to inherit config values from the parent project

1.3.9

Added

This release of Iterable's React Native SDK makes it possible for iOS apps to store in-app messages in memory, rather than in an unencrypted local file. (Version 1.3.7 added this same support for Android.)

To store in-app messages in memory on both iOS and Android, set useInMemoryStorageForInApps to true:

const config = new IterableConfig();
// ... other configuration options ...
config.useInMemoryStorageForInApps = true;
Iterable.initialize('<YOUR_API_KEY>', config);

When users upgrade to a version of your iOS or Android app that uses this version of the SDK (or higher), and they've enabled in-app memory storage, the local file used for in-app message storage (if it already exists) is deleted. However, no data is lost.

Deprecated

This release deprecates androidSdkUseInMemoryStorageForInApps, which was introduced in version 1.3.7, and replaces it with useInMemoryStorageForInApps. However, for now:

• Android apps store in-app messages in memory if useInMemoryStorageForInApps is true, androidSdkUseInMemoryStorageForInApps is true, or if both are true.

• iOS apps store in-app messages in memory if useInMemoryStorageForInApps is true. androidSdkUseInMemoryStorageForInApps does not affect iOS apps.

When you can, please update your apps to use useInMemoryStorageForInApps instead of androidSdkUseInMemoryStorageForInApps.

1.3.8

DEPRECATED - Please use version 1.3.9 or higher, as 1.3.8 does not contain the intended changes for this release.