Category: Supabase and databases

CRM logs out after time: Supabase session expired

Read this guide in Polish

After a few hours or restarting the CRM card, it requires re-logging, although it had previously worked.

Why is this happening?

Access token has a limited life span, and the app must properly renew the session and respond to its lack. The problem can increase different bookmarks and incorrect customer configuration.

Step by step solution

1. Play the problem after sleeping the application and save the exact auth message, without logging in tokens.

2 . Verify whether the Supabase client uses platform-compatible refresh service.

3 . Support expire without displaying an empty list that can be confused with losing lead.

4 . After the authentication has been renewed, download the profile, role and list of eligible data.

5 . Test logout, parallel cards and change password, remembering to cancel the session.

How do I check the score?

After the active session has been retrieved, the data appears normally; when the session is actually invalid, the user is logged in without revealing the data.

Do not circumvent the problem by very long tokens or keeping administrative keys in your browser.