fix: Support custom access token #1073
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Vinzent03
changed the title
|
Thanks for this. I might not have the time to review it today, but will get to it as soon as possible! |
dshukertjr
approved these changes
Nov 11, 2024
|
@dshukertjr hi, is there any timetable that a new version of the client will be published with this fix? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
What is the current behavior?
Passing a custom access token to supabase_flutter doesn't work. I noticed that the
SupabaseClient.dispose()method didn't work with custom access token as well.What is the new behavior?
The realtime reconnection logic is moved to the
Supabaseclass andSupabaseAuthis only initialized when no customaccessTokenis passed.Additional context
close #1072