© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
SupabaseS
Supabase•4mo ago•
2 replies
Alejandro

[CRITICAL BUG] Google OAuth Login Button is Broken on Chrome v141 (Windows/Android)

Hello Supabase Team/Community,

I am experiencing a critical issue with Google OAuth login that started after updating to Chrome version 141. It was working fine on Chrome version 140.

The NEW Symptom:
When the user clicks the "Sign in with Google" button, the application does not redirect to the Google login page at all. The user stays on the current page, and nothing happens.

Context:
* Project Stack: Next.js (App Router) + Supabase Auth
* Supabase Client: Using the recommended
@supabase/ssr
@supabase/ssr
package.
* Provider: Google OAuth (Gmail)
Supabase banner
SupabaseJoin
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
45,816Members
Resources

Similar Threads

Was this page helpful?
Recent Announcements

Similar Threads

Google oauth redirect is broken
SupabaseSSupabase / help-and-questions
6mo ago
Chrome Google Login sticks
SupabaseSSupabase / help-and-questions
3y ago
Google OAuth fails on new Chrome due to SameSite=Lax cookie (Supabase)
SupabaseSSupabase / help-and-questions
3w ago
google oauth redirect
SupabaseSSupabase / help-and-questions
4y ago