You were signed in a minute ago. You refreshed the page, opened a second tab, or clicked around as usual — and now you are on the login screen. The console says Invalid Refresh Token , Refresh Token Not Found , or the client throws Auth session missing! .
This is one of the most searched Supabase auth errors around Lovable, Bolt, Vite and other apps that use supabase-js . Usually the session was revoked, or the client is holding a refresh token the server no longer accepts.
Below are the checks I would run, in order. Everything here is taken from the User sessions guide, the Auth error codes table, the server-side Auth advanced guide , and the PKCE flow page, all read on 8 November 2026.
What a session actually is
A session starts when a user signs in. Supabase represents it with two values: a short-lived access token (a JWT; most apps should keep the default expiry of 1 hour) and a refresh token.…