auth.session() and auth.user() return null in SPA app when called right after createClient

[gawlk]

Bug report

Describe the bug

database.auth.session() and database.auth.user() are both null when called right after const database = createClient(SUPABASE_URL, SUPABASE_ANON_KEY) in a SPA app.

Steps to reproduce the behavior, please provide code snippets or a repository:

Just try the code

Expected behavior

I expect database.auth.session() and database.auth.user() to not return null if a user is connected. I need to check that in my router to change the route if needed, yet can't without doing some custom code because of the null issue. The storage being synchronous, the returns shouldn't be null.

System information

• OS: Mac OS
• Browser (if applies) [e.g. chrome, safari]
• Version of supabase-js: latest
• Version of Node.js: latest

[kiwicopple]

Hey @gawlk - I believe you're running into this one: supabase/auth-js#36

I'm working on it this week, just trying to figure out the best way to handle it for expo apps .

If you think it's unrelated feel free to re-open 👍

[silasabbott]

I'm having this exact same issue trying to redirect to/away from my login page. @gawlk, what did you end up doing?