Web app doesn't reconnect quick enough after loosing connexion

[clemlesne]

Describe the bug

If the user browser loose connection to the backend, a notification is displayed: Cannot connect to server: websocket error. But if the connexion technically come back few seconds after, the page keeps in this "stopped" state.

To Reproduce

• Open a reflex app
• Loose connexion few secs
• See that notification
• Get back the connexion right after
• See that the page stays in an errored state

Expected behavior

• The app would try quicker to reconnect (for example exponential back off caped to 5 secs, starting at 500 ms with a 1 sec timeout)
• The app would inform that it tries to reconnect (something explicit, like reconnection in progress)

Context

• Python Version: v3.13
• Reflex Version: v0.7.0
• OS: iOS
• Browser: Safari

[linear]

ENG-5447 Web app doesn't reconnect quick enough after loosing connexion

[clemlesne]

Could use PartySocket to enhance both UX and resiliency of the server connexion: https://github.com/threepointone/partyserver/blob/main/packages/partysocket/README.md.

[masenf]

Likely addressed in 0.8.12+ #5805