Socket io server v4 and swift client 16.0.1

[JimmyBjorklund]

Hi We have a socket io server running v4 but the swift client cannot connect. Is this expected? The server accepts connections from android and node justfine. We have allowEIO3: false on the server. The swift client get the upgrade message but after that nothing happens.

Thanks for any help. /Jimmy

[vandadnp]

Same thing here, this is quite a dealbreaker for us

[nuclearace]

Yes I’m looking into this. A new version should be coming soon

[vandadnp]

@nuclearace hi. Do you have any updates on this please?

[vandadnp]

@nuclearace hi there again. Do you have any updates on this please?

[vandadnp]

@nuclearace any updates on this would be really helpful. thank you for your efforts and time

[vandadnp]

@nuclearace hi again, since 20 days have gone by, I thought to ask you for some pointers as to where the bug lies and we could try to solve it ourselves and send a PR to you if that would help?

[Sadmansamee]

We really stuck on this :(

[vandadnp]

@Sadmansamee agreed, we too. The state of this repository is quite alarming. We are ready to help fix this ourselves but absolutely zero communication so far from @nuclearace unfortunately

[darrachequesne]

Hi everyone! I was not able to reproduce the issue: https://github.com/socketio/socket.io-swift-fiddle

Am I missing something? Could it be a version mismatch?

[JimmyBjorklund]

No we use the lates on the backen and the latest of this client should work without the allowEIO3, this work great for node clients and android its only the swift client that is not working.

[JimmyBjorklund]

Hi everyone! I was not able to reproduce the issue: https://github.com/socketio/socket.io-swift-fiddle

Am I missing something? Could it be a version mismatch?

You ar missing to set the options: this.io = new SocketIO.Server(httpServer, { path: path, allowEIO3: false });

[vandadnp]

@darrachequesne have you seen the above message from @JimmyBjorklund ?

[Pic2490]

@darrachequesne have you seen the above message from @JimmyBjorklund ?

I downgraded my NodeJs SocketIO version to 2.4.0 and it worked

[darrachequesne]

@JimmyBjorklund hmm, that's weird, on the server side:

• allowEIO3 defaults to false (doc)
• path defaults to "/socket.io/", which is the same value as the client here (doc)

That being said, the path must match on the server and the client. Are you using a custom path?

@Pic2490 please check the compatibility table here: https://github.com/socketio/socket.io-client-swift/blob/master/Usage%20Docs/Compatibility.md

[rouzbeh-abadi]

The swift client issue is still not fixed, and adding .connectParams(["EIO": "3"]) doesn't help that. Should we wait for an update?

[Ryce]

Wow, I spent the last 2 days pulling my hair on this one. And downgrading both iOS and Node to EIO3 solved the issue...