You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
From 1 week and a couple days ago, we have a problem in our application, basically, before this time, users use login with OTP normally, and have a refresh token automatically, every good.
But now, after this days, when user login with OTP, this generate a valid token, but, if they close and access app again after 1 hour, this is logged out, because the token is no more valid.
The problem is, i use Supase from 1 year, and never have this problem, i use Supabase.initialize all time on start app, and this check if the old token is valid, if not, refresh that. But now, don't work anymore.
Debbuging, i see the client.auth.session <- its comming null on app after this 1hour time.
To Reproduce
Only starts Supabase.initialiize, this generate a token in console -> put app closed in background, and re-open after a medium time, this retorn the same token (don't refresh).
Expected behavior
The token needs to be refresh when i open app again, when the old token its not valid, and goTrue Session not be null.
Screenshots
Version (please complete the following information):
On Linux/macOS
I'm using latest version of Flutter, and latest version of Supabase supabase_flutter 2.5.1.
On Windows
Additional context
I think explained all infos.
The text was updated successfully, but these errors were encountered:
gabrielviannadev
changed the title
Supabase.initialiize don't refresh token after 1h on app open again
Supabase.initialize don't refresh token after 1h on app open again
Apr 26, 2024
@gabrielviannadev I cannot reproduce this on my end, but are you able to reproduce it? Do you have reliable steps to reproduce every time, or do you see this happening only once in a while?
i am also facing the issue but i is not happening consistently but many times when app is opened after some time is gives below error and user gets sign out.
I experience the same problem on my production app - users are randomly logged out from the app. In Supabase logs, I see exactly the same log as @com8member2 included above. Please bump priority on it!
Describe the bug
From 1 week and a couple days ago, we have a problem in our application, basically, before this time, users use login with OTP normally, and have a refresh token automatically, every good.
But now, after this days, when user login with OTP, this generate a valid token, but, if they close and access app again after 1 hour, this is logged out, because the token is no more valid.
The problem is, i use Supase from 1 year, and never have this problem, i use Supabase.initialize all time on start app, and this check if the old token is valid, if not, refresh that. But now, don't work anymore.
Debbuging, i see the client.auth.session <- its comming null on app after this 1hour time.
To Reproduce
Only starts Supabase.initialiize, this generate a token in console -> put app closed in background, and re-open after a medium time, this retorn the same token (don't refresh).
Expected behavior
The token needs to be refresh when i open app again, when the old token its not valid, and goTrue Session not be null.
Screenshots
Version (please complete the following information):
On Linux/macOS
I'm using latest version of Flutter, and latest version of Supabase supabase_flutter 2.5.1.
On Windows
Additional context
I think explained all infos.
The text was updated successfully, but these errors were encountered: