Social auth broken in gotrue-js 2.45

[ehanahamed]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

Social auth worked perfectly in my app (quizfreely.ehan.dev) until today (v2.27 was published on npm today i think). When trying to sign in with google, supabase would redirect to google's auth screen and google's auth screen would redirect back to my app successfully. However supabase wouldn't sign the user in once redirected back. Email sign in still works perfectly, but social auth doesn't.

To Reproduce

1. Use supabase-js v2.27 (I used it through a cdn, jsdelivr)
2. Try to sign in with some social auth (In my case it's google)
3. Supabase redirects to google auth screen
4. Google auth screen redirects back to your site
5. Your not sign-in-ed ¯\_(ツ)_/¯

How I temporarily un-broke my app

This problem does not happen in v2.26 (which is why it only started happening to me today), so I downgraded to v2.26 and now everything works! ¯\_(ツ)_/¯

System information

• Browser: Chrome
• Version of supabase-js: 2.27

Additional context

This is probably NOT the same problem as (#811), because supabase/supabase-js#811 mentions that their problem still happens in 2.26, while my problem is solved in 2.26 and only happens in 2.27

[soedirgo]

I think you meant v2.26 and v2.27 instead of v2.6 and v2.7?

[ehanahamed]

@soedirgo Yea, my bad, I meant 2.27 and 2.26, I edited it now to avoid confusion

[ehanahamed]

The issue is "fixed" in supbase-js v2.29 because they rolled back to an older gotrue-js version (2.43.1), see supabase/supabase-js#817 for more info.

Since the problem still exists (its just temporarily "avoided" in supbase-js), I guess I'll keep this issue open?

[j4w8n]

@ehanahamed this should be resolved in supabase-js v2.31.0

[ehanahamed]

Yup, it's fixed in supbase-js 2.31, since it now uses gotrue-js v2.46! Thanks