OAuth branding verification stuck: Name mismatch due to Supabase callback domain (No Trust & Safety email received)

My branding verification is instantly rejected with the following finding:

“The app name shown on your OAuth consent screen does not match the app name on your home page.”

The Console tells me to “Reply to your email thread with our Trust and Safety team after you have resolved the issues.” However, because the rejection is handled instantly by the automated gateway, no email thread from Trust & Safety has ever been created or sent to my developer contact address (I have checked all inbox folders, including spam/promotions).

Technical Root Cause:
Because our app is currently unverified, Google’s consent screen falls back to displaying our OAuth redirect host (supabase.co) as the app name to users.

When the automated verification crawler initiates the sign-in flow on our website:

  1. It sees the Google consent screen displaying supabase.co instead of our actual configured app name (“LearnStack”).
  2. It compares supabase.co to the actual brand name “LearnStack” on our homepage (learnstackos.com) and flags it as a mismatch.

What I have already verified:

  • Our Authorized domains list only contains learnstackos.com. We do not have supabase.co listed under Authorized domains.
  • We do not have a custom logo uploaded (so this should be a standard verification).
  • Our homepage at learnstackos.com has “LearnStack” in the <title> tag, headers, and body copy.
  • Our domain ownership is fully verified in Google Search Console.

Since I cannot afford a custom authentication domain with our hosted provider, and the automated system is blocking us from receiving the manual review email, could a Google representative please manually trigger the Trust & Safety email thread for our project or initiate the manual review?

Thank you!