Hello,
Project number: (PII Removed by Staff)
Project ID: (PII Removed by Staff)
App name: Uplace
Homepage: (URL Removed by Staff)
Our OAuth branding verification is stuck in a rejection loop with a single finding:
“The app name shown on your OAuth consent screen does not match the app name on your home page.”
This finding does not reflect the actual state of our homepage:
- The OAuth consent screen app name is “Uplace”
- The homepage title tag, og:title and og:site_name all read “Uplace”
- The site is fully server-rendered (static Astro build), so the name is visible to any crawler without JavaScript
- The name “Uplace” appears in the visible page content and in the site logo
- The homepage describes the app’s functionality and links to our privacy policy (URL Removed by Staff) and terms of service ( URL Removed by Staff), matching the URLs configured on the consent screen
- The authorized domain (URL Removed by Staff) is verified in Google Search Console with a project owner account
Additional context:
- This exact branding was previously reviewed and approved with no issue. The re-verification was only triggered by an update to the user support email address.
- We also tried changing the app name to lowercase “uplace” to match the logo exactly. Same instant rejection.
- We have temporarily removed the Google Calendar scopes from our request in order to resolve the branding step first. Still rejected.
- Every resubmission is rejected almost immediately with the same finding, which strongly suggests an automated gateway rather than a manual review.
The Verification Center instructs us to “Reply to your email thread with our Trust and Safety team after you have resolved the issues.” However, no such email was ever received. We checked the inbox and spam folders of the developer contact address, the user support address and all project owner accounts. No thread exists, so we have no way to notify a reviewer that the issue is resolved.
“Last reviewed” currently shows 17 Aug 2026, and resubmitting does not change the outcome.
This appears to be the same recurring issue reported in several recent threads in this category (same finding, same missing Trust & Safety email), some of which were resolved by the Third Party Data Safety team after being posted here.
Request: could a community manager or the Third Party Data Safety team trigger a manual re-review of our branding, or provide a channel to submit our fix confirmation? We are happy to provide side-by-side screenshots of the consent screen configuration and the live homepage.
Thank you very much for your help.