Addressing Android 15 Compatibility with 16 KB Page Size in Sendbird Android SDK

[famous90]

Background

First and foremost, we want to acknowledge the diverse needs of our customers. Many of you support a wide range of Android API levels, including legacy versions, to accommodate your users. For this reason, we’ve kept the Sendbird Android SDK’s minimum API level low and have selected library versions, such as conscrypt-android:2.2.1, to ensure broad compatibility.

While this approach ensures we meet the needs of customers working with older devices, it also means that adopting the latest enhancements and fixes for modern Android versions can be challenging. We appreciate your understanding as we work to balance these considerations.

Issue Overview

With the release of Android 15 and the introduction of the 16 KB page size feature, some applications using Sendbird Android SDK have encountered crashes. This is because the version of conscrypt-android currently used by the SDK (2.2.1) does not support 16 KB page sizes. The root cause has been identified as incompatibility in native code within conscrypt-android:2.2.1.

The good news is that conscrypt-android:2.5.3 and later versions have resolved this issue. Customers who have overridden the dependency to 2.5.3 have confirmed that this resolves the crashes.

Temporary Workaround

Until the Sendbird SDK is officially updated with a newer version of conscrypt-android or drop out conscrypt-android, you can apply the following workaround in your build.gradle file:

implementation("com.sendbird.sdk:sendbird-chat:4.19.3")
implementation("org.conscrypt:conscrypt-android:2.5.3")

This forces the dependency to use conscrypt-android:2.5.3 instead of the default version included in the SDK. Please test this solution in your app to confirm it resolves any crashes you’ve experienced.

Future Plans

We’re actively working to address this issue in the following ways:

Raising Minimum API Level

In the near future, we plan to raise the minimum API level for the Sendbird Android SDK to 27. This will allow us to drop the use of conscrypt-android entirely, as the platform’s built-in security providers (available in API 27 and above) are sufficient. This change will simplify dependency management and improve compatibility with modern Android versions.

Additional Support

If you encounter issues or have questions about this workaround, please don’t hesitate to reach out via our support channels or share your experience in this discussion. We’re here to help ensure your app’s success on all supported Android versions.

Thank you for your patience and understanding as we work to balance the diverse needs of our customers while keeping pace with Android’s evolving requirements.