I've been struggling with Supabase user's being null on the server but not on the client. On the server I'm using

supabase.auth.api.getUserByCookie(req)

(using next.js), and on the client I'm using

supabase.auth.user()

. What often happens is in a pretty short time period after authentication (30 mins or so), the

getUserByCookie

starts returning null, but

supabase.auth.user()

correctly resolves the user on the client. I still have the sb:token cookie and it's not expired yet, so I'm confused why that's not working Any idea what I might be doing wrong?

You need to set the cookie first before you can get the cookie

supabase.auth.api.setAuthCookie

It looks like am calling that following this API route from the next.js example: https://github.com/supabase/supabase/blob/master/examples/nextjs-with-supabase-auth/pages/api/auth.js

Hmm I'm not sure about that workaround, unfortunately I'm not using Supabase with Next.js but with SvelteKit and the setup is sorta similar, but I'm definitely getting the user on the server as well as the client

Sure, that could help! Thanks

Thanks, and just found this issue that might be what I'm experiencing https://github.com/supabase/gotrue-js/issues/32#issuecomment-797012940

I'm almost certain the auto refresh issue was fixed months ago

That or maybe the next.js example is missing something? I'm not using the

@supabase/ui

Auth

stuff, I'm guessing there's nothing in there that would be relevant for refreshing tokens. Only thing I can see in that source for that component that i'm not using is auth.session()

Yeah auth.session() shouldn't make a difference in this case

Not sure, I'll give that a try shortly

I am also facing this issue with nextjs and supabase, after some inactivity or if i change some code while server running on localhost, the user becomes null, not sure why, in supabase settings the jwt expiry is 1 hr but this is happening very oftenly.

Can you create an issue on the Supabase GitHub along with the steps taken to get this result. Also if possible create an example repo that replicates the issue.