64_32 AAB shows only arm64-v8a in Play Console, making 32-bit devices incompatible.

[Banupriya Srinivasan]

Android app Bundle shows only arm64-v8a in Play Console despite 64_32 build — legacy 32-bit devices marked incompatible

We’ve been building and uploading our Chromium-based Android App Bundle (.aab) to Play Console for some time now using the 64_32 configuration.
However, we recently noticed that some legacy devices (pure 32-bit / armeabi-v7a only) are showing the app as not compatible on Play Store.

Our build setup includes:

android_64bit_target_cpu = true
android_app_secondary_abi = "armeabi-v7a"
target = "//chrome/android:monochrome_64_32_public_bundle"

The generated .aab clearly contains multiple lib folders for both arm64-v8a and armeabi-v7a, but Play Console still lists only arm64-v8a under “Supported ABIs” in the App Bundle Explorer.

Has anyone encountered this behavior?

• Is there a known issue with Play Console recognizing dual-ABI (64_32) bundles?

• Do we need a separate pure 32-bit build target to maintain support for older armeabi-v7a devices but play console rejected it even though vversion codes were different.

• Or has Chromium changed how it packages secondary ABIs inside AABs?

Any insights or suggestions to ensure compatibility with pure 32-bit devices would be greatly appreciated.

Thanks in advance!

[Pradeep H]

Hi Bhanu Priya Srinivasan,

We use seperate builds for 64bit and 32bit and upload to play store. So there are two different aab builds uplaoded to Play Console. 

Play console will deliver to specific abi devices based on this.

Do you use is_high_end_android = true and chrome_pgo_phase = 2 in your build configuration ?

[Banupriya Srinivasan]

Hi Pradeep,

Yes, I tried the same too — built the MonochromePublic target with target_cpu=arm, but unfortunately I’m running into a Play Console issue while trying to upload it.

When I build the MonochromePublic target with target_cpu=arm (for 32-bit) and try uploading it, Play Console rejects the build due to the 64-bit requirement.

I already have a pure 64-bit (target_cpu=arm64) build uploaded successfully. However, even though the 32-bit build uses a lower version code, Play Console still blocks the upload because it doesn’t include a 64-bit variant in the same bundle/APK set.

Essentially, I’m trying to add 32-bit support alongside the existing 64-bit release, but the console doesn’t seem to allow publishing the 32-bit build separately.

Is there a recommended approach for handling this with Chromium-based browsers?

Also, no — I’m not using is_high_end_android = true or chrome_pgo_phase = 2 in my current build configuration. should i try adding those and rebuilding to see if it helps.

Thanks.

[Pradeep H]

Hi Banupriya

I am not particularly sure about MonoChromePublic because if you want the result you are expecting you need to make some changes in gni configuration as far as I know, instead use chrome_public_bundle to build for each abi seperately and upload to play console, this does not require any changes from your end and it should work without any issues