Project ID: (URL Removed by Staff)
Project number: (URL Removed by Staff)
App name: Vocitra
User type: External — Publishing status: In production
In the Verification Center, “Prepare for verification” has been permanently disabled since 24 September 2026. The Branding page shows no “Verify Branding” or “Publish branding” button, although every required field is filled in and saved: app name, support and developer emails, 120x120 logo, home page (URL Removed by Staff), privacy policy (URL Removed by Staff), terms (URL Removed by Staff), authorized domain (URL Removed by Staff) The domain is verified in Search Console under the same account.
Requested scopes: https://www.googleapis.com/auth/youtube.readonly (sensitive) and https://www.googleapis.com/auth/yt-analytics.readonly. The scope justification and the demonstration video link are saved under Data Access, and a reviewer test account is ready.
Because branding cannot be submitted, data access verification cannot be submitted either. I have already tried forcing a re-save of the branding, re-uploading the logo, the legacy consent screen at console.developers.google.com/apis/credentials/consent, and a different browser.
Could you either trigger the branding verification manually for this project, or tell me what condition unlocks the button? Several developers have reported the identical symptom on the developer forum since early September 2026 without a documented fix.
Vocitra is a read-only tool: it reads a creator’s own videos and analytics to suggest a title, description, chapters and subtitles that the creator applies themselves in YouTube Studio. It never publishes, modifies or deletes anything.
Thanks Ross.
I opened the support page: our project is on Basic support (billing only), and the console states “Your current support plan does not allow you to create cases for the selected project.” So a technical support ticket isn’t an option for us.
To recap the issue: in the Verification Center, “Prepare for verification” is disabled and no “Verify Branding” button appears, so the request can’t be submitted at all. The app is in production, the OAuth consent screen is complete, the domain is verified in Search Console, and the demo video and scope justification are saved under Data Access.
Is there another channel for OAuth verification console issues on projects without a paid support plan — or could someone from the OAuth verification team look at project ID vocitra?
Same symptom on our project, and the same loop.
Project ID: (PII Removed by Staff). User type: External. Publishing status: In production. App name: Atrium.
Branding is complete and saved: app name, support and developer email, 120x120 logo, home page (URL Removed by Staff) with the privacy policy at /legal/privacy/ and terms at /legal/terms/, authorized domain (URL Removed by Staff) (verified in Search Console under the project owner’s account). Scopes: gmail.send and calendar.readonly (sensitive).
The Branding page shows no Verify Branding or Publish branding button. The Verification Center says the branding must be verified and published before data access can be requested, and Prepare for verification stays disabled. Re-saving the domain and the logo changes nothing.
Could someone on the OAuth verification team publish the branding state for atrium-fleet, or say what unlocks the button? We’re on the Basic (billing-only) support plan, so a support case isn’t available to us either. Thank you.