Version 7.0.1
Released: 25 Mar 2026
Bug Fixes
Fixed an issue during migration from SDK v6 to v7 where registration data (alias, push opt-in state, tags, and custom attributes) could be lost if the device was offline or the server was unreachable. Migration data is now preserved and retried on the next launch.
Fixed a potential application freeze caused by concurrent updates to tags or custom attributes in the storage layer.
Fixed incorrect URL encoding for query parameters, ensuring proper handling of special characters in API requests.
Improved push notification reliability by addressing edge cases related to missed or duplicate push events.
Corrected ProGuard / consumer rules to prevent SDK classes from being stripped in release builds.
Improvements
Improved thread safety during SDK initialization to prevent race conditions when initialized from multiple threads.
Reduced application startup overhead through lazy initialization of internal components.
Build Requirements
Gradle: 9.3.0 or higher
Android Gradle Plugin: 9.1.0 or higher
Notes
This release focuses on migration reliability, stability, and push delivery consistency.
Upgrade is strongly recommended, especially for customers migrating from SDK v6.
Version 7.0.0
Released: 25 Feb 2026
Initial Release
First official public release of the Mapp Engage Android SDK v7.
Establishes the new SDK generation under the artifact:
com.mapp.sdk:engage-android
Introduces the asynchronous API model based on Call<T>.
Defines the technical baseline for v7:
Minimum SDK: 23
Target SDK: 36
Java 17
Kotlin 2.2.21+
Breaking Changes
Android SDK v7 is not backward compatible with SDK v6.
Public API structure differs from previous versions.
Migration from v6 requires code adjustments. Refer to the Migration Guide.