Record submitted foreground location declaration

This commit is contained in:
SimpleTest 2026-08-13 21:58:11 +03:00
parent dbfb019598
commit ba92a7e62e
4 changed files with 47 additions and 45 deletions

View File

@ -95,22 +95,14 @@ permission or disclosure screen.
Do not use a real home address, real medical information, chat text, email,
handover code, access token, or another person's location in the recording.
### Current draft review
### Retained operator copy
The local 30-second draft
`/g/home/Downloads/Who-Need-Help-Play-Console-location-sharing-DRAFT.mp4`
was visually reviewed on 2026-08-09. Its SHA-256 is
`550d831747e75abb4ad1bea11ff20c37b6ceedbf971883643d102fd04168b2ab`.
It shows the before-sharing state, the in-app trigger, prominent disclosure,
Android location permission, active in-app state, persistent notification,
the matched participant's live marker, background/minimized operation, the
notification Stop action, and the removed marker after Stop.
Earlier draft recordings were removed after the final Play-delivered evidence
was approved. The retained operator copy is:
This draft is a recording reference, not final Play submission evidence. The
final unlisted video must be recorded from the exact `0.1.2 (3)` build delivered
through Google Play Internal testing, and that installed build must pass the
Play installer, signing identity, App Link, active-sharing, and Stop-cleanup
checks before the video URL is entered in Play Console.
`/home/simple/Downloads/Who-Need-Help-Google-Play-FGS-location-review.mp4`
It is the verified 21.379802-second edit described below, not a separate draft.
### Reproducible production fixture
@ -226,9 +218,15 @@ Server-side verification for the same take observed active tracking with a
retained current position, then stopped tracking with zero retained raw
positions. Exact cleanup deleted the run-scoped request, assignment, tracking
session, and temporary requester; the protected runtime state and prepare log
were removed. Production readiness remained healthy. This file is final local
evidence, but it is not considered submitted until an unlisted hosted URL is
entered and saved in Play Console.
were removed. Production readiness remained healthy. The retained operator
copy has the same SHA-256 and is stored at
`/home/simple/Downloads/Who-Need-Help-Google-Play-FGS-location-review.mp4`.
The video was hosted as an unlisted YouTube Short at
`https://youtube.com/shorts/UZh_QBdlbBc`. The authenticated Play Console
foreground-service form was saved with **User-initiated location sharing** and
this URL. This records the submitted form state; it is not a claim that Google
has approved the declaration.
The remaining Play policy references were rechecked on 2026-08-10. The current
Play Help still requires a video demonstration for the declared permission and

View File

@ -6,19 +6,21 @@ does not authorize saving fields in Play Console or publishing a release.
## Observed Console state on 2026-08-13
- App type is **App**.
- App category is not selected.
- App category was subsequently saved as **Social**.
- Tags are not selected.
- Store-listing contact email, phone, and website are empty.
- The default English listing has no saved short description, full
description, app icon, feature graphic, or phone screenshots.
- The Dashboard showed 9 of 11 setup tasks complete. The remaining setup tasks
were category/contact details and the store listing.
- The Dashboard initially showed 9 of 11 setup tasks complete. Category was
saved afterward; public contact details and Store-listing completion still
require a current Console recheck.
- Closed testing was still locked pending those setup tasks and reported zero
opted-in testers.
- The foreground-service declaration had no saved task selection. Selecting
**User-initiated location sharing** temporarily exposed a required video-link
field; the selection was then cleared and the final form had all checkboxes
unchecked, no video field, and a disabled Save action. Nothing was saved.
- After this initial observation, the foreground-service declaration was saved
with **User-initiated location sharing** and the unlisted demonstration URL
`https://youtube.com/shorts/UZh_QBdlbBc`. Recheck the current Console state
before any later release; this runbook does not treat a saved form as Google
approval.
These are direct observations from the authenticated Play Console session on
that date. Recheck the Console before applying because its fields and policy

View File

@ -86,18 +86,20 @@ samples, zero retained raw positions after Stop, and exact fixture cleanup.
The final 21.379802-second foreground-location declaration video was recorded
from this Play-delivered candidate and verified locally and server-side. Its
path and SHA-256 are recorded in
`android/play-store/location-and-fgs-declaration.md`. It has not yet been
uploaded or entered in Play Console.
`android/play-store/location-and-fgs-declaration.md`. It is hosted as an
unlisted YouTube Short at `https://youtube.com/shorts/UZh_QBdlbBc`, and the
authenticated Play Console foreground-service form was saved with
**User-initiated location sharing** and this URL. This does not claim Google
approval.
The remaining gates are:
1. host the verified final video as an unlisted video and enter its URL in the
Play Console foreground-service/location form;
2. complete and verify the Play Console foreground-service/location form;
3. complete the Play Console category/contact task and Store listing; read-only
1. recheck the saved foreground-service declaration before submitting a new
bundle or release and respond to any Play policy feedback;
2. complete the Play Console public contact task and Store listing; read-only
Dashboard inspection on 2026-08-10 showed app setup at 9 of 11 tasks and
Closed testing locked;
4. recruit the required tester cohort only after Closed testing is unlocked;
3. recruit the required tester cohort only after Closed testing is unlocked;
the Dashboard currently reports `0 testers currently opted-in`;
5. keep Closed and Production tracks untouched until their separate gates are
4. keep Closed and Production tracks untouched until their separate gates are
complete.

View File

@ -77,20 +77,20 @@ results from product limits and unknown production properties.
### Google Play Console and store-presence observation on 2026-08-13
- A read-only inspection of the authenticated Play Console observed app setup
at 9 of 11 tasks. The two incomplete tasks are **Select app category and
provide contact details** and **Set up store listing**. App type is `App`,
category and tags are not selected, and the public email, phone, and website
fields are empty. The default listing still has no saved short description,
full description, app icon, feature graphic, or phone screenshots. No
Console value was saved during the inspection.
- The foreground-service declaration has no saved task selection. The current
form reveals a required video-link field when **User-initiated location
sharing** is selected; that is the only observed use case matching this
application. The verified local demonstration is
`output/android/play-console/wnh-fgs-review-final-v5.mp4`, SHA-256
- A read-only inspection of the authenticated Play Console initially observed
app setup at 9 of 11 tasks. The category was subsequently saved as `Social`;
tags remain empty. A monitored public contact address and the Store listing
still require separate verification before they can be treated as complete.
The initial observation had empty public email, phone, website, listing text,
icon, feature graphic, and screenshots; recheck the Console before applying
the prepared assets because those external fields can change independently.
- The foreground-service form was subsequently saved with
**User-initiated location sharing** and the unlisted demonstration URL
`https://youtube.com/shorts/UZh_QBdlbBc`. The retained operator copy is
`/home/simple/Downloads/Who-Need-Help-Google-Play-FGS-location-review.mp4`,
SHA-256
`3c5f52019bf8a42ff42e1d9232afc126b62627390d74eed75084d82ecb33ac56`.
It has not been hosted and no declaration was saved.
The saved form is submission evidence, not evidence of Google approval.
- Closed testing remains locked until app setup is complete. The Console
reported zero opted-in closed testers. Current Google Play documentation for
a new personal developer account requires at least 12 opted-in testers for