Marketing Cloud Personalization Android SDK Release Notes

1.5.0 

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.

1.4.2 

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.

1.4.1 

Released August 2024

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

1.4.0 

Released August 2023

1.3.1 

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:

      1// In your app's build.gradle :
2dependencies {
3    //...
4
5    // To consistently use Kotlin version 1.8.0 across transitive dependencies:
6    implementation(platform("org.jetbrains.kotlin:kotlin-bom:1.8.0"))
7
8    //...

  • Push notification updates:

  • Documentation updates:

1.3.0 

Released December 2018

1.2.3 

Released June 2017

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

1.2.2 

Released December 2016

1.2.1 

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

Marketing Cloud Personalization iOS SDK v1.5.0
Marketing Cloud Personalization Android SDK v1.5.0
Release Notes
Native Mobile SDK Features
Integration
Tracking
Push Notifications
Mobile Data Campaigns
Testing
API Reference
Item Reference
Constant Field Values

DID THIS ARTICLE SOLVE YOUR ISSUE?
Let us know so we can improve!