3.8.0

What's changed

Config

• Introduced clientId as a clearer alternative to the now-deprecated hardwareId; both refer to the same property, and while we encourage using clientId, this is not a breaking change as hardwareId remains available for backward compatibility.

Geofence

• Improved support for Roboelectric tests.

• What's fixed

ChangeApplicationCode

• Fix an issue where changeApplicationCode was not working properly with anonymous contacts.

Push

• Fix an issue where on Android API level 35 clicking on the push message would not start the application.

3.7.11

What's fixed

Emarsys SDK

• Fix a crash on Android 12 during the initialization of the SDK

3.7.10

What's fixed

Emarsys SDK

• Fix automatic contact setting during SDK initialization
• Fix activity lifecycle tracking to track app:start event

3.7.9

What's fixed

Emarsys SDK

• Fix an issue when encrypting nullable Strings

3.7.8

Known Issue

An issue has been found with the handling of nullable strings in the new encryption solution, please use 3.7.9 instead!

What's changed

Emarsys SDK

• Prevent some unnecessary network calls in some cases
• Drop usage of the deprecated Jetpack security crypto library to encrypt data in shared preferences

What's fixed

Geofence

• Geofence now works after the application has been closed.

3.7.7

What's fixed

Geofence

• Fixed a compatibility issue with Android 14 (API level 34) and above.

In-App

• Fixed an edge-case when the Activity was not found for the given In-App message to display.

3.7.6

What's changed

Emarsys

• Changed error handling in database operations to receive more detailed information.

3.7.5

What's fixed

Push

• Fixed issue where the message id was not passed to the event handler.

• Fixed issue where the custom field was not passed to the event handler.

• Inapp

• Fixed issue where the showing of the inapp during an activity lifecycle transition caused a crash.

• Emarsys

• Fixed issue where an image handling error could cause a crash.

3.7.4

What's fixed

Push

• Fixed issue where the Default Tap Actions' payload was not mapped correctly.

3.7.3

What's fixed

Push

• Fixed issue where rootParams were not mapped from RemoteMessages