What's changed

Emarsys SDK

• Proguard rule added for Emarsys SDK to prevent issues when host application uses R8# What's
  changed

Emarsys SDK

• Prevent requests without an application code from being sent and return an
  InvalidArgumentException instead through the CompletionListener

What's changed

Emarsys SDK

• Kotlin updated to 1.9.0
• jvmToolchain updated to Java 17

What's fixed

In-App

• The SDK could crash in some rare cases during WebView creation

What's new

Huawei

• Followed up some major Huawei dependency updates, as we always try to keep our dependencies up-to-date

For now Huawei Toolkit still does not support Android 12. Updates about this issue: here

This crashes the application when running it on Android 12+, and Emarsys-Huawei is integrated into the application. No harm done when running on Huawei devices, or on devices below Android 12.

What's new

Geofence

• If it's enabled, now the SDK sends an event (geofence EXIT) also when the mobile device leaves the area of a configured geofence.

Note: The Geofence feature is still in pilot phase!

What's fixed

Dependencies

• Updated some minor dependencies. Related commit is here.

Threading

• There were some edge-cases when LifecycleObserver addObserver were called on a thread other than the UI thread.
• It caused a crash, but only in the SDK, it could have caused some issues in the session reporting/handling. Now it's always added on the UI thread.

Inline In-App

• Fixed a crash, which happened when an Inline In-App were displayed before finishing the Emarsys.setup().

Important Notes

• Please keep in mind that after 2021.08.06 we will drop support of Android versions below Nougat (API level 24). For more details please visit https://github.com/emartech/android-emarsys-sdk/wiki/FAQ#when-do-we-increase-the-minimum-android-version-required-for-the-sdk
• Deprecated methods are going to be removed in our next major release (3.0.0)
• Kotlin version will be updated from 1.4.32 -> 1.5.0 in the next minor release!

What's fixed

• Transitive dependencies has been added to the release.

Important Notes

• Deprecated methods are going to be removed in our next major release (3.0.0)

What's new

On Event Action

• Emarsys SDK now supports silent On Event Action

What's changed

Push

• Thumbnail notification style is now extendable

Important Notes

• Deprecated methods are going to be removed in our next major release (3.0.0)

What's new

Testing

• Added support for Espresso Idling resources.

Upgraded Dependencies

• Kotlin version upgraded to 1.4 FAQ
• Firebase Core version upgraded to 18.0.0
• Firebase Messaging version upgraded to 21.0.0

What's fixed

Config

• Application code change won't fail, if push token isn't set.

Important Notes

• Deprecated methods are going to be removed in our next major release (3.0.0)

What's changed

Predict

• Modified Product, customFields now use Map<String,String?> map instead of Map<String,String>. This way the use case when the Product Catalog contains no value for a given custom field, therefore the field arrives containing a null value in the recommendation, can be handled.

What's new

Predict - availability zones

• Added support for availability zones in Predict recommendations.

What's fixed

In-App

• Deprecated EventHandler now provides a Context instead of null

Android 11

• Fixed usage of resolveActivity() to avoid malfunctioning on devices using API level 30 due to some changes on package visibilities on Android 11

Important Notes

• Deprecated methods are going to be removed in our next major release (3.0.0)
• Minimum API level is now 21 instead of 19. For more details please visit https://github.com/emartech/android-emarsys-sdk/wiki/FAQ#when-do-we-increase-the-minimum-android-version-required-for-the-sdk

What's changed

User Centric Message Inbox

• added campaignId and collapseId, changed TTL to expiresAt in Message.kt

What's new

User Centric Message Inbox

• added predefined tags to user centric Message Inbox. See InboxTag.kt
• enabled anonim contact message fetch so Message Inbox now works without calling setContact first

What's fixed

Push Notifications

• the title of push messages using the MESSAGE style is now correctly set to the value received in the push message

In-App

• now sending In-App metrics, like loading-time, on-screen-time to the Emarsys Mobile Engage backend
• fixed In-line In-App to fill it's container

Important Notes

• Deprecated methods are going to be removed in our next major release (3.0.0)
• Please keep in mind that from the next release we will drop support of Android KitKat (API level 19). For more details please visit https://github.com/emartech/android-emarsys-sdk/wiki/FAQ#when-do-we-increase-the-minimum-android-version-required-for-the-sdk

What's new

• extend notifications with new message styles supporting separate settings for LargeIcon and BigPicture
• inline in-app view is now available in the Android SDK Wiki page

What's fixed

• improved async functionality of the SDK by adding extra API layers above some internal dependencies
• fixed IamDialog has already had a parent crash
• improved thread safety in Dependency Container with ConcurrentHashMap
• in case mobile engage is disabled during Emarsys setup, the SDK does not initialise mobile engage contact anymore
• do not try to send requests when the device is offline

