android-credentialslisted
Install: claude install-skill yybd/app-factory
# Android Credentials & Signing
> **Conversational language:** talk to the user — questions, summaries, reports — in the `conversational language` set in the hub `DATA.md` (`$APP_HUB/DATA.md`); fall back to the language the user writes in if it is unset. This sets the *conversation* language only.
Android signing is far smaller than Apple's — no provisioning profiles, no
per-device entitlements, no portal. One keystore signs the build; Google does the
rest. Almost every confusion comes from **there being two keys, not one.**
## Prerequisites
- **Tools:** a JDK matching the project's toolchain (`keytool`, `jarsigner`) and
`apksigner` from the Android SDK build-tools; nothing to `pip`/`gem` install.
- **Credentials:** owned here — the upload keystore under `$KEYS_ROOT/signing/android/` and the
Play service-account JSON, both recorded by path in `$KEYS_ROOT/credentials.json`.
- **Hub (`$APP_HUB`):** optional — `DATA.md` records identifiers and paths and sets the
conversational language; the secrets themselves never live there.
- **Other tracks:** none.
## The two keys
| | **Upload key** | **App signing key** |
|---|---|---|
| Who holds it | you (`$KEYS_ROOT/signing/android/<app>/`) | **Google**, under Play App Signing |
| What it does | proves *you* uploaded the AAB | signs the APKs that reach devices |
| If lost | recoverable — ask Google to reset it | fatal if you are **not** enrolled in Play App Signing |
With Play App Signing on (the default for new apps, and ma