Bug: user cookie is not set properly on callback, causing error on middleware about kinde-auth-nextjs HOT 7 CLOSED

Can be connected to: kinde-oss/kinde-typescript-sdk#59

Also, just to mention, other cookie, access token, refresh token and id token are set properly. Manually setting user cookie fixes the issue.

from kinde-auth-nextjs.

Does this happen on 2.2.3?

Last version had a dependancy update on the cookie package

from kinde-auth-nextjs.

Same thing with 2.3.3, even checked with Next.js 14.2.1. Not sure what's happening, maybe the root cause is somewhere else. As this happened for me without updating libraries. Because I worked on e2e tests, and they started to fail with this error. I was not doing any changes on Kinde, or in packages, or not touching auth stuff at all.

from kinde-auth-nextjs.

Also wondering, since all other cookies, access_token, refresh_token, id_token are set properly, then can it be issue with cookies at all? I've tried yesterday to trace the exact code, but couldn't find it. I'll try again today. Maybe for some reason user cannot be fetched from kinde and that's why only the user cookie is not set.

from kinde-auth-nextjs.

One thing interesting for me based on typescript-sdk. Shouldn't be the user object created from id_token? Like it's done here: Link and not from the user cookie?

from kinde-auth-nextjs.

Hey @50BytesOfJohn, thank you for raising. Seems like the TS SDK stopped setting the 'user' cookie. So In 2.2.5-1 I removed the dependency on the cookie and grabbed the data from the id_token instead

from kinde-auth-nextjs.

Thanks, @peterphanouvong. Resolved.

from kinde-auth-nextjs.