Prompt
I’m unhappy with Supabase Auth for social login edge cases
Latest observation
That’s a pretty common feeling. Supabase Auth is solid for the “happy path,” but social login edge cases can get annoying fast—especially around account linking, provider collisions, email mismatches, redirect quirks, and sessions after browser/app changes.
If you want, I can help in a few ways:
-
Diagnose a specific issue
Tell me the exact edge case you’re hitting and I’ll help debug it. -
Compare alternatives
I can compare Supabase Auth with:- Clerk
- Auth0
- WorkOS
- Firebase Auth
- NextAuth/Auth.js
- custom OAuth + your own user table
-
Design a safer auth flow
If you want to stay on Supabase, I can suggest patterns for:- manual account linking
- avoiding duplicate users
- handling multiple providers per email
- adding email verification checks
- using a separate app-level identity table
-
Recommend a migration path
If you’re considering leaving Supabase Auth, I can outline a low-risk migration plan.
If you want, paste one example of the social login edge case that’s frustrating you, and I’ll tell you whether it’s a Supabase limitation, a configuration issue, or something worth migrating away from.