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
- Sites: Auto deploy on wrong github repos...
Hello, I have kinda with UAT(testing env) and prod env. When i pull request from dev -> uat, which stands as pre-prod environment to fully test all functionalit...
- Generate CSR
How do I generate a CSR for my domain host? They are asking me to generate one for my hoosting here on appwrite
- Appwrite Push Notifications: "Unknown er...
Hi all, I'm running into an issue with Appwrite push notifications in my web project. When I try to manually send a notification to a user from the Appwrite we...