Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

WebSocket connection failed error after inactvity

See original GitHub issue

If I lose internet connection for an extended period of time after opening a WebSocket and then come back to my app, I get the error shown below. Immediately after the error, my socket onerror() listener is called followed by onclose(). That seems right to me, but I feel like there shouldn’t be a fatal error on the app. I would just re-connect the socket in this situation.

I am on the iOS Simulator for an iPhone 5 running React Native 0.22.2.

simulator screen shot 7 apr 2016 15 14 47

Issue Analytics

State:
Created 7 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

2reactions

igoldencommented, Jan 3, 2017

+1 Happening to me now with large background requests to API

0reactions

afilpcommented, Sep 8, 2016

+1 Can you please reopen this? It happens to me too. I am in “DEBUG” mode on an actual device and when the iPad sleeps then it shows this message when I turn it on. This is quite disturbing, if it could be fixed it would be good. Thanks!

Top Results From Across the Web

WebSocket connection failed error after inactivity #8302 - GitHub

Hi there! This issue is being closed because it has been inactive for a while. But don't worry, it will live on with...

WebSockets in Chrome and Firefox Disconnecting After One ...

It seems like if sockets are disconnected by the server after one minute of inactivity that would apply to IE and Edge just...

Troubleshooting connection issues | Socket.IO

You are trying to reach a plain WebSocket server · The server is not reachable · The client is not compatible with the...

Get rid of that annoying “WebSocket connection to '…' failed ...

The module was not inactive. Finally, through further source code poking, I discovered there's a static public method called Jetpack:: ...

Client WebSocket disconnects when browser is minimized or ...

The fix: ... 1. disable the feature "Intensive throttling of Javascript timer wake ups" in Chrome or, 2. change the web-transport inactive-timeout ......