Erik Little
Erik Little
It looks like you're expecting to get the same event that you're sending? Is that the correct API? If it is you should make sure your server is configured properly
Do you see your event getting to the engine in your logs?
I meant from the client's engine log. It would look something like `LOG SocketEngine: Got message: 451-["multipleItems",[1,2],{"test":"bob"},25,"polo",{"_placeholder":true,"num":0}]`
There's now an option when making the socket. ``` swift let socket = SocketIOClient(socketURL: url, options: [.ConnectParams(["hello": "world"])]) ```
Make sure you're only changing properties on the `handleQueue`. Any interaction with the manager/client should happen on that queue. Also, your server needs to be socket.io 3, or pass `.version(.two)`...
@olgadanylova In theory yes, but it's always a good idea to make sure you're on the same queue to avoid races. Is that error message from a debug build? Sometimes...
@olgadanylova v16 client would require `.version(.two)` to connect with a socket.io 2 server. There were some changes to engine message parsing that could cause issues like this.
It's compatible with 2.4 and 3.0+
Hm, not sure on that one. This library shouldn't need to be made binary compatible between Swift versions, since it's not meant to be distributed in binary form like the...
Sorry for missing this. Does the logs spit out something about an unknown session id?