Important Notes

• Deprecated methods are going to be removed in our next major release (3.0.0)
• Please keep in mind that after 2020.09.04 we will drop support of Android KitKat (API level 19). For more details please visit https://github.com/emartech/android-emarsys-sdk/wiki/FAQ#when-do-we-increase-the-minimum-android-version-required-for-the-sdk

What's new

• Usage of firebaseInstanceId for hardware identification

What's fixed

• Access token is now kept up to date in case of unqueued network calls

Important Notes

• Deprecated methods are going to be removed in our next major release (3.0.0)
• Please keep in mind that after 2020.09.04 we will drop support of Android KitKat (API level 19). For more details please visit https://github.com/emartech/android-emarsys-sdk/wiki/FAQ#when-do-we-increase-the-minimum-android-version-required-for-the-sdk

What's new

• campaignId is now available through NotificationInformationListener - Wiki page, Sample Application

What's fixed

• reworked applicationCode change - for detailed documentation see the SDK's wiki page
• fixed Emarsys SDK dependency container thread safety issues
• fixed Push parsing error on API level 19

Important Notes

• Deprecated methods are going to be removed in our next major release (3.0.0)
• Please keep in mind that after 2020.09.04 we will drop support of Android KitKat (API level 19). For more details please visit https://github.com/emartech/android-emarsys-sdk/wiki/FAQ#when-do-we-increase-the-minimum-android-version-required-for-the-sdk

What's fixed

• fixed applicationCode change, when was initialized with null applicationCode
• fixed that the SDK now does not trigger app:start on orientation change
• fixed crash when receiving pushes on some edge cases
• fixed that main thread was blocked by track custom event

Important Notes

• Deprecated methods are going to be removed in our next major release (3.0.0)
• Please keep in mind that after 2020.09.04 we will drop support of Android KitKat (API level 19). For more details please visit https://github.com/emartech/android-emarsys-sdk/wiki/FAQ#when-do-we-increase-the-minimum-android-version-required-for-the-sdk

What's new

• Emarsys SDK now uses FusedLocationMessenger for geofencing, for more optimised battery usage.

What's fixed

• Fixed the order of commands on push notification actions. Now it is guaranteed, that the SDK launches the application before it sends the event to the application.
• The SDK now sends the push-token on application-code change if it was cached.

Important Notes

• Deprecated methods are going to be removed in our next major release (3.0.0)
• Please keep in mind that after 2020.09.04 we will drop support of Android KitKat (API level 19). For more details please visit https://github.com/emartech/android-emarsys-sdk/wiki/FAQ#when-do-we-increase-the-minimum-android-version-required-for-the-sdk

What's new

• Emarsys SDK now works async without blocking the main thread
• Push notification title is omitted when it's empty

What's fixed

• Fixed crash on in-app display in some edge cases
• Fixed SQLite error when IN clause contained more than 1000 items

Important Notes

• Deprecated methods are going to be removed in our next major release (3.0.0)
• Please keep in mind that 3 months from this release we will drop support of Android KitKat (API level 19). For more details please visit https://github.com/emartech/android-emarsys-sdk/wiki/FAQ#when-do-we-increase-the-minimum-android-version-required-for-the-sdk

What's fixed

• prevented unnecessary deviceInfo tracking
• push token is only sent when changed
• geofence now can be disabled

Important Notes

• Deprecated methods are going to be removed in our next major release (3.0.0)

What's new

• Created geofencing feature - Geofence
• Created user centric inbox - MessageInbox
• Now triggering appEvents on push actions

What's fixed

• Fixed eventHandler usage, when presented from the public API

Important Notes

• Deprecated methods are going to be removed in our next major release (3.0.0)
• Some released features are still under development and needs pilot agreement. Make sure to contact Emarsys before integrating these features!

What's fixed

• fixed mapping of null values in predict

Important Notes

• Deprecated methods are going to be removed in our next major release (3.0.0)

What's fixed

• fixed application doesn't opens twice on push
• fixed openExternalUrl action to show browser when the application is already foreground
• revert usage of Firebase instanceId to AndroidId

Important Notes

• Deprecated methods are going to be removed in our next major release (3.0.0)

What's new

• contactFieldId now can be changed through Config
• hardwareId, language, notificationSettings available through Config
• added support for silent messages
• use FirebaseInstanceId as hardwareId
• unify eventHandlers through our public API

What's fixed

• fixed sqlite cursor handling issue
• fixed sqlite transaction handling issue
• fixed event type resolution on some non English devices

Important Notes

• Deprecated methods are going to be removed in our next major release (3.0.0)