
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
- File tokens regenerate each page reload
Hello, on appwrite 1.7.4, when I create a file token via the API Tokens(appwriteAdminClient)#createFileToken I get a secret, then when I check in the console t...
- CSV Import Shows Success but Data Not Ap...
I tried importing a CSV file into my PRODUCTS collection. The dashboard shows the message “Import to PRODUCTS completed successfully,” but no data appears in th...
- [FEATURE] Better usage analytics for app...
Recently, i've gotten **73** emails from appwrite regarding excesive GBHours usage. I've almost hit the limit of 1000 and it is really hard to track down which ...
