Verification Center: "Prepare for verification" permanently disabled — Branding page has no "Verify Branding" button

Google Cloud Cloud Foundations & Onboarding
1

Project number: *(PII Removed by Staff)** (PII Removed by Staff) — external app, publishing status **In production**, using sensitive scopes.

**The problem (chicken-and-egg):**

1. In the **OAuth Verification Center**, “Data access status” shows **not verified**, and the **“Prepare for verification”** button is disabled with the message: *“You need to verify and publish your branding before you can request for verification.”*

2. But the **Branding** page has **no “Verify Branding” button** at all — even though the documentation (Manage OAuth App Branding) says an External + In-production app should see it.

**What I have already ruled out:**

- Branding form is complete: app name (FlintDB), logo, homepage, privacy policy + terms (same domain), authorized domain, support email — all saved successfully (“Branding changes saved!”).

- Audience: External + In production.

- Domain `flintdb.app` is verified in Search Console (`sc-domain:flintdb.app`) under the same account that owns the project.

- Re-saving branding with an equivalent homepage value does not trigger any verification flow.

- Same UI on both console.cloud.google.com and console.developers.google.com — no button on either.

- The Audience page still says “please submit your app for review” and the external user cap counts 1/100, so there is **no pending review** in the system.

This looks identical to topics 373997, 380094 and 380713 — the self-serve path is completely stuck, and the old direct contact form (`support.google.com/cloud/contact/oauth_app_verification`) now returns 404.

**Ask:** could someone from the OAuth verification / Trust & Safety team manually trigger the branding verification (or the data-access review) for project (PII Removed by Staff), or advise what unblocks the “Verify Branding” button? Scope justifications and a demo video are ready to submit as soon as the flow opens.

2

Adding another confirmed case of this exact bug, since it doesn’t appear resolved yet.

Project: External, sensitive/restricted scopes (gmail.readonly, gmail.send), Publishing status “In production.”

Confirmed state, checked multiple times over 24+ hours:

  • Branding: app name, logo, support email, homepage, privacy policy, terms of service, and authorized domain all filled in and saved (Save/Discard buttons greyed out — no pending changes).
  • Authorized domain is also now separately verified in Google Search Console under the same account, in case that was a factor — made no difference.
  • Tried the “minor edit” workaround (change app name, save, revert, save, hard refresh) — no new “Verify Branding” button appeared.
  • Data Access: both scopes added and saved.
  • Demo video uploaded and linked.

Despite all of this, Verification Center still shows “you need to verify and publish your branding before you can request for verification,” “Prepare for verification” stays permanently disabled, and there is no “Verify Branding” button on the Branding page at all.

Filed a report through the in-console “Send feedback” widget with a screenshot — no response after several hours. Also tried Gemini Cloud Assist in Cloud Console, which couldn’t open a support case at all (Basic support tier).

This is clearly not a per-project config issue at this point — would appreciate any word from Google staff on whether this is a known, tracked bug.

3

Same here, identical symptom, complete configuration. Domain verified as a Domain property by the project owner today and the button still doesn’t render. Adding a data point in case volume helps triage.

4

Hello,

Our OAuth consent screen (External, publishing status: In production) shows this banner on the Branding page: “Your branding has not been shown to users. Resolve the issue on the branding page and verify again.” However, there is no Verify button and no Publish Branding action anywhere on the page, so we have no way to trigger verification.

The configuration is complete and correct: app name, user support email, developer contact email, app home page, privacy policy, and terms of service links are all set; both authorized domains are listed; and the domain is verified in Google Search Console under the project owner’s account. We request only non-sensitive scopes (openid, email, profile), so no scope verification is required.

This matches other reports, for example threads 381088 and 373997.

Could you please restore or enable the Verify / Publish Branding action so our app name can be published to users? I am happy to provide the project ID or screenshots.

Thank you.

6

Same issue here, adding our case for visibility. (PII Removed by Staff) (powerads-ads-did). App is External + In production, all branding fields complete with a logo saved, authorized domain verified as a Domain property in Search Console under the same account that owns the project. The Branding page renders no “Verify Branding” button (checked the cloud.google.com and developers.google.com renders and the legacy consent path — identical), and Verification Center’s “Prepare for verification” is aria-disabled behind “You need to verify and publish your branding”. Scope justification + demo video are already saved on Data Access (single sensitive scope, ../auth/adwords). The direct contact form (support.google.com/cloud/contact/oauth_app_verification) returns 404. Happy to provide any details needed — this fully blocks verification submission.

7

Same state here, adding a data point.

Project number: (PII Removed by Staff)
User type: External, publishing status: In production
Scopes: four restricted Google Health scopes (activity_and_fitness,
health_metrics_and_measurements, sleep, profile — all .readonly)

Verification Center shows:

  • Branding status: “Your branding is not being shown to users.”
  • Data access status: “You need to verify and publish your branding
    before you can request for verification.” — “Prepare for verification”
    is greyed out.

The Branding page is complete and saved (Save is greyed out): app name,
support email, logo, home page, privacy policy and terms links all set
and returning 200, two authorized domains, developer contact set. There
is no “Verify Branding” button anywhere on the page, which the docs at
Manage OAuth App Branding - Google Cloud Platform Console Help say should be present.

Both authorized domains (nucora.ai, nucora.app) are verified in Search
Console under (PII Removed by Staff), which holds Owner on the
project — so the documented Owner/Editor requirement is satisfied.

Tried: hard refresh, re-saving branding, verifying the second domain.
No change. The oauth_app_verification contact form 404s.