---
title: "Changelog"
slug: "changelog-engage-android-sdk"
updated: 2026-06-26T08:11:24Z
published: 2026-06-26T08:11:24Z
canonical: "docs.mapp.com/changelog-engage-android-sdk"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

## Version 6.1.5

**Released:** 9 Jun 2026

### Bug Fixes

- Fixed an issue where `triggerInApp` could return an empty message response on the first app install, caused by a timing issue during device registration.
- Added a retry mechanism (up to 3 attempts, 2 seconds apart) to improve In-App message delivery reliability immediately after the initial device registration.

> [!NOTE]
> Note
> 
> - The retry mechanism is active only during the first device registration and does not affect subsequent app launches.
> - This release improves the reliability of In-App message delivery for newly registered devices.

---

## Version 6.1.4

**Released:** 1 Jun 2026

### Bug Fixes

- Fixed an issue where In-App messages could report two events instead of one.
- Fixed an issue where In-App statistics delivery could fail in certain scenarios due to duplicate requests.
- Added retry logic for failed In-App statistics requests and de-duplicated concurrent sends to improve reliability.

### Improvements

- Updated In-App event retry logic to limit retries to a maximum of 5 attempts, improving network efficiency and preventing excessive retry loops.

> [!NOTE]
> Note
> 
> This release focuses on improving the accuracy and reliability of In-App message event reporting and statistics delivery.

---

## Version 6.1.3

13 Nov 2025 **Bug Fixes**

- Fixed an issue where notificationMode settings had no effect — setting the mode to BACKGROUND_ONLY or SILENT_ONLY previously caused push messages to be displayed even when the application was in the foreground.
- Removed unnecessary flags from the SDK’s AndroidManifest.xml:
  - usesCleartextTraffic="true"
  - networkSecurityConfig

These flags are not required by the SDK and can still be overridden in the host application’s manifest if needed.

- Fixed a bug where the device’s cached state was not properly invalidated after logout, which caused certain SDK methods to malfunction.
- Fixed an issue where device fingerprint information was not updated when changes occurred.

**Dependency Updates**

- com.google.code.gson:gson: 2.13.2
- com.google.dagger:dagger: 2.57.2
- com.google.firebase:firebase-bom: 34.4.0
- com.github.bumptech.glide:compiler: 5.0.5
- androidx.appcompat:appcompat: 1.7.1
- androidx.webkit:webkit: 1.14.0
- androidx.work:work-runtime: 2.10.5
- androidx.concurrent:concurrent-futures: 1.3.0

## Version 6.1.2

Oct 7 2025

**Bug Fixes**

- Storing custom attribute values with data type Number

## Version 6.1.1

Oct 2 2025

- Fixed bug - protocol TLSv1.1 is not supported on Android 16.
- Update Gradle version from 8.11.1 to 8.13
- Updated Android Gradle Plugin (AGP) version from 8.9.2 to 8.13.0

## 6.1.0

**Enhancements**

**Alias Management**

Added method:

```java
public RequestStatus setAlias(String alias, boolean resendAttributes)
```

When a new alias value is provided and `resendAttributes` is set to TRUE, it will trigger a re-sync of all previously set custom attributes with the backend.

**Custom Attributes**

Added method:

```java
public RequestStatus setAttributes(Map<String, Object> attributes)
```

Enables updating multiple custom attributes in a single call.

---

## 6.0.28

18.05.2025

**General Notes** We encountered unexpected issues with the release of version 6.0.27, as such we have skipped over it directly to 6.0.28

**Bug Fixes**

- Fixed an error related to missing deviceID fields
- Fixed an error that caused too many API requests and an overload on our servers.
- It is now possible to update custom user attributes on runtime.

**Improvements**

- Improved reliability of network requests.
- With this version, we prevent the extension of AppoxeeOptions. This will prevent accidentally causing re-registration of the user on every app start.
- We switched our SDK publishing method, as our current one will be sunsetted by the end of June.
- To avoid overloading our servers, new values are now compared to the existing cache before being sent to the backend.

**Implementation Guideline** Please ensure AppoxeeOptions is not implemented as a subclass in your current SDK implementation.