autoRefreshToken doesn't work

Bug report

Describe the bug

After initialising supabase client with

createClient(supabaseUrl, supabaseKey, {
  localStorage: AsyncStorage as any,
  autoRefreshToken: true
});

and setting the JWT expiry to 60 (seconds) on the supabase dashboard, the token does not refresh after 60 seconds have elapsed. Oddly enough, setting the JWT expiry to anything less than 60 triggers the token refresh but it constantly updates without waiting for expiry

To Reproduce

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

1. Setup RN project (I used expo bare)
2. Set JWT expiry to 60
3. Add supabase auth state listener
4. Sign in
5. Wait for refresh token to update (doesn’t update)

Expected behavior

The token should refresh after the expiry time set on the supabase dashboard

System information

• OS: macOS
• Version of supabase-js: 1.11.14
• Version of Node.js: 16.1.0

[b2m9]

Sorry to dig out an old issue, but are we sure this is fixed? Despite initializing the Supabase client with autoRefreshToken: true I have to double check session.expires_at and initiate supabase.auth.refreshSession() manually throughout my app. (on version 1.28.2)

There isn’t much documentation on how autoRefreshToken is supposed to work. But judging from the questions in the discussions section, I’m not the only one who is having trouble letting Supabase refresh expired JWTs.

[churichard]

Having the same issue here. I’m constantly needing to log back into my app, even though I’ve set the expiration date to be a week long and have autoRefreshToken set to true. It seems like I need to re-enter my credentials even if the token is not actually expired (i.e. I need to re-enter my credentials even though a week has not passed since the last time I did it). This happens both on localhost and on my production website.

If autoRefreshToken is true, I would expect the token to be automatically refreshed without needing to enter my credentials again. In other words, if I’ve logged in once, I should stay logged in unless I’ve explicitly logged out or cleared my cookies/cache.