I’m trying create the most basic app (using Gmail API for SMTP) for personal use only. This is based on the instructions/tutorial provided by the Wordpress plugin “WP Mail SMTP” so that you can send forms/emails via Gmail – and what’s killing me is that it works SOMETIMES. That is, I followed the instructions and published the app and it worked fine.
Then, performing the identical stream of actions results in the “Publish” button being greyed out and the error message displayed: “Your app’s OAuth configuration is incomplete. You must enter the missing information to proceed. Please visit the Branding page to finish configuring your app.”
Just to be clear: branding verification isn’t needed for this use case. There are no missing required fields on the Branding page. If I delete the client and re-add it, nothing changes. If I make subtle changes (to the name etc) and re-save it, nothing changes. It’s an error that appears with very buggy or random causes, and there appears to be no workaround. This happened (reproduced) 3 times in a row on 3 projects created from scratch.
Anybody else getting this or find a way around it?
Btw, I’m using this for the YouTube API, also without verification. Then found this thread with no answers, but I happened to stumble across it and make progress.
On the Audience page, if you hover over the grayed-out Publish button, a tooltip pops up and gives you a hint, like a secret scroll hiding behind a walkthrough wall. Then you have to complete a side quest.
Publish button tooltip:
Valid app name, support email, homepage url, and privacy policy url are required for switching the app to external production mode. You must enter the missing information to proceed. Please visit the Branding page to finish configuring your app.
Highlight reel:
I did as it said and was able to Save, then Publish. Idk if it’ll work for Gmail API access, but OAuth hurdle cleared.
Detailed walkthrough:
On the Branding page, I already had the starred fields filled in (app name, support email, dev email). I filled in the homepage and privacy policy URLs with my homepage URL (left ToS URL empty). That triggered the Authorized Domains field to become required, so I entered my domain name, then was able to Save.
Now back to the Audience page. My Publish button became active. I hit it and it published.
This worked – all I had to was add the application homepage, authorized domain, and privacy policy (I just used the same link as my home page), and I was able to publish.
I also have to suggest a different workaround for this specific issue, I just paid for the Pro version of WP Mail SMTP to use their One Click install option. I would have preferred not to pay to workaround, but it did bypass the problem and let me keep going.
My project is stuck in the Verification Center and I cannot submit my app
for data access verification. This looks identical to several recent
reports on this forum (e.g. topics 381088, 390969, 389245).
Project details:
Project ID: (PII Removed by Staff)
App name: (PII Removed by Staff)
Publishing status: In production
User type: External
Scopes requested (sensitive only, no restricted scopes):
Verification Center > Branding status says: “Your branding has been
verified, but is not yet being shown to users. You can publish it in
the branding page.”
However, there is NO “Publish branding” (or any publish/verify) button
anywhere on the Branding page.
Verification Center > Data access status says: “You need to verify and
publish your branding before you can request for verification”, and the
“Prepare for verification” button is permanently disabled (greyed out).
Everything else is complete:
Branding fully configured: app name, logo, support email, home page
(URL Removed by Staff), privacy policy
(URL Removed by Staff), terms of service
(URL Removed by Staff), authorized domain trailix.ai
Authorized domain trailix.ai is verified in Google Search Console
under the project owner account
Scope justification and demo video (YouTube, unlisted) are filled in
and saved on the Data Access page
Privacy policy includes the Google API Services User Data Policy /
Limited Use disclosure
What I have already tried, with no change:
Editing and re-saving branding fields (developer contact emails,
terms of service URL) to trigger a re-review — save succeeds
(“Branding changes saved!”) but the Verification Center status does
not change
Hard refresh, different browsers
Since the previous direct OAuth verification contact form now returns
404 and I am on Basic support, this forum seems to be the only channel.
Could someone from the Trust & Safety / OAuth verification team please
take a look at this project and either publish the verified branding or
reset the branding state so the “Prepare for verification” flow can
proceed?
