Alpha APK signing reality #53

Closed
opened 2026-08-03 22:43:03 +00:00 by TheAnachronism · 1 comment

Part of #41

Question

How are APKs from .forgejo/workflows/alpha-release.yml actually signed today (Flutter/Android defaults, keystore, v1/v2), and what does that imply for install trust and update-in-place when a friend sideloads? Primary sources: this workflow, android/ Gradle config, Flutter/Android signing docs.

Part of #41 ## Question How are APKs from .forgejo/workflows/alpha-release.yml actually signed today (Flutter/Android defaults, keystore, v1/v2), and what does that imply for install trust and update-in-place when a friend sideloads? Primary sources: this workflow, android/ Gradle config, Flutter/Android signing docs.
Author
Owner

Resolved on branch research/alpha-apk-signing-reality in docs/research/alpha-apk-signing-reality.md (commit e27472d). Alpha release-mode APKs are signed with the runner user's debug keystore; current output is v2-only, and the workflow does not guarantee key persistence, so a clean/different runner can break Android update-in-place and require uninstall/reinstall.

Resolved on branch `research/alpha-apk-signing-reality` in [`docs/research/alpha-apk-signing-reality.md`](https://git.anachronis.dev/TheAnachronism/tt-rss-viewer/src/branch/research/alpha-apk-signing-reality/docs/research/alpha-apk-signing-reality.md) (commit `e27472d`). Alpha release-mode APKs are signed with the runner user's debug keystore; current output is v2-only, and the workflow does not guarantee key persistence, so a clean/different runner can break Android update-in-place and require uninstall/reinstall.
Sign in to join this conversation.
No description provided.