I am configuring a Desktop OAuth client for my own use only, with no public distribution. The project uses a personal Google account (not a Workspace organization), External audience, Testing status, and one test user: myself. The only declared scope is https://www.googleapis.com/auth/drive.metadata.readonly.
App name, user support email and one developer contact email are configured. There is no logo, homepage, privacy-policy URL, terms-of-service URL, or authorized domain.
The Audience page disables “Publish app” and says: “To publish your app, you must complete the configuration on the Branding page.” Branding shows no field-specific error. Verification Center reports no verification is needed while Testing, and Overview’s Project diagnostics shows no recommendations. No OAuth project settings have been changed during this investigation.
- Exactly which Branding fields must be completed to enable “Publish app”? Is a public website required even for a personal-use app covered by the verification exception?
- Is there a supported diagnostic view identifying the missing requirement? I do not want to enter placeholder URLs, expand scopes, or create a new project to bypass it.
- If this personal-use app can move to In production without verification, would a newly issued refresh token for this restricted scope be free of the Testing-specific seven-day expiry? I understand other expiration/revocation rules may still apply.
Official guidance I have read:
- Submit for brand verification | App verification to use Google Authorization APIs | Google for Developers
- Restricted scope verification | App verification to use Google Authorization APIs | Google for Developers
- Manage OAuth App Branding - Google Cloud Platform Console Help
- Manage App Audience - Google Cloud Platform Console Help