Repository navigation
Android moves from Experimental to the releases (Beta 6) - #777
Merged
Merged
Conversation
experimental.yml's android job, as a release build: this release's LARECOMP_VERSION with no experimental stamp (its update check takes the normal releases), versionCode from the run's own time (always above the experimental APKs players have), the same key, apksigner verify and check_apk.sh. Six files on a release now; 'android' is a platform for test builds. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ormal platform From Beta 6 the signed APK is on every release (release.yml). Experimental builds keep Linux aarch64 and Windows on ARM. Experimental Android installs are offered Beta 6 by LARECOMP_EXPERIMENTAL_UNTIL. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
From Beta 6, Android ships on the normal releases (user 2026-11-13).
androidjob: experimental.yml's build as a release build. It uses this release's LARECOMP_VERSION with no experimental stamp, so its update check takes the normal releases. versionCode is minutes since 2026-01-01 at the run's own time, so it's always above the experimental APKs players have. It uses the same key (ANDROID_KEYSTORE_B64 / ANDROID_KEYSTORE_PASSWORD; the job fails without them), plusapksigner verifyandtools/check_apk.sh. A release now has 6 files, andandroidis a platform for test builds.LARECOMP_EXPERIMENTAL_UNTIL "beta_6", so they offer Beta 6 once it's out. docs/android.md (docs/android.md: where the port stands, signing, device testing #770) already says the APK ships with every release.The Android session reviewed the job's rules: versionCode from the run time, no experimental stamp, keep the signing check, the NDK/CMake/platform pins, assembleRelease only, and a fresh checkout.
Checked
ci-test-relapk(run 43507134751, platforms=android): every job green; the draft gotLAS.Recomp-beta_6-android.apk(90471408 bytes).After Beta 6 is published
The Experimental page still holds the last experimental APK; delete that asset by hand.
🤖 Generated with Claude Code