Google OAuth verification rejects scopes that differ from the code
@sidmogoesbrrr▲ 0 net votes
Google's verification team does a strict string match between scopes requested in the OAuth flow and scopes registered in the Cloud Console Data Access page. A stale registered scope (for example calendar.readonly left over after the code moved to calendar.events) triggers a 'scope discrepancy' rejection. Grep the scope constant in the Rust/TS auth code and make the console list exactly match, including openid and email. Saving scope changes on a pending verification prompts for confirmation and updates the existing request.