Fix · Supabase and databases

"JWT expired" or user logged out suddenly

Not checked against the vendor's current screens

What you may see

After some time requests fail with JWT expired
The user must sign in again too often

Most likely cause

The login token is short lived and must be renewed; the renewal does not happen, because the session code is missing or the cookie is lost.

Check first (about two minutes)

Does it fail after about an hour, or right away?

The fix prompt

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

The exact error or what you see

What you did before it happened

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a careful senior engineer who knows Supabase (database, login and file storage) and explains it to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

Menu and button names change over time. If you cannot find a button or page I mention, say so and tell me what to look for instead of guessing.

THE PROBLEM
"JWT expired" or user logged out suddenly

THE EXACT ERROR OR WHAT I SEE
[paste the exact error here]

WHAT I DID BEFORE IT HAPPENED
[write in a few words what you did before it happened]

MOST LIKELY CAUSE
The login token is short lived and must be renewed; the renewal does not happen, because the session code is missing or the cookie is lost.

DO THESE STEPS, IN THIS ORDER
1. Check how the app creates the Supabase client and whether automatic token refresh is on.
2. For a server-rendered app, check the session refresh runs in the proper place (middleware or the documented helper) and cookies are written back.
3. Handle the expired case with a clear message and a way to sign in again.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- After waiting beyond the token time, a request still works without signing in again.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not make tokens last forever.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Check how the app creates the Supabase client and whether automatic token refresh is on.
For a server-rendered app, check the session refresh runs in the proper place (middleware or the documented helper) and cookies are written back.
Handle the expired case with a clear message and a way to sign in again.

Do not do this

Do not store tokens in places other than the library's own storage.
Do not make tokens last forever.

Try another entry