You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When signing into a Supabase app on macOS via a 3rd party auth provider, Supabase does automatically store tokens in the users's keychain. That's very welcome, so I don't have to handle this task myself.
However, when calling supabase.auth.signOut(scope: .local), those entries are not cleared and the user is immediately signed in again after the app has been restarted.
Since the Supabase automatically stores credentials in the keychain upon sign-in, I expected it to clear out those entires automatically when signing out.
Is this a bug, or are my expectations out of place?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When signing into a Supabase app on macOS via a 3rd party auth provider, Supabase does automatically store tokens in the users's keychain. That's very welcome, so I don't have to handle this task myself.
However, when calling
supabase.auth.signOut(scope: .local)
, those entries are not cleared and the user is immediately signed in again after the app has been restarted.Since the Supabase automatically stores credentials in the keychain upon sign-in, I expected it to clear out those entires automatically when signing out.
Is this a bug, or are my expectations out of place?
Beta Was this translation helpful? Give feedback.
All reactions