OAuth drive.file: Publish app disabled despite saved required Branding fields

Hello,

An External OAuth app is in Testing and uses only https://www.googleapis.com/auth/drive.file for Drive access. On Audience, Publish app is disabled and asks to complete the configuration on the Branding page.

App name, user support email, and developer contact email are populated and saved. Branding shows no field-specific validation error. Homepage, privacy-policy, and terms URLs are blank and are not marked as required in the form. No View issues control is visible.

What exact supported prerequisite enables Publish app in this configuration? Are public homepage/privacy/terms URLs mandatory for an owner-only integration that is not publicly distributed, even when brand verification is not being requested? If so, please identify the current official requirements. If not, how can the missing configuration or project state be diagnosed through the supported console or support process?

The goal is to remove Testing’s seven-day authorization limitation while keeping drive.file and the existing client, without broader Drive permissions, placeholder URLs, or bypassing verification. I understand publishing status and brand/scope verification are separate.

This question intentionally excludes account details, project/client identifiers, credentials, and private screenshots. Thank you.

Hello, there is no documented personal-use or owner-only exemption here. Publish app is a server-side completeness check, and the button does not name the requirement it thinks is unmet, so the fields you can see are not a reliable guide to what is missing.

The three blank URLs you listed, homepage, privacy policy, and terms of service, are the visible gaps in your Branding page. Fill them with real, publicly reachable pages for the app, with a privacy policy that covers the Drive data you access through drive.file, and then save and check whether Publish app becomes available. Do not use placeholder URLs. That will not work, and it can create a verification problem later.

If the button is still disabled after that, the missing requirement is not something the console shows you, and it cannot be diagnosed from the Branding page alone. Open a Google Cloud support case from the project, choose the OAuth consent screen issue, and ask support to name the exact unmet requirement that keeps Publish app disabled for this project. That is the supported way to get the missing item identified.

While you wait, stay in Testing. You will need to re-authorize every seven days, but that is the expected behaviour for an unpublished external app, and it does not mean the client or the drive.file scope is broken.