Releases: emartech/android-emarsys-sdk
Releases · emartech/android-emarsys-sdk
2.13.0
What's new
getPushToken
- the SDK now provides a method under push which returns the pushToken
isAutomaticPushSendingEnabled
- the SDK now provides a method under config which returns if the automaticPushSending is enabled or not
sdkVersion
- the SDK now provides a method under config which returns the current version of Emarsys SDK
verboseConsoleLogging
- verbose console logging is now available in the Emarsys SDK
What's fixed
- Fixed an issue, where Inline In-App buttonClicks were not reported
- Fixed nullPointerException in EmarsysMessagingService when deviceInfo was accessed before the setup finished
Important Notes
- Deprecated methods are going to be removed in our next major release (3.0.0)
2.12.1
2.12.0
Known Issues
- This release does not contains transitive dependencies please use 2.12.1 instead.
What's new
Shared hardwareId
- Added support to share hardware IDs between customer applications. More info in the link above.
In-app
- Added support for a newer version of the backend service, which allows an unlimited amount of in-app displays
What's changed
- From this version cached data stored in the shared preferences are encrypted.
What's fixed
- Fixed an issue, that caused a crash when more than 100 geofences were registered.
- In-app dialog now closes when an URL button is clicked.
Important Notes
- Deprecated methods are going to be removed in our next major release (3.0.0)
2.11.1
What's fixed
Mobile Engage Session
- Fixed an issue, where session handling could happen on the UI thread.
Geofence
- Fixed an issue, that geofence triggers could cause an exception on some edge cases.
- Fixed that, the GeofenceBroadcastReceiver worked on the UI thread.
Important Notes
- Deprecated methods are going to be removed in our next major release (3.0.0)
Release 2.11.0
What's new
Mobile Engage Session
- Emarsys SDK now creates sessions, when the application is in foreground. More information is available here
Known Issues
- In this version we discovered a bug, where the SDK throws an exception on the main thread, instead of the SDK's. We do not recommend to use this version in production, use the previous version instead.
What's fixed
Inline in-app
- Fixed issue, where buttonClicks were not reported
Important Notes
- Deprecated methods are going to be removed in our next major release (3.0.0)
2.10.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)
2.9.1
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)
2.9.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
2.8.0
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
setContactfirst
What's fixed
Push Notifications
- the title of push messages using the
MESSAGEstyle 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
2.7.0
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