Repository navigation
Conversation
Both apk-job failures on this repository happen before any project code runs: - android-actions/setup-android@v3 fails on the current hosted runner, so the job never reaches npm ci (the SDK is already installed on ubuntu-latest). - expo prebuild generates a Gradle 9 wrapper while React Native ships AGP 8.12; that pairing fails at configuration time with "SoftwareComponent with name 'release' not found". Install the pinned SDK packages with sdkmanager, pin the wrapper to Gradle 8.14.3 after prebuild, and upload the APK as an artifact as well as to the release. workflow_dispatch is added so a build can be triggered without a tag.
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
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.
What
The
apkjob has been failing before it reaches any project code. Two independent breakages:1.
android-actions/setup-android@v3fails on the current hosted runner.The job stops there, so
npm ciand the build never run.ubuntu-latestalready ships the Android SDK, so this installs the pinned packages withsdkmanagerinstead of going through the action:2. Gradle 9 + AGP 8.12 cannot configure the
:expoproject.expo prebuildgeneratesgradle-9.3.1-bin.zipin the wrapper, whilereact-native/gradle/libs.versions.tomlpinsagp = 8.12.0. That pair dies at configuration time with:After prebuild the wrapper is pointed at Gradle 8.14.3, which is the line AGP 8.12 supports. Reproduced and verified locally: 9.3.1 fails in ~9 min at configuration, 8.14.3 builds the arm64 release APK.
Also
workflow_dispatchso a build can be triggered without pushing a tag (handy for testing the toolchain).upload-artifactbefore the release step, so a build is retrievable even when the release upload or the signing secret is missing.softprops/action-gh-releasegetscontinue-on-error: true; without a release permission the artifact is still the deliverable.Verification
Ran this exact workflow on a fork against
v1.8.0and it produced a working arm64 APK (apksigner verifyclean,INTERNETpermission present,assets/index.android.bundleintact). Thecheckjob is unaffected.No project source is touched — the diff is
.github/workflows/android.ymlonly.