emitWithAck returning No ACK about socket.io-client-swift HOT 10 OPEN

@hourksavet @nuclearace
I've tested with both [String: Any] and [Any], but I'm encountering the same error

from socket.io-client-swift.

@drekka @bazza @nuclearace

from socket.io-client-swift.

Because ack is required server send an ack back

from socket.io-client-swift.

@hourksavet The server is successfully sending the acknowledgment back, as confirmed by testing in Postman.
However, there's an issue: when the request is sent from an iOS, the server-side logs do not show the parameters. Interestingly, the parameters are visible in the logs when the request is sent from Postman

from socket.io-client-swift.

@hourksavet brother please see the below image for request from postman

from socket.io-client-swift.

You set "timeout" = 1 second it too short time for sending data. Please test to increase your timeout. timeout will kill your emit thread.

Timeout it like to API request timeout

from socket.io-client-swift.

@hourksavet I increase the timeout = 20 but still getting the same error "NO ACK"

from socket.io-client-swift.

@hourksavet I increase the timeout = 20 but still getting the same error "NO ACK"

Please check your formate data to emit, is formate [String: Any] or [Any] or not
If your side follow by docs to emitWithAck, check logic ack code server side.

from socket.io-client-swift.

I am using v15.2.0 and test with v16.1.0; It working. Maybe server side do eat you.
NO ACK because your service side not call ack back.

from socket.io-client-swift.

Namespace concatenate extra comma while connecting to server namespace

from socket.io-client-swift.