Fix/refresh token optional #924
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Bug fix - Supabase client will ignore
autoRefreshToken
setting when setting a session with an expired access tokenBreaking Change -
Session
type now hasrefresh_token
as optionalWhat is the current behavior?
When a Supabase client is initialized with auto refresh token disabled
but a session is set with
client.setSession()
and the access token is determined to be expired the client will disregard theautoRefreshToken
setting and attempt to refresh the token.What is the new behavior?
The client will abide by the
autoRefreshToken
setting and not refresh a session if auto refresh token is disabled and the access token provided when setting the session has expired.