I am a developer building Google Workspace Add-ons and Chrome Extensions. I am completely blocked from publishing any new products and am seeking a viable escalation path, as all standard support channels appear to be closed to me.
The Core Problem:My YouTube channel (@KarelTest), which is required to host unlisted videos for the mandatory OAuth 2.0 verification process, was terminated by what I've identified as an automated system error. This termination now prevents me from submitting new add-ons for verification.
What I Have Tried:
- YouTube Appeal: Denied by an automated system.
- Google Cloud Technical Support: Blocked, my account has no permission to create technical cases.
- Google Cloud Billing Support: Blocked, my account is on a free trial.
- Google Workspace Issue Tracker: Blocked, my account does not have permission to create issues in any relevant component.
I am in a catch-22: a system error has blocked me, and the same system prevents me from reporting the error.
Below is the detailed forensic analysis of why the termination was a misunderstanding.
1. Forensic Analysis & Root Cause:
- Unintentional Brand Impersonation: Two of my apps used names that triggered this: "Google AI Studio - File Reader" and "YouTube Playlist Collector". I now understand this violates trademark guidelines.
- Demonstration of Security Bypass: The videos showed the required process of a user clicking "Go to... (unsafe)" for an unverified app during the OAuth flow. To an automated system, this pattern is indistinguishable from a malicious actor.
2. Crucial Missing Context:These videos were not for the public. They were created solely for Google's internal OAuth verification team.
My Question:Given that I am locked out of all direct support and feedback channels, what is the correct, official escalation path for a developer to have a cross-platform issue like this reviewed by a human at Google? I am fully prepared to correct all issues with my content if given a chance.
I attempted to resolve this issue through every official developer channel available. Specifically, I tried:
- The standard YouTube appeal form.
- Creating a technical support case via the Google Cloud Console.
- Filing a bug report in the Google Workspace Issue Tracker.
My expectation was that at least one of these channels would provide a path to a human review, where I could present my detailed analysis and explain the critical context of the OAuth verification process.
The actual result was a systemic blockade. Each attempt was rejected by automated systems or permission errors related to my account's support level, leaving me with no official way to report or resolve this development-critical issue.