v4.0.0

What's New?

• ✨ (#363) The events module in the SDK has been rewritten in Kotlin for better performance and improved stability.

Full Changelog: v3.5.1...v4.0.0

v3.5.1

What's new?

• 🐛 (#362) Fixed a bug that caused the timestamp (ISO8601) to created_at (Epoch) conversion to error out when processing the payload received from the in-app API.

v3.5.0

What's new?

• 🐛 (#354) Sending explicit intents in internal broadcasts to support Android 14 (API Level 34) or higher.

• 🐛 (#358) Optimised performance by fixing a UI lag issue that was introduced in v3.4.6 of the library.

• ✨ (#357) We've improved the security of stored user information by using EncryptedSharedPreferences. To enable this feature, set the saveUserInfoAsEncrypted flag to true in the configuration while initializing the SDK.

  configuration.setSaveUserInfoAsEncrypted(true);

  • WARNING: The preference file should not be backed up with Auto Backup. When restoring the file it is likely the key used to encrypt it will no longer be present. You should exclude the preference file "com.blueshift.encrypted.preferences" from backup using backup rules.
  • WARNING: Once the encryption is enabled, we can not go back and use the SharedPreference implementation with an app update.
  • EncryptedSharedPreferences requires a minimum SDK version of 23. As a result, the library's minSdkVersion has been bumped to 23.

• ✨ (#360) We have disabled the automatic identify events based on the changes in the email address. The developer now has to send an identify event when the user's email address changes.

• ⚙️ (#356) Development Tooling Updates

  • Gradle version to 8.6
  • Android Gradle Plugin (AGP) version to 8.4.0
  • Kotlin version to 1.9.23
  • targetSdkVersion to 34
  • Gradle script for publishing library to support AGP 8.4.0

v3.4.6

What's new?

• ✨ (#348) Dedicated events to track app installs and app updates

⚠️ Warning: During the Blueshift Android SDK integration, if you have followed the step Install Referrer Tracking (optional), then you must remove the receiver you added as part of that step. Otherwise, starting with this version of the SDK, you might see duplicate app_install events when the app is installed from a referrer URL, resulting in data discrepancies.

v3.4.5

What's new?

• ✨ (#351) Added execution key as part of track API calls for in-app messages & push notifications

v3.4.4

What's new?

• ✨ (#347) Added big-image preview on expandable notifications
• 🐛 (#349) Added missing delivered event for the in-app messages pulled from the inbox API
• ⚙️ (#346) Remove the code that handles category-based deep links

v3.4.3

What's new?

• ✨ (#343) Added country_code and language_code to the event attributes.
• ✨ (#341) Ability to open push and in-app links (URLs) in external apps/browsers. (To know more, email us at support@blueshift.com.)
• ✨ (#340) Included the adapter_uuid as bsft_aaid in the campaign stats API calls.
• 🐛 (#338) Avoid app crashes due to missing component errors for JobScheduler.
• 🐛 (#337) Avoid holding monitors/mutex while waiting for HTTP API calls.
• ⚙️ (#342) Moved package from AndroidManifest.xml to build.gradle as namespace.

v3.4.2

Hotfix Release

What's new?

• Avoiding an NPE caused when the in-app API returns null as a response.

v3.4.1

What's new?

• The BlueshiftInboxManager.displayInboxMessage() method will now mark the in-app message display as user-initiated.
• Added a new helper method (InAppManager.getRegisteredScreenName()) to get the name of the current screen registered for showing in-app messages.
• Added more helper methods for the cross-platform plugins to communicate with the mobile inbox.

v3.4.0

What's New

• Mobile Inbox is here 🎉 (To know more about the feature, please check our documentation or reach out to us via support@blueshift.com)