OAuth verification stuck — homepage resolved, no Trust & Safety email ever received

Google Cloud Cloud Foundations & Onboarding
1

Hi Google team,

My OAuth app verification is stuck at “Pending developer action” with no email thread for me to reply to.

  • Project ID: (PII Removed by Staff)
  • OAuth Client ID: (PII Removed by Staff)
  • App name: Reassign
  • Homepage: reassign[.]ai
  • Privacy policy: reassign[.]ai/privacy
  • Developer contact: (PII Removed by Staff)
  • Sensitive scopes under review:
    • googleapis[.]com/auth/calendar.calendars.readonly
    • googleapis[.]com/auth/calendar.events

Flagged issue (last reviewed Jun 11, 2026): “Homepage requirements — your home page does not explain the purpose of your app.”

Status: Resolved. The homepage now clearly states what Reassign does and how it uses Google Calendar data, and points to the privacy policy.

The problem: the Verification Center tells me to “reply to your email thread with the Trust and Safety team,” but no such email ever arrived. I have checked every project owner/editor and every consent-screen contact address — inbox, spam, all mail, every tab — and specifically searched for both known senders (api-oauth-dev-verification-reply and google-cloud-compliance). Nothing. Project Checkup confirms my contact info is current and owners/editors are correct, so this isn’t a contact-reachability problem. The console gives no option to resubmit.

I’m on Basic support and can’t open a technical case. Could a Googler please either re-send the original review email so I can reply, or re-check the homepage requirement and advance the case?

Thank you,
Leo

2

Following up since I haven’t had a reply yet.

I’ve seen several threads in this category describing the same situation: verification stuck on “pending developer action,” with instructions to reply to a Trust & Safety email that never arrived. In a few of them it looked like the case eventually cleared on its own, without the developer doing anything.

Is that accurate? Do these sometimes resolve automatically once the flagged issue is fixed, or does someone on the team need to manually re-trigger the review or re-send the original email?

I’d just like to know whether to keep waiting or whether action is needed on my end. Any guidance appreciated.

Thanks,
Leo