Publish app disabled for a personal-use Desktop OAuth app: which Branding fields are missing?

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.

  1. 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?
  2. 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.
  3. 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:

Update — 20 October 2026

The immediate publishing blocker is now resolved. After submitting this question, I added a small static application-information website, a privacy-policy URL, a terms-of-service URL, and the corresponding authorized domain to Branding and saved the changes. “Publish app” then became available, and I moved the app to In production. I did not test these fields individually, so this does not establish which one was necessary.

I have also reauthorized the same personal account and Desktop OAuth client with exactly the same drive.metadata.readonly scope. Token refresh and the subsequent metadata reads are working. I did not expand permissions or enable billing. Moving to In production is not the same as completing Google verification; the app still displayed an unverified-app notice during authorization.

I would still appreciate clarification on the remaining questions:

  1. For a personal-use app covered by the verification exception, which Branding fields are actually required to enable publication? Does the exception waive verification only, rather than the website/Branding configuration?
  2. Is there a supported way to identify the specific missing field when “Publish app” is disabled?
  3. Does a refresh token newly issued after moving to In production avoid the Testing-specific seven-day expiry for this scope? I understand that other expiration and revocation rules still apply. The token response did not provide a refresh-token lifetime, and I have not yet observed more than seven days of operation, so I am not claiming an unlimited lifetime.

The original description above records the situation when I submitted the question. Thank you for any guidance.