Marketing Cloud Personalization Android SDK Release Notes

Released April 2026

Fixed a potential Application Not Responding (ANR) error by moving persisted configuration and queued event loading to a background thread during SDK initialization. This update prevents synchronous disk I/O from blocking the main thread on devices with low internal storage.
Added Evergage.OnSdkReadyListener and a corresponding start(ClientConfiguration, OnSdkReadyListener) method to handle SDK readiness. The callback runs on the main thread after persisted state loads and the anonymous ID is stable. Use this overload when your app requires a reliable anonymousId before making an outbound request. Standard tracking calls don't need to wait and continue to queue automatically.
Added the isServerConfigLoaded() method to check whether server configuration is loaded and events are campaign-eligible.
Added OnServerConfigLoadedListener alng with the addOnServerConfigLoadedListener and removeOnServerConfigLoadedListener methods. The listener runs on the main thread when server configuration is loaded and events are campaign-eligible, and fires immediately if configuration is already loaded when the listener is registered.
Updated the Mobile Data Campaigns Guide with the recommended pattern for deferring campaign handler registration until server configuration has loaded.

Released March 2026

Added the Google Play SDK Console verification file for improved developer authentication.
Resolved compatibility issues to ensure seamless performance on Android 15.
Resolved a thread safety issue with SimpleDateFormat initialization.
Resolved UI coordinate handling to ensure accurate data capture in event tracking.

Released August 2024

Resolved an issue with host app minification and obfuscation (for instance, ProGuard) that caused class renaming.

Released August 2023

Released June 2023

OS updates:
- EvergageActivity needs to declare android:exported in the manifest
- Official Google/Android nullability annotations have transitioned from the older com.android.support:support-annotations to the latest androidx.annotation:annotation. You may find that those annotation libraries declare using a specific Kotlin version, which may collide with other Kotlin versions declared by other dependencies in your app. One way to resolve this is to choose a Kotlin version to consistently use everywhere:
Push notification updates:
- Verify user has granted permission to the new Android 33 runtime notification permission before accepting the Firebase Cloud Messaging token
- Support automatically getting token in more recent Firebase Cloud Messaging versions, when the host app is using Firebase and has enabled usePushNotifications
Documentation updates:
- Additional details in setFirebaseToken and Push Notifications Guide credentials
- User consent should be obtained before calling start
- Additional details in globalContext

Released December 2018

New feature: mobile push notification campaigns, supporting Firebase Cloud Messaging
Automatically gather time zone, to support time zone specific scheduling of push notification campaigns
Expanded app-defined ClientConfiguration provided on start
Fixed test URL confirmation toasts (Android window permissions had changed)
Support accumulating time viewed via viewCategory and viewTag, as was already done for viewItem and viewItemDetail
Support optional different action name in view APIs, via

Released June 2017

Fixed: After reset, the SDK needs to once again automatically fetch the initial configuration from the server
Documentation improvements

Released December 2016

Released November 2016

First GA public release

Network: Queueing, connectivity monitoring
Tracking: APIs, Screen/Activity context, lifecycle monitoring (Activities, "foreground", "background")
Campaigns: Data, In-App Message, URL-handling for testing
Auto-detects DEBUG/debuggable builds and adjusts default log level