useSession() and getSession() are supposed to extend expiresAt right?
Calling useSession() on the client or getSession() on the server is supposed to extend the session expiresAt if past updateAge correct? I cannot for the life of me get it to extend. I'm checking returned data and the DB itself.
Sveltekit - 2.28.0
expiresIn: 4 * 60
updateAge: 30
Running local.
I've tried:
Better Auth 1.0.0, 1.2.12, and 1.3.6
Calling useSession() on the client
Calling getSession() on the server with headers properly passed
With and without cookieCache enabled
With and without sveltekitCookies plugin (BA 1.3.6)
With and without customSession (https://github.com/better-auth/better-auth/issues/3713)
With and without disableCookieCache query parameter
I've read and understood all the Doc Concepts pages on the website
I've followed the sveltekit integration guide (https://www.better-auth.com/docs/integrations/svelte-kit)
Removed all plugins for potential interference
What am I missing??
I feel like I'm going crazy....
GitHub
customSession with cookieCache enabled not returning Set-Cookie hea...
Is this suited for github? Yes, this is suited for github To Reproduce Setup auth with customSession plugin and cookieCache enabled Perform getSession from client side Check the response headers Cu...
SvelteKit Integration | Better Auth
Integrate Better Auth with SvelteKit.
1 Reply
hey, mind opening a Github issue for this?