Tanstack Start Server functions cookie issue
Hi, I'm having trouble getting session_data cache cookie to update when I use the auth api inside a tanstack start Server function. It is similar to next.js I think, and I have recreated a version of the nextCookies() plugin for tanstack start. problem is it works perfectly in development server, but not in vercel/netlify deployment.
can anyone confirm if they have the same issue or help? thanks!
15 Replies
Hi, i would be interested in this since it would allow me to use better-auth on the server side. Did you manage to fix the issue?
Let me know if you guys sort out server side TanStack Start for Better Auth, so I can update the starter with checks and redirects for the auth/settings page from better-auth-ui
hi @Benfa , unfortunetly I still haven't figured it out, the plugin works for dev environement but not on deployment. If you want the cookies to work you can use api routes, but so far for server actions it seems the same issue as next.js is happening. looking forward to hear any ideas to improve this.
@daveycodez sure i'll ping you if I ever fix it
hmmm i just created a plugin that might help, i got it working for my oidc issue
do you have any repo i can try this on?
@Yahya
@daveycodez do you have an example on the starter where this is failing? i'd like to test this concept
I don't do server side checks on the starter
Better Auth UI does client side check on the settings page
My Next.js starter checks cookies in Middleware but the TanStack one just uses the client side protection atm
@gib here i created a repo for you https://github.com/yahyazgour/tanstack-start-better-auth
i've included .env.example, I disabled tanstack query caching, I delayed getSession() server function by 2seconds, and I enabled better auth cookie cache, and my plugin tanstackStartCookies().
You will see in dev server, the session_data cookie gets added back on every page refresh (Set-Coookie header available), after you manually delete it.
But when you deploy this to either Vercel or Netlify, the plugin doesn't work.
@Benfa @daveycodez maybe you want to check this out as well
GitHub
GitHub - yahyazgour/tanstack-start-better-auth
Contribute to yahyazgour/tanstack-start-better-auth development by creating an account on GitHub.
let me know if you have any ideas on how to improve/fix this
thanks a lot!
@Yahya so what is the expected outcome on vercel?
to delete the session data and it not be set again?
because it works for me on vercel
using your plugin
@gib so basically when the signIn() function from the authClient finishes, it sets a cookie session_data. I delete the cookie manually, I refresh the page to invoke my custom useSession() hook (which uses the auth api instance in a tanstack server function) and normally, it should add the cookie back after I deleted it because of my plugin.
this is the exact behavior happening in dev server, but it fails to add back the cookie in vercel or netlify.
are you sure it works?
the cookies work fine with the authClient, but using the auth api object in server functions i think doesn't work, just like next.js which is why I thought of creating a plugin like nextCookies() in the first place
Yea want to try?
TanStack Start | Type-Safe, Client-First, Full-Stack React Framework
TanStack Start is a type-safe, client-first, full-stack React framework.
@Yahya
it does actually work, so the plugin is working just fine or we don't even need it? will have to test on my original setup, but this is very helpful
when i go to the network tab in my deployed version, I can't see a seperate request for getSession server function. I assumed it was because of the prefetch session im kicking in the __root loader, when it is running in the server (first load/page refresh) but in your version I can see the request. I think this is the reason why im not getting a set cookie header. can you help me figure out why? did you change anything in the setup I sent you? can you try enabling react query caching too and see if better auth cookie cache will still work?
