We use an existing Desktop OAuth client with PKCE and the androidpublisher scope for our own Google Play operator account. The project owner confirms that Google Auth Platform > Audience now displays In production.
However, a fresh consent flow still explicitly says the app is currently being tested. An authorization-code exchange with access_type=offline and prompt=consent returned a new, distinct refresh token with refresh_token_expires_in=604799. Refreshing it from our existing server also returned a remaining lifetime of approximately seven days. The downloaded client configuration has the same project ID as the project whose publishing status was changed. We have not requested a time-limited grant parameter.
Both the old and new credentials can currently read the Play product catalog and an existing purchase through the Android Publisher API (HTTP 200). We have kept the existing server credential in place and have not revoked any authorization, recreated clients, or modified user data.
The Manage OAuth Clients help page mentions 5 minutes to a few hours for client-setting changes, but I cannot find a documented propagation period specifically for Testing → In production.
- Is there a propagation delay for publishing status, and how long should we wait before retrying once?
- Can a previous testing grant cause a newly issued distinct token to retain a seven-day lifetime after publishing?
- How can Google verify the effective publishing status for this client without revoking the existing working grant?
- If this is a backend inconsistency, what is the appropriate private support/escalation channel? We can provide the project/client IDs privately.
No token, secret or authorization code is included. This is a technical question, not a request for app verification approval.