supabase-auth-flow

Protect go_router routes in Flutter by wiring redirect guards that check the Supabase auth session provider. The router evaluates the authentication state before navigation, automatically redirecting unauthenticated users to the login screen and preventing access to protected routes.

Handle Flutter login and logout flows by invoking Supabase auth methods and letting the centralized Riverpod session provider react to the changes. This approach minimizes boilerplate by automatically updating the global auth state and triggering go_router redirects without manual state resets.

Access the current Supabase user data across Flutter widgets by reading the exposed currentUserProvider. This Riverpod provider derives from the underlying Supabase session provider, ensuring your UI consistently retrieves the authenticated user's profile data without direct Supabase client calls.

Your Flutter app may lose the Supabase session after a hot restart if the session provider is not properly initialized from Supabase's persistent storage. A secure auth flow restores the session by checking the initial Supabase client state before building the go_router configuration.