chore: bump com.iterable:iterableapi from 3.4.9 to 3.4.14

[dependabot]

Bumps com.iterable:iterableapi from 3.4.9 to 3.4.14.

Release notes

Sourced from com.iterable:iterableapi's releases.

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.

3.4.13

Added

• IterableInAppManager.setRead now accepts IterableHelper.SuccessHandler successHandler.
• IterableApi.inAppConsume now accepts IterableHelper.SuccessHandler successHandler and IterableHelper.FailureHandler failureHandler.

3.4.12

Added

• setEmail and setUserId now accepts IterableHelper.SuccessHandler successHandler and IterableHelper.FailureHandler failureHandler.

Changed

• OTT devices (FireTV) will now register as OTT device instead of Android under user's devices.

3.4.11

Added

• Custom push notification sounds! To play a custom sound for a push notification, add a sound file to your app's res/raw folder and specify that same filename when setting up a template in Iterable.

  Some important notes about custom sounds and notification channels:

  • Android API level 26 introduced notification channels. Every notification must be assigned to a channel.
  • Each custom sound you add to an Iterable template creates a new Android notification channel. The notification channel's name matches the filename of the sound (without its extension).
  • To ensure sensible notification channel names for end users, give friendly names to your sound files. For example, a custom sound file with name Paid.mp3 creates a notification channel called Paid. The end user can see this notification channel name in their device's notification channel settings.
  • Be sure to place the corresponding sound file in your app's res/raw directory.

• To help you access a user's email address, userId, and authToken, the SDK now provides convenience methods: getEmail(), getUserId(), and getAuthToken().

Changed

• Updated the Security library and improved EncryptedSharedPreferences handling.

  To work around a known Android issue that can cause crashes when creating EncryptedSharedPreferences, we've upgraded androidx.security.crypto from version 1.0.0 to 1.1.0-alpha04. When EncryptedSharedPreferences cannot be created, the SDK now uses SharedPreferences (unencrypted).

  If your app requires encryption, you can prevent this fallback to SharedPreferences by setting the encryptionEnforced configuration flag to true. However, if you enable this flag and EncryptedSharedPreferences cannot be created, an exception will be thrown.

• Improved JWT token management. This change addresses an issue where null values could prevent the refresh of a JWT token.

Fixed

• Fixed an issue which could prevent in-app messages from respecting the Position value selected when setting up the template (top / center / bottom / full).

• Fixed crashes that sometimes happened during in-app message animations.

... (truncated)

Changelog

Sourced from com.iterable:iterableapi's changelog.

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.

3.4.13

Added

• IterableInAppManager.setRead now accepts IterableHelper.SuccessHandler successHandler.
• IterableApi.inAppConsume now accepts IterableHelper.SuccessHandler successHandler and IterableHelper.FailureHandler failureHandler.

3.4.12

Added

• setEmail and setUserId now accepts IterableHelper.SuccessHandler successHandler and IterableHelper.FailureHandler failureHandler.

Changed

• OTT devices (FireTV) will now register as OTT device instead of Android under user's devices.

3.4.11

Added

• Custom push notification sounds! To play a custom sound for a push notification, add a sound file to your app's res/raw folder and specify that same filename when setting up a template in Iterable.

  Some important notes about custom sounds and notification channels:

  • Android API level 26 introduced notification channels. Every notification must be assigned to a channel.
  • Each custom sound you add to an Iterable template creates a new Android notification channel. The notification channel's name matches the filename of the sound (without its extension).
  • To ensure sensible notification channel names for end users, give friendly names to your sound files. For example, a custom sound file with name Paid.mp3 creates a notification channel called Paid. The end user can see this notification channel name in their device's notification channel settings.
  • Be sure to place the corresponding sound file in your app's res/raw directory.

• To help you access a user's email address, userId, and authToken, the SDK now provides convenience methods: getEmail(), getUserId(), and getAuthToken().

Changed

• Updated the Security library and improved EncryptedSharedPreferences handling.

  To work around a known Android issue that can cause crashes when creating EncryptedSharedPreferences, we've upgraded androidx.security.crypto from version 1.0.0 to 1.1.0-alpha04. When EncryptedSharedPreferences cannot be created, the SDK now uses SharedPreferences (unencrypted).

  If your app requires encryption, you can prevent this fallback to SharedPreferences by setting the encryptionEnforced configuration flag to true. However, if you enable this flag and EncryptedSharedPreferences cannot be created, an exception will be thrown.

• Improved JWT token management. This change addresses an issue where null values could prevent the refresh of a JWT token.

Fixed

• Fixed an issue which could prevent in-app messages from respecting the Position value selected when setting up the template (top / center / bottom / full).

• Fixed crashes that sometimes happened during in-app message animations.

... (truncated)

Commits

• e094722 [MOB - 6507] - Prepare for 3.4.14 (#596)
• e2981db Merge changes (#594)
• 47b9a9a [MOB - 6372] - Prepare for 3.4.13 (#587)
• a744570 Squashed commit of the following:
• 5fe48a2 [MOB-6223] - Prepare for 3.4.12 (#571)
• 70a66ae Merge branch 'master' into encryption
• 62ac73e [MOB-6055] - [OMNI CG] - Add callbacks to setting email/user id (#570)
• fa121af Merge pull request #532 from amanjayshahomnicg/firetv-updateuser-fix
• e232049 Merge branch 'master' into firetv-updateuser-fix
• 650679e Merge pull request #561 from Iterable/CherryPick-InMemoryStorage-on-Master
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)