Google OAuth always returns 500 error on /auth/v1/callback after login
Hi all,
I am trying to set up Google OAuth with Supabase Auth for my Expo React Native app (using @supabase/supabase-js@2.52.0). After logging in with Google, I always get a 500 error on the /auth/v1/callback endpoint. This happens both in my app and when I test directly via the authorize URL.
What I’ve tried:
After authenticating with Google, I am redirected to the callback URL and receive a 500 error from Supabase. I have rebuilt credentials and double-checked all settings multiple times.
Is there anything else I should check, or is this a known issue? Any help would be appreciated.
Thank you!
I am trying to set up Google OAuth with Supabase Auth for my Expo React Native app (using @supabase/supabase-js@2.52.0). After logging in with Google, I always get a 500 error on the /auth/v1/callback endpoint. This happens both in my app and when I test directly via the authorize URL.
What I’ve tried:
- Created a Google Cloud OAuth 2.0 client (type: Web application)
- Set the authorized redirect URI in Google Cloud to: https://cqhfwtkdmbjmaeeznovd.supabase.co/auth/v1/callback
- Added my Supabase project domain (cqhfwtkdmbjmaeeznovd.supabase.co) to the Authorized Domains in the Google Cloud OAuth consent screen
- Set the client ID and client secret from Google Cloud in the Supabase dashboard (Auth > Providers > Google), double-checked for typos and extra spaces
- Regenerated the client secret and tried creating a new OAuth client
- Confirmed my Google OAuth consent screen is in Testing mode and my user is listed as a test user
- Waited for changes to propagate
- Checked Supabase Auth logs, but did not see a clear error message
- Tried the flow both from my app and by visiting https://cqhfwtkdmbjmaeeznovd.supabase.co/auth/v1/authorize?provider=google directly in the browser
- OS: Windows 10
- Framework: Expo React Native
- Supabase JS: @supabase/supabase-js@2.52.0
- Platform: Web and Android
After authenticating with Google, I am redirected to the callback URL and receive a 500 error from Supabase. I have rebuilt credentials and double-checked all settings multiple times.
Is there anything else I should check, or is this a known issue? Any help would be appreciated.
Thank you!
