Reconcile Play release checklist

This commit is contained in:
SimpleTest 2026-08-13 22:08:16 +03:00
parent ba92a7e62e
commit dab96a9ed1

View File

@ -93,7 +93,8 @@ block publishing changes, including Store Listing, Pricing, and Distribution.
three localized text limits, the 512×512 icon, the 1024×500 RGB feature
graphic, and all four 1080×1920 RGB phone screenshots.
- [ ] Enter the prepared alt text when the assets are uploaded in Play Console.
- [ ] Choose category/tags in the current Console options.
- [x] Choose category in the current Console options. **Social** was saved;
tags were deliberately left empty rather than adding an inaccurate tag.
- [ ] Complete **Select an app category and provide contact details** in Play
Console. Read-only Dashboard inspection on 2026-08-10 showed this task
incomplete; no values were selected or saved during that inspection.
@ -139,31 +140,29 @@ block publishing changes, including Store Listing, Pricing, and Distribution.
behavior: not a government app, no financial features, and Healthcare
services and management only. The app is not described as a medical
service.
- [ ] Complete the mandatory Play Console foreground-service declaration for
the `location` service used by the exact AAB.
Read-only inspection on 2026-08-10 showed this as the only App content
item under `Need attention`. A repeated read-only inspection showed all
task choices unchecked, with **Save** and **Discard** disabled. The
truthful prepared choice is **User-initiated location sharing**; no
incomplete form was saved or submitted.
- [ ] Upload the unlisted demonstration video showing the user-triggered start,
- [x] Complete the mandatory Play Console foreground-service declaration for
the `location` service used by the exact AAB. The authenticated form was
saved with **User-initiated location sharing**. A saved declaration is
submission evidence, not evidence of Google approval.
- [x] Upload the unlisted demonstration video showing the user-triggered start,
prominent disclosure, Android permission, persistent notification,
minimized-app operation, and Stop action. The final local 21.379802-second
Play-delivered evidence file has been visually and server-side verified;
its exact path and checksum are recorded in
`location-and-fgs-declaration.md`. Hosting it as an unlisted video and
saving the resulting URL in Play Console remain incomplete.
minimized-app operation, and Stop action. The final 21.379802-second
Play-delivered evidence file was visually and server-side verified,
hosted as an unlisted YouTube Short at
`https://youtube.com/shorts/UZh_QBdlbBc`, and saved in the declaration.
Its retained path and checksum are recorded in
`location-and-fgs-declaration.md`.
Immediately before upload on 2026-08-10 the exact final file was
revalidated as H.264, 720×1600, 21.379802 seconds, SHA-256
`3c5f52019bf8a42ff42e1d9232afc126b62627390d74eed75084d82ecb33ac56`;
a fresh contact-sheet review still showed the disclosure, Android prompt,
minimized persistent notification with Stop, and returned stopped state.
- [ ] Reconcile any target-SDK-37 persistent precise-location declaration shown
by Play Console with the exact artifact. The app uses a user-started
location foreground service and does not declare
`ACCESS_BACKGROUND_LOCATION`; do not answer that it requests the
background-location runtime permission.
- [ ] Use and verify the prepared declaration copy in
- [x] Reconcile the target-SDK-37 location declaration with the exact artifact.
The saved use case is user-initiated location sharing. The app uses a
user-started location foreground service and does not declare
`ACCESS_BACKGROUND_LOCATION`; the form was not answered as if it requests
the background-location runtime permission.
- [x] Use and verify the prepared declaration copy in
`location-and-fgs-declaration.md`.
## Testing