App Finishers

Fix guide · updated 2026-11-16

Supabase "Unsupported provider: provider is not enabled"

{"code":400,"error_code":"validation_failed","msg":"Unsupported provider: provider is not enabled"}

A user clicks "Sign in with Google" (or GitHub, Apple, Microsoft) and, instead of Google's account picker, the browser shows a page of raw JSON on your Supabase address: "Unsupported provider: provider is not enabled". Supabase refuses to start the login because that provider isn't switched on, or isn't fully set up, in the project your app talks to. The words after "Unsupported provider:" tell you which. Here's each variant and its fix.

What the error means

We read the Supabase Auth source code and ran it ourselves (version 2.198, November 2026) with the provider off, half set up and misspelled. When your app starts a login, Supabase Auth first loads that provider's settings. If that fails, it answers HTTP 400 with "Unsupported provider:" followed by the reason:

Your code never sees this error. signInWithOAuth() only builds the login address and sends the browser there, so it returns no error and a try/catch around it catches nothing. The JSON page comes straight from Supabase.

The one-minute check

Look at the address of the JSON page. It starts with the address of the project that answered, like https://abcdefghijklmnop.supabase.co/auth/v1/authorize?provider=google. The part before .supabase.co is that project's reference. Now look at your Supabase dashboard's address: the part after /project/ is the reference of the project you're changing. If the two differ, you're turning things on in one project while your app uses another.

You can repeat the test any time without your app: paste https://<your-ref>.supabase.co/auth/v1/authorize?provider=google into a browser. Any Google page, even a Google error page, means Supabase's side is set up. The JSON means it isn't, and the end of the message says why.

1. "provider is not enabled": the switch is off

In the Supabase dashboard, go to Authentication → Sign In / Providers and click Google (or your provider) in the list. Turn on Enable Sign in with Google, fill in Client IDs and Client Secret (for OAuth) from your Google Cloud OAuth client of type "Web application", and save. The same panel shows your project's callback URL: add it to that client's Authorized redirect URIs in Google Cloud.

If you're sure you already turned it on, it's usually one of these:

2. "missing OAuth secret": the switch is on, a key is empty

This one is a trap. The Google and Apple panels let you save with a Client ID and no secret, because Google's One Tap button and native Android and iOS sign-in don't need one. The web login, the one signInWithOAuth() starts, does. Supabase then reports the provider as on (its settings endpoint, /auth/v1/settings, says "google":true), yet every web login fails with:

{"code":400,"error_code":"validation_failed","msg":"Unsupported provider: missing OAuth secret"}

Fix: in Google Cloud (Google Auth Platform → Clients), open your OAuth client of type Web application, copy its client secret into Client Secret (for OAuth), and save. "missing OAuth client ID" is the same fix for the other field.

While you're on that panel: if you list several client IDs (web, iOS, Android), put the web one first. The web login uses the first ID in the list, and Supabase's own Google guide says the same.

3. "Provider … could not be found": a name Supabase doesn't know

The word after "Provider" is exactly what your code sent. Supabase lowercases it, so Google works like google, but it has to be one of Supabase's own names. The ones that catch people:

Write the name as a fixed string:

await supabase.auth.signInWithOAuth({
  provider: 'google',   // 'azure' for Microsoft, 'linkedin_oidc' for LinkedIn
  options: { redirectTo: window.location.origin },
});

4. Self-hosted Supabase: "missing redirect URI"

On supabase.com you never type a redirect URI: the dashboard shows it as the callback URL. On your own server, Supabase Auth reads each provider from environment variables and needs all four: GOTRUE_EXTERNAL_GOOGLE_ENABLED=true, GOTRUE_EXTERNAL_GOOGLE_CLIENT_ID, GOTRUE_EXTERNAL_GOOGLE_SECRET and GOTRUE_EXTERNAL_GOOGLE_REDIRECT_URI (the callback address you registered with Google). If one is empty, you get the matching message from cases 1 and 2, or "missing redirect URI". Apply a change with docker compose up -d: a plain restart keeps the old values.

Native mobile apps: "Provider (issuer …) is not enabled"

If your app signs in with Google's native SDK and passes the token to signInWithIdToken(), a switched-off provider gives a different message, with the code provider_disabled:

{"code":400,"error_code":"provider_disabled","msg":"Provider (issuer \"https://accounts.google.com\") is not enabled"}

Same fix as case 1. Then add your iOS and Android client IDs to Client IDs, after the web one. For iOS, Supabase's Google guide also says to turn on Skip nonce checks.

If an AI tool built your app

Your AI tool can't flip a switch in your Supabase dashboard, so cases 1 and 2 are yours to fix there. On Lovable Cloud it's different: Lovable's docs say that asking it to "Add Google login to my app" turns Google on for you. For case 3, give your AI tool this prompt:

Find every call to supabase.auth.signInWithOAuth. The provider must be a fixed lowercase name that Supabase knows ('google', 'github', 'apple', 'azure' for Microsoft, 'linkedin_oidc' for LinkedIn), never a variable that can be empty. Fix any call that doesn't follow this, list each call with its provider, and don't change anything else.

Not quite your error?

Still stuck?

If the panel shows the provider on with both keys filled in, the one-minute check points at that same project, and you still get "Unsupported provider", copy the full message from the JSON page: the part after the colon is the exact reason, and it's the first thing anyone helping you will ask for. The Auth logs in your dashboard also record each refused login.

Other Supabase problems? See Supabase fixes.