On 1.3.7
I am using the Flutter package connectivity_plus: ^6.0.1
I can get it working real well initially - it "auto detects" if there is an internect connection without having to poll it and then it will "automagically" make a callback if there are changes to the network.
Now, my real purpose for using it is to get an initial signal if connectivity has changed and then check if a realtime connection is still intact (be it trying to write to part of the document to trigger the message updates or something else).
The strange thing is that once I initiate that realtime connection, doing connect/disconnect no longer triggers Connectivity Plus.
As for the realtime connection, I'm 100% sure I got it working (could receive updates to a document) but turning off the network doesn't trigger any onError or onDone callback. It doesn't trigger even after I remove Connectivity Plus.
How do I reliably and efficiently handle network disconnects in the case of the realtime connection?
Recommended threads
- 1.6.2 to 1.7.0
Hi everyone. I am running a self-hosted Appwrite server on version 1.6.2. What is the safest way to migrate to the next version? Should I update directly to...
- Exception: Route not found when calling ...
I have self-hosted v1.8.1 and I am using an Appwrite function with node-appwrite v22. When I call the createVarcharColumn() in my server function I get this exc...
- Document created without ID in console
Hi team, I’m experiencing an issue in the Appwrite console. When I create a document in a collection via the **Collections UI**, the document gets created **wi...