-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Subscribe socket error at 2 message #42
Comments
Error in console: nw_socket_handle_socket_event [C1:1] Socket SO_ERROR [54: Connection reset by peer] |
I suspect this is a duplicate of #39 - @alexkite03, what version of Xcode/Swift toolchain are using? One of the "effects" of #39 is that msgID is not read (or parsed right for that matter) from the subscribe ack and the socket hangs open waiting for the ack with expected msgId to be received, however server drops the socket after a while, since the ack has been sent and delivered, but never acted upon. |
Hey @kervich, I'm seeing the same issue on Xcode 11 Beta (11M336w) on macOS 10.15 Beta (19A471t). |
Hello, I'm also experiencing the same issue ("[connection] nw_socket_handle_socket_event [C1:1] Socket SO_ERROR [54: Connection reset by peer]") where the connection is closed after successfully receiving the first message; if I don't send messages, pings are regularly received without never closing the connection. Anyone found a workaround? EDIT: Someone did!, the commit 0b3256f works like a charm. |
Hi,
I can't receive more than 1 message without disconnection (Socket error)
What is the correct way to suscribe to a topic?
This is my code:
https://pastebin.com/ad1D8P4w
The text was updated successfully, but these errors were encountered: