Play App Signing: what it means for Orbit and the choice to make
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,40 @@
|
||||
# Play App Signing for Orbit: what it means and the choice to make (10 November 2026)
|
||||
|
||||
Research only. No keys were created, exported or uploaded.
|
||||
|
||||
## How it works for a new app
|
||||
|
||||
- Every new Play app uses Play App Signing. Google holds the **app signing key** and signs what people install.
|
||||
- You sign uploads with a separate **upload key**. If the upload key is lost, Google can reset it; the app signing key is
|
||||
unaffected.
|
||||
- By default Google **generates** the app signing key for a new app. Before the first open-testing or production release
|
||||
you can instead choose **Change key** and provide a copy of your own key (the PEPK tool encrypts it for upload).
|
||||
- Sources: Play Console Help, "Use Play App Signing" (support.google.com/googleplay/android-developer/answer/9842756).
|
||||
|
||||
## Why it matters for Orbit
|
||||
|
||||
Both TVs run Orbit signed with your own key (certificate SHA-256 `042f9637…58e1`). Android only installs an update over
|
||||
an app signed with the same key.
|
||||
|
||||
| Choice | Your TVs | Risk |
|
||||
| --- | --- | --- |
|
||||
| **A. Give Play a copy of your key** (PEPK) | Can move to the Play version as an ordinary update. No uninstall, nothing lost. | Google holds a copy of the key your TVs trust. The key on your stick and in Bitwarden stays valid. |
|
||||
| **B. Let Google generate a new key** (the default) | Can't update to the Play version. Moving over means uninstalling, which deletes their data, unless a restore path is built first. | None to your own key. Two Orbits that can't update each other. |
|
||||
| **C. Play under a new package name** (for example `tv.orbit.classic.play`) | Keep updating from your own builds as today; the Play app is a separate install. | Two apps to maintain; no shared data. |
|
||||
|
||||
## Other things the Play edition needs
|
||||
|
||||
- **No self-updates.** Play's Device and Network Abuse policy: an app from Play may not update itself by any method
|
||||
other than Play's own. The Play build must leave out Orbit's own updater and the install-packages permission.
|
||||
- **App bundle (.aab)** rather than APK for uploads, signed with the upload key.
|
||||
- **A developer account**, which you'd create yourself.
|
||||
- **No built-in server**: done in 0.126.0 (built, not installed).
|
||||
|
||||
## My recommendation
|
||||
|
||||
**A**, unless you'd rather Google never holds your key. It's the only choice where both TVs simply update to the Play
|
||||
version and keep everything. The decision has to be made before the first open-testing or production release, because
|
||||
the key can't be changed back to yours afterwards without a key upgrade.
|
||||
|
||||
Next steps once you choose (each needs your OK): a Play build variant without the updater, an upload key kept beside
|
||||
the current backups, and an .aab built by CI.
|
||||
Reference in New Issue
Block a user