General Info

• I installed the latest version of Supabase Kt
• I checked for similar feature requests

Feature request

Current state:

1. User is signed out and signs in with Google
2. User successfully signs in with Google and returns back to app with accessTokens, etc in the url params.
3. When supabase is loaded after redirect from Google, supabase.auth.sessionStatus will check locally stored session and will emit Unauthenticated.
4. Only after, the url params get consumed and sessionStatus becomes Authenticated

Proposition:

• Also check url params before first sessionStatus is determined on web

This will make the sign in experience smoother, especially when the UI is reacting uppon the current signed in state.