Hi there,
I'm using the latest version of react-stomp 4.1.1,
Lately, I've encountered an issue to keep WebSocket messages coming through onMessage,
but I found that after the network connection is resetting, whether because I switched WIFI network, or just lost WIFI connection for a couple of seconds - the onMessage won't be triggered anymore.
Just to clarify - the socket itself does re-connect after the connection lost, I can see the heartbeat and the incoming messages in the network tab (chrome developers tools), but as I said - the onMessage did not trigger, although the messages did come.
any thoughts what can cause it, or how can I solve it?
Hi there, I'm using the latest version of react-stomp 4.1.1, Lately, I've encountered an issue to keep WebSocket messages coming through
onMessage
, but I found that after the network connection is resetting, whether because I switched WIFI network, or just lost WIFI connection for a couple of seconds - theonMessage
won't be triggered anymore.Just to clarify - the socket itself does re-connect after the connection lost, I can see the heartbeat and the incoming messages in the network tab (chrome developers tools), but as I said - the
onMessage
did not trigger, although the messages did come.any thoughts what can cause it, or how can I solve it?
Thanks!