I've been struggling with making the ws extension reliable on mobile browsers. I am testing with my iphone. I put some debug code in the extension to write to the DOM when the socket close and error events are fired and this does not always happen when the browser loses and gains focus. I though I'd raise this issue in case anyone else has experienced it and knows of a work around.
I've been struggling with making the ws extension reliable on mobile browsers. I am testing with my iphone. I put some debug code in the extension to write to the DOM when the socket close and error events are fired and this does not always happen when the browser loses and gains focus. I though I'd raise this issue in case anyone else has experienced it and knows of a work around.
I think it is related to this: https://stackoverflow.com/questions/75869629/ios-websocket-close-and-error-events-not-firing although the events do generally fire for me but not always, so sometimes the software thinks the socket is still open but actually it is no longer operating.