Alpha APK signing reality #53
Labels
No labels
needs-info
needs-triage
ready-for-agent
ready-for-human
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
TheAnachronism/tt-rss-viewer#53
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
Resolved on branch
research/alpha-apk-signing-realityindocs/research/alpha-apk-signing-reality.md(commite27472d). 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.