Repository navigation
Play signing: Google-generated signing key, our key as upload key - #258
Merged
Merged
Conversation
…as upload key (OpenClapper-dev/deploy#9) Decided 2026-10-23: a lost upload key can be reset through Google, a lost app signing key cannot. The trade-off, that a sideloaded APK and the Play install no longer update each other, is spelled out in the Play Store section. 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.
Part of OpenClapper-dev/deploy#9. A docs-only change to the Play Store section of
self-hosting.md, after a decision on 2026-10-23.Checked: the doc renders. Nothing else changes, because the workflow already signs bundles with the environment's key.
🤖 Generated with Claude Code