3.6.0-beta1

• This release includes initial support for Anonymous user activation, a feature that allows marketers to convert valuable visitors into customers. With this feature, the SDK can:
  • Fetch anonymous profile creation criteria from your Iterable project, and then automatically create Iterable user profiles for anonymous users who meet these criteria.
  • Save information about a user's previous interactions with your application to their anonymous profile, after it's created.
  • Display personalized messages for anonymous users (in-app, push, and embedded messages).
  • Merge anonymous profiles into an existing, known user profiles (when needed).
• Anonymous user activation is currently in private beta. If you'd like to learn more about it or discuss using it, talk to your Iterable customer success manager (who can also provide detailed documentation).

3.5.3

Fixed

• Fixed an issue where the SDK would crash if the IterableInAppMessage object was null when consuming an in-app message.

Changed

• The SDK now provides more insight into JWT refresh failures, to help you take appropriate action in your application code. Now, when a JWT refresh fails (for any of various reasons), the SDK calls onAuthFailure(AuthFailure authFailure) on the IterableAuthHandler instance you provided to the SDK at initialization. The AuthFailure object provides more information about the failure.
• onAuthFailure(AuthFailure authFailure) replaces onTokenRegistrationFailed(Throwable object), so if you've implemented that method you'll need to update your application code.
• For more information, see the documentation for Iterable's Android SDK.

3.5.2

Added

• Introducing a new method setAuthRetryPolicy in IterableConfig to set the retry policy for JWT token refresh.
• You can now use method - pauseAuthRetries(boolean pauseRetry) to pause or resume the JWT token refresh retries.
• trackPurchase method now accepts attributionInfo parameter to track purchase with attribution information.

Fixed

• Embedded manager listeners are active only if feature is enabled

3.5.1

Fixed

• Embedded manager syncs messages as soon as user logs in
• Fixed a bug to prevent app crashes due to malformed authTokens
• Fixes a bug where push notifications opens would lead to app crashes
• Fixes a bug where crashes would occur due to SDK not being initialized

Changed

• Updates Glide library in embedded message OOTB views to version 4.16.0

3.5.0

Added

• introduces support for embedded messaging: an eligibility–based, personalized messages sent from Iterable to your mobile and web apps, which can display them inline, using native interface components.
• To display embedded messages, you can use customizable, out-of-the-box components provided by the SDK (cards, notifications, banners), or you can build fully custom components of your own design.
• To learn more, read Embedded Messages with Iterable's Android SDK.

Changed

• IterableConfig is updated with an enableEmbeddedMessaging flag that needs to be set to true to allow use of embedded messaging functionality

3.5.0-beta1

Merge pull request #663 from Iterable/evan/MOB-7312-prepare-for-3.5.0…

3.4.17

Added

• when JWT is invalid, IterableAuthManager is updated to fetch and store a new JWT token locally
• IterableRequestTask now has a retry mechanism that fetches a new JWT token and retries the request if JWT is invalid
• retries are capped at a max of 5

3.4.16

Fixed

• SDK now handles null scenarios preventing crashes when IterableEncryptedSharedPreference creation fails.
• Updated crypto library to version 1.1.0-alpha06.
  1.1.0-alpha05 solves a race condition during creation process.
• Fixes #631 and #616

3.4.15

Added

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:

Java

IterableConfig config = new IterableConfig.Builder()
  // ... other configuration options ...
  .setDataRegion(IterableDataRegion.EU)
  .build();
IterableApi.initialize(context, "<YOUR_API_KEY>", config);

Kotlin

val configBuilder = IterableConfig.Builder()
   // ... other configuration options ...
  .setDataRegion(IterableDataRegion.EU)
  .build();
IterableApi.initialize(context, "<YOUR_API_KEY>", config);

Fixed

• Addressed React Native SDK push notification deep linking issues where the app would restart instead of resuming the last activity upon being backgrounded.
• Resolves an additional push notification problem 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)

3.4.14

Added

• IterableInAppManager.setRead now accepts IterableHelper.FailureHandler failureHandler

Fixed

• Fixes an issue where IterableInAppManager.removeMessage caused build failure in React Native SDK pointing to legacy method calls.
• Fixes an issue where custom action handlers were not invoked when tapping on push notification when the app is in background.