Description

After #30590 excluded x86_64 from the production AAB (to silence Play's 16 KB page-size warning), Play started rejecting the next release with:

This release is not compliant with the Google Play 64-bit requirement.
The following APKs or App Bundles are available to 64-bit devices, but they only have 32-bit native code: 5174

Play's 64-bit rule requires every 32-bit ABI shipped to be paired with its 64-bit equivalent:

Shipping x86 without x86_64 is what triggered the rejection.

Fix

Drop x86 too, making production ARM-only (armeabi-v7a + arm64-v8a). This satisfies both:

• 64-bit rule — armeabi-v7a is paired with arm64-v8a; no unpaired 32-bit ABI remains.
• 16 KB rule — no x86_64 means no x86_64 libconceal.so / libsecp256k1.so warnings.

android/app/build.gradle's existing abiFilters(*reactNativeArchitectures()) plumbing automatically picks up the new list, so this is a one-file change.

User impact

Essentially zero. Real Android phones haven't shipped on x86 since ~2016 (the Asus Zenfone 2 era). Any modern Chromebook or emulator that could run x86 is also arm64-v8a or x86_64-capable, and Play picks one of those instead. android/gradle.properties.github.dual-versions (used for BrowserStack real-device runs) has been on armeabi-v7a,arm64-v8a all along, so this just brings the main release config in line with the proven-real-devices target set.

What's NOT changing

• android/gradle.properties (default, local dev) — still ships all four ABIs for emulator support.
• android/gradle.properties.github (CI E2E) — still uses x86_64.
• android/gradle.properties.github.dual-versions — already armeabi-v7a,arm64-v8a.

Changelog

CHANGELOG entry: null

Related issues

Fixes: Google Play "This release is not compliant with the Google Play 64-bit requirement" rejection introduced by #30590.

Follow-up trackers for fixing the underlying 16 KB alignment so we can re-add x86_64 / x86 if ever needed:

• tech-debt(android): replace react-native-fast-crypto with quick-crypto scrypt to drop libsecp256k1.so #30591 — replace react-native-fast-crypto with react-native-quick-crypto scrypt
• tech-debt(android): drop Facebook Conceal dependency from react-native-keychain to remove libconceal.so #30592 — drop the Facebook Conceal dependency from react-native-keychain

Manual testing steps

Feature: Production AAB no longer contains x86 or x86_64 ABIs

  Scenario: A production release build is generated
    Given a clean checkout of this branch
    When the production AAB is built via the standard release workflow
      (cp android/gradle.properties.release android/gradle.properties
       before ./gradlew bundleProdRelease)
    Then `unzip -l app-prod-release.aab | grep '/lib/'` shows only
      `lib/arm64-v8a/` and `lib/armeabi-v7a/` entries
    And no `lib/x86/` or `lib/x86_64/` entries appear

  Scenario: Local dev on x86_64 emulator still works
    Given default android/gradle.properties (unchanged) is in use
    When `yarn android` is run
    Then x86_64 native libs are still produced and the app installs/runs

  Scenario: CI E2E on x86_64 emulator still works
    Given android/gradle.properties.github (unchanged) overlays for CI
    When `./gradlew assembleProdDebug` runs
    Then the resulting APK contains `lib/x86_64/` and Detox tests pass

  Scenario: Play Console upload succeeds
    Given a production AAB built from this branch
    When the AAB is uploaded to the Play Console
    Then the 64-bit compliance check passes
    And no 16 KB page-size warning appears for x86_64 .so files

Screenshots/Recordings

Before

Play Console:

Error: This release is not compliant with the Google Play 64-bit requirement.
The following APKs or App Bundles are available to 64-bit devices, but they only have 32-bit native code: 5174

After

64-bit compliance check passes; 16 KB warning for x86_64 .so files remains cleared.

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable — N/A (build-config change; verification is via the unzip -l check on the produced AAB and the Play Console upload)
• I've documented my code using JSDoc format if applicable — N/A
• I've applied the right labels on the PR — team-mobile-platform

Performance checks (if applicable)

• I've tested on Android — gradle.properties.github.dual-versions has been on armeabi-v7a,arm64-v8a for BrowserStack real-device runs without issue.
• I've tested with a power user scenario — N/A (no JS behavior change)
• I've instrumented key operations with Sentry traces — N/A

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

Made with Cursor