don't send expired JWTs about gotrue-js HOT 8 CLOSED

+1 for this. During development I've noticed some issues where if the Chrome engine is inactive for a little bit (say, your comp was on standby) but the tab is still open, I can only assume my JWT will have expired, as I can't query rows. After a little bit, it "fixes" itself, but this is a little annoying to handle as it should be handled as part of the library.

from gotrue-js.

It's beyond annoying to always be logged out of supabase apps, including the supabase dashboard.

from gotrue-js.

I think this is fixed now with v2. Congratulations supabase team 👏

from gotrue-js.

First-time contributor here, I'd be happy to take a look at this if it's up for grabs

from gotrue-js.

Having a look now, thinking of putting the checks in SupabaseClient in the _getAuthHeaders method as a starting point to check on client initialization then opening PRs to the GoTrue, PostgREST, Realtime, and Storage clients to check per request. Would that work @awalias?

from gotrue-js.

Yeah, second this

from gotrue-js.

I am still experiencing this issue with "@supabase/supabase-js": "^2.1.4" - I have only tried locally with "supabase": "^1.24.0", not in production.

from gotrue-js.

If not fixed, with v2 there should be better behavior. We're not seeing problems on app.supabase.com or many other projects.

With supabase/postgrest-js#335 this should become even better. I'll close the issue now, do continue to comment if you have any further issues.

@cohlar Would you mind using the very latest v2 of the library. Do have in mind that if you're doing server side rendering there can be some confusing behavior that looks like this issue.

from gotrue-js.