Socket stuck after "connecting" event #525
-
I've been trying to debug our iOS subscriptions not picking up after losing connection. Testing is done by throttling the device to 1Kbps and see the subscriptions drop. After 5 minutes, the device is set back to normal. I included logs statements on every event to see the order events are triggered and to help diagnose. The normal pattern after the initial close is: delay -> connecting -> error -> closed...(repeat) From the logs I see times where it shows: delay -> connecting...and doesn't do anything else. Here's the current web socket link setup:
I was wondering if there's a way to reactively restart the cycle if it hangs for over 30s or something. I was thinking about including a setTimeout during the connecting phase that has a function to kick off the retries, but gets reset as long as other events fire. However, don't see a way with the current API to trigger that sort of action. Side note: Even when the ping/pong picks back up, I noticed our subscriptions still don't pick back up. Thoughts? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Duplicate of #290. Check out the answer and discussion there. |
Beta Was this translation helpful? Give feedback.
Duplicate of #290. Check out the answer and discussion there.