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

[dependabot]

Bumps com.iterable:iterableapi from 3.4.9 to 3.4.11.

Release notes

Sourced from com.iterable:iterableapi's releases.

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.

3.4.10

Warning Some users have reported crashes in apps built with version 3.4.10 of Iterable's Android SDK. We're investigating the issue. In the meantime, please test thoroughly. If you see crashes, revert to version 3.4.9.

This release includes support for encrypting some data at rest, and an option to store in-app messages in memory.

Encrypted data

In Android apps with minSdkVersion 23 or higher (Android 6.0) Iterable's Android SDK now encrypts the following fields when storing them at rest:

• email — The user's email address.
• userId — The user's ID.
• authToken — The JWT used to authenticate the user with Iterable's API.

(Note that Iterable's Android SDK does not store the last push payload at

... (truncated)

Changelog

Sourced from com.iterable:iterableapi's changelog.

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.

3.4.10

This release includes support for encrypting some data at rest, and an option to store in-app messages in memory.

Encrypted data

In Android apps with minSdkVersion 23 or higher (Android 6.0) Iterable's Android SDK now encrypts the following fields when storing them at rest:

• email — The user's email address.
• userId — The user's ID.
• authToken — The JWT used to authenticate the user with Iterable's API.

(Note that Iterable's Android SDK does not store the last push payload at rest—before or after this update.)

For more information about this encryption in Android, examine the source code for Iterable's Android SDK: IterableKeychain.

... (truncated)

Commits

• be29cfd Merge pull request #536 from Iterable/MOB-5894-Release-3.4.11
• 1e235ab Removed line breaks as suggested
• 0179df9 Revised changelog
• ec066e3 [MOB - 5894] - Prepare for release
• fc559c2 Merge branch 'master' into Encryption-Fix-New
• 1fa276e Merge pull request #535 from Iterable/MOB-5893-Encryption-Rebase-fix
• 4aea9b2 Merge pull request #534 from Iterable/MOB-5874-authToken-refresh-when-null
• ecaf2bd Merge pull request #533 from Iterable/MOB-5873-Email-UserID-AuthToken-Getters
• cb0e4c3 [MOB - 5874] - Schedule auth refresh when auth null
• fb38707 [MOB - 5873] - Public getters for Email UserID and Auth
• 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)

[dependabot]

Superseded by #77.