Supabase OAuth - Google - Staging/Prod vs. Editor Redirects

[pyee]

So I’m using Supabase Auth, and Google sign in, and everything works well. However, it seems I can either set it up to work well in the editor (development), or work right in staging, or work on the production URLs.

What am I missing, and how do you guys manage the redirect URLs on the supabase side and get them to work in all 3 environments?

[loukas]

Maybe this helps? In the EDIT I figured it out

Does Supabase sign up not automatically log the user in?

Hi @lmac ! I think I am in a similar situation and would appreciate your solution if it applies: Supabase auth with Google, user appears in supabase users & a session is created when he logs in with google email/password on the Consent Screen from the weweb botton that uses “Supabase - Sign in with Provider” workflow BUT does not appear as authorised in weweb variable (Authorised: False) and the page redirects to: http://localhost:3000/#access_token=eyJhb… which is a non accessible screen per…