
This has happened to me with NextJS and SvelteKit.
I'm following the code from https://appwrite.io/docs/quick-starts/nextjs and what I see in the user's session, is that the expire
parameter is set to yesterday while on Appwrite I have the session length of the 365 days
What is happening here?

What do you mean yesterday? The year is 2024

Oh, you're right 🤦♂️ In that case, why is it that on hard reload the cookie isn't kept?

what makes you say that?

checking the cookies storage on the browser and seeing that the cookie for the login is not longer there

can you share a screenshot of what you're seeing?

I also wonder if timezones make a difference, take the timestamp and convert it to your local timezone?

Ok, so I had the functions on the .server file and that was the issue. Moving them to .page made them work. Wondering if there would be a way of still using Svelte’s form actions and send the cookie via the result to store it on the client side

you may need to look into Appwrite SSR techniques. For example, you can look at https://svelte-kit.ssr.almostapps.eu/
Recommended threads
- Stuck in "deleting"
my parent element have relationship that doesnt exist and its stuck in "deleting", i cant delete it gives me error: Collection with the requested ID could not b...
- Help with 409 Error on Relationship Setu...
I ran into a 409 document_already_exists issue. with AppWrite so I tried to debug. Here's what I've set up: Collection A has 3 attributes and a two-way 1-to-m...
- Database Double Requesting Error.
I am getting error for creating new document in an collection with new ID.unique() then too getting error of existing document. When button is pressed one docum...
