Invalid refresh_token error if JWT expiry happens while sat idle in app
Hi all
I've got a github issue open here but reposting here in case anyone has any ideas...
Long version: https://github.com/supabase/supabase-js/issues/628
Short version: After moving to supabase-js v2 I'm seeing that if my JWT expires while sat idle in the app, I get 400 errors and console messages saying 'Invalid refresh_token', I'm not sure if this is a bug, expected behaviour, or if I've done something wrong. Full details are in the github issue...
I only noticed this as I dropped my JWT expiry right down to a 5-mins in order to do some testing on returning users with my changes for supabase-js v2 when I noticed this.
Cheers
Gary
I've got a github issue open here but reposting here in case anyone has any ideas...
Long version: https://github.com/supabase/supabase-js/issues/628
Short version: After moving to supabase-js v2 I'm seeing that if my JWT expires while sat idle in the app, I get 400 errors and console messages saying 'Invalid refresh_token', I'm not sure if this is a bug, expected behaviour, or if I've done something wrong. Full details are in the github issue...
I only noticed this as I dropped my JWT expiry right down to a 5-mins in order to do some testing on returning users with my changes for supabase-js v2 when I noticed this.
Cheers
Gary
GitHub
Bug report Describe the bug I have a Vue 3 SPA using Pinia and Vue Router. I use signInWithOtp as my auth method. I recently updated to supabase-js v2 and everything seemed fine at first but I noti...
