perf: reuse native AAR and Gradle outputs across release APKs - #55
Merged
Merged
Conversation
andre487
enabled auto-merge (squash)
October 2, 2026 22:04
APK artifacts
Built from commit |
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.
Release assembly rebuilt the gomobile AAR for each ABI and again for universal, and cleaned Gradle outputs before every APK. Build the all-ABI AAR once and reuse it with the existing ABI filters, retaining intermediate Gradle outputs between variants. Version offsets, APK_VARIANT, binding flags and signing remain unchanged.
Local complete signed-release lane: 214.47 s → 177.11 s (17.4% shorter), one sequential pair with existing caches on macOS arm64; not a CI timing guarantee. All five APKs are byte-identical to baseline, including signatures; size change is zero. Verified ABI inventories, version codes, minSdk, ZIP entries and SHA-256. Both runs passed native tests and Android tests/lint/build; candidate JVM report has 169 passing tests. Bash syntax and diff checks pass.
Exact byte sizes, hashes, method and limitations are recorded in docs/reviews/release-build-2026-10-03.md. No APK was published or installed, and official F-Droid reproducibility was not rerun.