Run Android E2E with ARM64 APKs - #58092
Closed
cortinico wants to merge 3 commits into
Closed
Conversation
meta-cla
Bot
added
the
CLA Signed
cortinico
marked this pull request as ready for review
August 24, 2026 13:24
|
@cortinico has imported this pull request. If you are a Meta employee, you can view this in D117195078. |
|
@cortinico merged this pull request in 25ebffd. |
meta-codesync Bot
pushed a commit
that referenced
this pull request
Aug 24, 2026
Summary: Follow-up to #58092. Android API 35 x86_64 emulator images expose both `x86_64` and `arm64-v8a` through `libndk_translation.so`. SoLoader 0.12.1 only searches the first ABI when loading uncompressed native libraries directly from the APK, causing ARM64-only RNTester and template apps to crash while loading `libreactnative.so`. Enable legacy JNI packaging through a CI-only Gradle init script so Android extracts the ARM64 libraries and the existing SoLoader `ApplicationSoSource` can load them. This applies only to dry-run RNTester builds and Android template E2E builds. Nightly and release packaging is unchanged. Failure evidence: https://github.com/react/react-native/actions/runs/32741094253 ## Changelog: [INTERNAL] [FIXED] - Extract native libraries for ARM64 Android E2E APKs running through NDK translation. Pull Request resolved: #58103 Test Plan: - `./node_modules/.bin/prettier --check .github/actions/build-android/action.yml .github/workflows/e2e-android-templateapp.yml` — passed. - Parsed both modified YAML files with the `yaml` Node package — passed. - Parsed the embedded workflow shell scripts with `bash -n` — passed. - Compiled `.github/workflow-scripts/legacy-jni-packaging.gradle` with the Groovy compiler bundled with Gradle 9.4.1 — passed. - Full Android E2E validation is delegated to this draft PR because the local Gradle daemon could not establish its localhost connection. Reviewed By: christophpurrer Differential Revision: D117222109 Pulled By: cortinico fbshipit-source-id: 65e09a38eed84474a2f50f7f5847e1676da4411b
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary:
Build only the
arm64-v8aAndroid ABI for dry-run CI artifacts and run the ARM64 RNTester and template-app APKs on an API 35google_apisx86_64 emulator using the system images built-in NDK translation support.This also makes the Maestro emulator API level and target configurable, logs the device ABI/native-bridge configuration, and updates local RNTester artifact selection to use the ARM64 split.
Release and nightly publication builds continue to build all supported Android ABIs.
Changelog:
[INTERNAL] [CHANGED] - Run Android E2E tests with ARM64 APKs through NDK translation.
Test Plan:
node --check .github/workflow-scripts/maestro-android.js— passed.node --check scripts/release-testing/test-release-local.js— passed.yamlNode package — passed../node_modules/.bin/prettier --check <modified files>— passed.git diff --check HEAD~3..HEAD— passed.actionlintreported only existing repository metadata warnings for the custom4-core-ubuntulabel and the missing description in the localyarn-installaction.yarn test .github/workflow-scripts/__tests__/maestro-android-test.js --runInBandcould not start because the local dependency tree is missingflow-parser; restoring dependencies was blocked by HTTP 503 responses from the npm registry.libndk_translation.so.