
I have configured the client yet it takes a certain time for it to get initialized added a future delayed after configuration that worked but wanted a methodology that could be ideal for production level code does appwrite provide anything for this ?
TL;DR
The client takes time to initialize. Rather than initializing it on every `onInit`, it should be created once as a singleton. Use `const` to create it and use it. The `update` method's purpose is unclear, consider using `FutureBuilder` for UI updates. Slow connection could be due to daily backups. Test with Postman to see if it's also slow.
- I don't think the client should be initialised on every
onInit
.I am not sure if this isGetX
or something like that. In-fact the client should be created once afaik like a singleton. You could make it aconst
and use it, i guess? - I don't know that the
update
method does, change UI? maybe tryFutureBuilder
. Since this is also a network call and you seem to on appwrite cloud, I've heard in general forum that a slow connection could be due to daily backups or something. - Also, what happens if you try to use
Postman
or something to simulate similar network request? Is that slow too?
Recommended threads
- CRUD Operations don't work
Hey all, Create, update, and delete is not working for the Appwrite database. The database seems down. When will it be solved? As I can see from the other suppo...
- Flutter OAuth2 Google does not return to...
When the flow starts, the browser opens, I select an account, and it keeps showing: """ Page not found The page you're looking for doesn't exist. `general_rout...
- Appwrite REST API Docs in LLM-Friendly F...
Is there a version of the Appwrite REST API documentation available in a format suitable for LLM vector embedding? Specifically, I’m referring to the following ...
