Record verified Play Console setup

This commit is contained in:
SimpleTest 2026-08-03 20:44:50 +03:00
parent 39c07ea0ff
commit c56c2cebd3

View File

@ -4,16 +4,19 @@
- [x] Google Play developer identity verification approved.
- [x] Contact phone verification completed.
- [ ] Play Console enables **Create app**.
- [x] Play Console enables **Create app**.
## App identity and signing
- [ ] Create Android app `Who Need Help` with package
- [x] Create Android app `Who Need Help` with package
`org.whoneedhelp.mobile`.
- [ ] Default language: English (United States).
- [ ] App: not a game; free; no ads.
- [ ] Accept Play App Signing.
- [x] Default language: English (United States).
- [x] App: not a game; free; no ads.
- [x] Accept Play App Signing.
- [ ] Record upload-certificate SHA-256 and Play App Signing SHA-256 separately.
The source-bound candidate records the upload SHA-256; the Play App
Signing SHA-256 remains pending until the first internal release is
accepted by Play Console.
- [ ] Add the Play App Signing SHA-256 to production Google/Firebase Android
configuration.
- [ ] Publish and verify
@ -29,7 +32,9 @@
lint, package name, version code/name, target SDK, and production origin.
- [x] Install the release APK generated from the same source-bound build on the authorized
physical phone and run the release smoke test.
- [ ] Upload the source-bound AAB first to internal testing.
- [ ] Save and publish the source-bound AAB currently uploaded to the internal
testing draft. Do not mark this complete until Play Console shows one
accepted artifact and the internal release is available to testers.
## Store presence