You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user logs in on my application, data correctly sends out data.user and data.sesssion. However, after switching pages, data.session changes to NULL. I tried all methods, asked the supabot assistant for help, changed cookies options and still doesn't store well... I'm hoping this is a bug because I'm struggling hard X)
To Reproduce
On a NextJS 15 application, with Pages Router, install SSR by following the official guide for setting up SSR with Auth on the official Supabase website. Now, log on to an account and log the data.session between pages. After the initial login, you should get all data (data.user and data.session) and after that, data.user should still be stored and data.session should be empty.
Expected behavior
Data.session should store between pages and actions.
System information
OS: Windows 11
Browser: Firefox
"@supabase/supabase-js": "^2.47.8"
Node version : v21.6.2
The text was updated successfully, but these errors were encountered:
Bug report
Describe the bug
When a user logs in on my application, data correctly sends out data.user and data.sesssion. However, after switching pages, data.session changes to NULL. I tried all methods, asked the supabot assistant for help, changed cookies options and still doesn't store well... I'm hoping this is a bug because I'm struggling hard X)
To Reproduce
On a NextJS 15 application, with Pages Router, install SSR by following the official guide for setting up SSR with Auth on the official Supabase website. Now, log on to an account and log the data.session between pages. After the initial login, you should get all data (data.user and data.session) and after that, data.user should still be stored and data.session should be empty.
Expected behavior
Data.session should store between pages and actions.
System information
The text was updated successfully, but these errors were encountered: