alex2341355
- If the application is not used for a long time, realtime disconnected. 2.if the application goes into the background, the connection is interrupted. 3.never reconnects. you need to restart the application.
on the other hand, in the same application, socket io works perfectly. no breaks. if a break occurs, the connection is restored. for several months there is no error. Maybe you should change the realtime technology to socket io. At the moment it is impossible to use realtime.
TL;DR
Developers are facing ongoing issues with the REALTIME feature where the connection gets disrupted when the application is not in use for a long time or goes into the background. The connection never automatically reconnects, requiring a manual restart of the application. However, Socket IO in the same application works perfectly with no interruptions. Considering the successful track record of Socket IO, it might be beneficial to switch to this technology as a solution for the ongoing REALTIME connectivity issues. Recommended threads
- Realtime with multiple connections
I need the Realtime on multiple Collections for diffrent applicational logic. So my question is: Is there a way to have only 1 Websocket connection or do I need...
- i am getting 404 not found in my current...
in my current appwrite i am getting 404 not found from backend side and in frontend getting error of CORS error as backend is not working
- How to create a custom authentication sy...
I’m looking to create an Appwrite function that first verifies a client using some custom logic, like providing a secret key. Once this verification is complete...