We operate a small personal-use publishing dashboard using an External OAuth web client. The project is In production and its branding has been verified and published. The Audience page shows 3 users / 100, and the token-grant limit is 10,000 per day.
New Drive authorization succeeds through the same client and HTTPS callback. Existing YouTube refresh grants still work. However, new authorization for both YouTube channel owners displays “This app is blocked”, with no Advanced or continuation option and no visible numeric error code. The owners have also reproduced this manually in normal Chrome, so it is not limited to an embedded browser or automated clicks.
The application’s YouTube request uses:
- https://www.googleapis.com/auth/youtube.readonly
- https://www.googleapis.com/auth/youtube.upload
- https://www.googleapis.com/auth/youtube.force-ssl
These scopes are declared under Data Access and match the application’s existing request. A diagnostic request containing youtube.readonly alone also reaches the same hard block. We stopped before consent, did not obtain a code/token, and have not replaced or revoked the working grants.
Google documents a personal-use exemption for apps with fewer than 100 users:
We understand that this exemption does not override account protections or other applicable restrictions. We have not identified a specific client or policy error from the generic heading. The Console’s Errors chart currently shows an earlier date range and does not explain the recent failure.
What is the supported way to determine the exact blocking reason for this case? Is there a documented private diagnostic/contact route to distinguish a client restriction, account restriction, YouTube-specific issue or scope-verification requirement?
If scope verification is specifically required, how should the complete consent portion of the required demonstration be supplied while new consent itself is blocked? We do not want to submit a simulated or misleading successful OAuth flow.
We are preserving the working grants and are not seeking to bypass account protections or create replacement projects. We can supply project-specific identifiers through an appropriate private Google support channel.