Changes in a Google OAuth testing project may sometimes seem not to reflect immediately due to caching, propagation delay, or misconfiguration. Here’s how to fix it effectively:
Verify redirect URI configuration: Ensure the Redirect URI in the Google Cloud Console exactly matches the URI used in your app, including protocol (https://) and trailing slashes. Even small differences cause redirect_uri_mismatch errors.
Clear cached credentials or tokens: OAuth clients often cache previous redirect URIs or credentials. Try revoking old tokens or testing in an incognito/private browser window to ensure changes take effect.
Wait for propagation: Some updates in Google Cloud Console, like Drive UI Integration URLs, can take a few minutes to propagate across Google servers. Wait 5–10 minutes and retry the flow.
Double-check project and API selection: Confirm that the changes were made in the same testing project and that the correct Google Drive API and UI integration are enabled. Changes in one project don’t affect another.
Test with a new client or session: If updates still don’t reflect, create a new OAuth client ID or restart your app session to force Google’s OAuth system to fetch the latest configuration. This often resolves stale configuration issues.
Ensure exact URI matches, clear cached tokens, wait for propagation, confirm project/API settings, and retry with a fresh session.