I have a question regarding the connect parameter (withPayload) in swift-socketIO.
Specifically, I want to know if there is any internal logic that automatically wraps the dictionary into an "auth" key when using withPayload.
then I saw an Github issue where auth information was passed using withPayload, and it worked fine.
However, when I wrap the payload with an "auth" key, authentication fails.. Without wrapping it, authentication succeeds.
I checked the internal code of swift-socketIO and couldn't find any logic that automatically wraps the dictionary into an "auth" key. Is there any internal logic in swift-socketIO that does this?
I have a question regarding the connect parameter (withPayload) in swift-socketIO. Specifically, I want to know if there is any internal logic that automatically wraps the dictionary into an "auth" key when using withPayload.
I'm trying to set the auth option during connect (like this), but couldn't find any related information in the swift-socketIO documentation.
then I saw an Github issue where auth information was passed using withPayload, and it worked fine. However, when I wrap the payload with an "auth" key, authentication fails.. Without wrapping it, authentication succeeds.
I checked the internal code of swift-socketIO and couldn't find any logic that automatically wraps the dictionary into an "auth" key. Is there any internal logic in swift-socketIO that does this?
Thank you for your assistance!