
Hi there! I am integrating my appwrite cloud backend with FlutterFlow using REST. I can log in and use the X-Fallback-Cookies header with the session cookie to perform operations on the appwrite backend. However, looking at the docs, for the REST platform, all requests headers are authenticated with a JWT token - since these have a validity of just 15 minutes according to the docs, I would need to either stay with my current X-Fallback-Cookies implementation or retrieve new JWT tokens before every request. Even the JWT token retrieval is authenticated with the Fallback session cookie. I am afraid that with future updates the X-Fallback-Cookie method might stop working and I will get in trouble with my app. Any advice?

IMO your approach is fine for the time being. There's growing support for long-lived (custom expiry tume) JWTs which will probably be released in an update in the future. Basically, I don't think you have to worry about cookies being deprecated anytime soon. Take it with a grain of salt because I'm not on the core team
Recommended threads
- Is it possible to initialize an Appwrite...
If I provide a project repository to someone, and within that repo there is an `appwrite.json`, is it possible to initialize the project in Appwrite from scratc...
- Realtime listener does not get update wh...
listener (flutter) ``` realtime .subscribe(['databases.6882943XXXXX.tables.public.rows.main']) .stream .listen((message) { print(message); });``` ...
- Appwrite Cloud - Rows get missing on Saf...
I have opened the appwrite console on my Safari. When I go to one of my project's database and then table, there are like 600+ rows and they often fail fetching...
