fix(auth): use project ref as namespace for storing token #430
Conversation
This file contains hidden or 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
dshukertjr
reviewed
Jun 28, 2024
No, it migrates the token to the new key: https://github.com/supabase/supabase-swift/pull/430/files#diff-6132ac0f2c100e8db5a2725259009c843e6dff71e699aadfcdf61f4b01c00192R30-R40 |
grdsdev
force-pushed
the
fix/auth/project-ref-as-namespace
branch
from
db41ada to
fa64559
Compare
dshukertjr
approved these changes
Jun 28, 2024
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?
When using multiple projects, for example, a dev and a production, both environments shares the same token.
What is the new behavior?