Clarification Needed: Does android-ndk27 AAR (v11.15.0) include 32-bit ABIs? Google Play warns about losing 1,688 devices

[krishnazerion]

Environment

• Android OS version: API 36
• Devices affected: 1688
• Maps SDK Version: 11.15.0

Observed behaviour and steps to reproduce

I'm integrating Mapbox Maps SDK v11.15.0 in my app. Reason to use the ndk27 variant is to support the 16KB page size requirement from Google Play. When uploading a build using Mapbox v11.15.0 (ndk27) to Google Play, I receive this warning:

This release no longer supports 1,688 devices that were supported in your previous release. If you proceed, your app will not be available to new users on these unsupported devices, and updates will not be available to users who already have your app installed on these devices. Check changes to your supported devices to see which devices are affected.

Below artifacts are included in my app:

implementation("com.mapbox.maps:android-ndk27:11.15.0")
implementation("com.mapbox.plugin:maps-locationcomponent-ndk27:11.15.0")
implementation("com.mapbox.plugin:maps-annotation-ndk27:11.15.0")

The warning strongly suggests that 32-bit (armeabi-v7a) ABIs may no longer be included somewhere in the dependency chain — potentially due to the new Mapbox NDK27 artifacts.

I want to avoid dropping support for these devices unless this change is intentional and documented.

Additional context

• App Target SDK: 36
• Migrating to android-ndk27 artifacts from older builds
• No recent changes on my side to ABI filters
• Concerned that switching to NDK27 builds may force ARM32 device exclusion

Request

Could you please confirm:

• Which ABIs are included in the android-ndk27 AARs for v11.15.0?
• If armeabi-v7a is no longer supported, is this an intended change?
• Is there an alternative artifact or approach to preserve 32-bit device support and also include 16KB Page size support?