while working on #39 I noticed a problem with the current auth implementation
Current implementation:
when user signs in, they are authenticated with supabase, for which they receive an access and a refresh token which is saved in storage
(Note that, supabase is using the token when making the following requests after that)
when the user closes and opens the app back again, it sees that it already has the tokens in the storage, so it decides not to authenticate again.
(Note that, supabase is not authenticated in this session)
when the requests are made which uses user's context, they now fail as user is not authenticated.
while working on #39 I noticed a problem with the current auth implementation
Current implementation:
access
and arefresh
token which is saved in storage (Note that, supabase is using the token when making the following requests after that)Possible solutions: