- 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
- RealtimeResponseEvent Typescript Bug
Hello, could you please fix RealtimeResposneEvent, the one in realtime.ts have timestamp: string, but the one in client.ts have timestamp: number, and it causes...
- Realtime Docs are outdated
The Realtime docs are outdated.
- Fine grained permissions for webRTC hand...
Hi, I am building a WebRTC P2P app for a university project and have hit a security limitation regarding permissions for anonymous users. The Architecture: We ...