mapbox / mapbox/mapbox-maps-android

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

Open
#2,691 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug :beetle:
Dominant language
Kotlin
Stars
578
Forks
161
PR merge metrics
No merged PRs in 30d

Description

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?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the native libraries inside the listed android-ndk27:11.15.0 AARs and compare their ABI contents with the older artifacts. Verify whether armeabi-v7a and 16KB page-size support are present, then document which artifact or configuration preserves the affected devices.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.