fix-google-auth

Sync local Google client secrets with Supabase to resolve OAuth server errors.

Updated Nov 9, 2025

Search Tags:#oauth #supabase #dev-server #google-auth #credential-mismatch

Ready to run

npx skills add https://github.com/canyouseeus/thelostandunfounds --skill fix-google-auth

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fix-google-auth
Source: https://github.com/canyouseeus/thelostandunfounds/tree/main/.agent/skills/fix-google-auth
Command: npx skills add https://github.com/canyouseeus/thelostandunfounds --skill fix-google-auth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Google Sign-In may fail with server_error: Unable to exchange external code caused by a mismatch between locally stored credentials (.env.local) and the Google client secret configured in Supabase. This can occur after running setup-google-oauth.ts or rotating keys in Google Cloud Console.

Core Features & Use Cases

Aligns local Google client secret with Supabase to resolve sign-in failures.
Provides a guided remediation flow: update local credentials, sync Supabase, and verify login.
Includes a script to securely update the local secret and a quick verification path.

Quick Start

Update your local Google client secret to match Supabase, sync the value in Supabase, and restart the dev server to verify login.

Frequently Asked Questions about fix-google-auth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

Why does Google OAuth return server_error when logging in through Supabase?▼

Google OAuth server_error occurs when your local client secret in .env.local does not match the secret configured in Supabase, often happening after running setup scripts or rotating keys in Google Cloud Console.

How do I fix the Unable to exchange external code error in Supabase?▼

To fix the Unable to exchange external code error, update your local Google client secret to match Supabase, sync the value in your Supabase project, and restart the dev server to verify login.

When do I need to sync local credentials with Supabase for Google authentication?▼

You need to sync local credentials with Supabase when your local .env.local secrets diverge from the Supabase secret, typically after executing setup-google-oauth.ts or rotating keys in Google Cloud Console.

Does updating the Google client secret in .env.local resolve Supabase sign-in failures?▼

Updating the Google client secret in .env.local resolves Supabase sign-in failures if you also sync the identical value in Supabase and restart your dev server to complete the verification flow.

What is the best way to resolve credential mismatches between local environment and Supabase?▼

The best way to resolve credential mismatches is aligning the local Google client secret with Supabase through a guided remediation flow that updates local credentials, syncs Supabase, and verifies login.

Google OAuth not working after Google Cloud key rotation, how to fix it?▼

Fix Google OAuth after key rotation by updating the local secret in .env.local, syncing the new value with the Supabase secret configuration, and restarting the dev server to verify successful login.