Hi I'm trying to use the provider way to login. Problem: it looks like the ``client.auth.user()`` is not reactive? Like I need to refresh my page to get the data (see gif)

I don't really know if it comes from Supabase or me, here is my code:

js
import { createClient } from '@supabase/supabase-js';

const client = createClient(
  import.meta.env.VITE_SUPABASE_URL as string,
  import.meta.env.VITE_SUPABASE_KEY as string
);

console.log('client.auth.user() =>', client.auth.user());

After some searchs, I think it could be come from there: https://github.com/supabase/gotrue-js/blob/master/src/GoTrueClient.ts#L67-L68

Okay so after tried a lot of things with gotrue, I get something really.... uh

Like I get the object in the localStorage, but when I'm trying to get it I get a null value??

But I think a workaround isn't a real fix (still a fix anyway for my case). I don't know why gotrue lib broke, but I think it should be fix a day

can you show your login code?

The ``getAccount`` method just returns the user

But as you saw in the dev tool screenshot, after login using a provider, the session is not saved correctly. It works fine after refresh the page manually

So I investigated the gotrue lib, and tried to debug it manually

can i see that code

you set user on the Root of svelte app

I'm not sure about the life cycle of svelte app. But it seems access client.auth.user() from the store doesn't work for your case

It works but I need to refresh my page manually after login using a provider

hmm okay, still weird for me anyway, like it shouldn't be a problem to get the current user logged because it is stored in the localstorage, so gotrue is making something weird here. Also, I don't really understand why returning values for the login with provider because we're redirect, so we never get that data (but it's another story)

The main issue here is gotrue which can't get the localStorage correctly

I don't know if it's because of js lang, or if it's a workflow issue

for it's crucial that your get user runs before or after getSessionFromUrl completes

> should give the current logged user, and not null after login using a provider it doesn't give you the user because you access it before the user is ready

at the state when you call the method, the user is not ready

But the user is stored in the local storage right?

1. you call login with 3rd party login 2. it will redirect back to your website with auth_token. 3. supabase client will get the token and send to Gotrue server for validation then the server will return the user info.

so at step 3. it will take a while for that to happen. That's why when you access it immediately, the user is null. if you refresh again, the user info is already on localstorage. So it can return immediately.

Wouldn't be better to open a new window with the provider, and so we can get the user object directly using ``client.auth.signIn({ provider: 'github' })`` for example?

So

js
const { user } = await client.auth.signIn({  provider: 'github' })

Would work

Because right now, we can't get the user like that xD

> Then the access_token needs to be verify with supabase gotrue-server which then will return the user if token is valid anyway, you will need to wait for this validation before you can access the user info

at least that's how supabase gotrue Oauth2 works

hope this help, if not feel free to open an issue on gotrue-js library

however as i know, it's troublesome to use supabase-client on backend api route.

yeah, i may have to admit you are right. It's a workaround

hahaha 😇 hope that we can do better

btw, i love thread in discord. Really help with long discussion like this 👍