IOS Auth header Support

[mohammadfahadrao]

I'm using sockets in android to have a connection between backend(node js) app and my android app.

I'm successfully able connect to socket by passing auth header like

 mSocket = IO.socket(uri, IO.Options().apply {
                // Pass the authentication details using 'auth'
                auth = mutableMapOf<String, String>(
                    "api_key" to "key here",
                    "app_id" to "os-dev"
                )
            })

Since backend is expecting in auth.

this is working fine for android but on ios swift i'm unable to do so. I don't want to switch to query params as i'll have to change backend code and that is not in my reach.

Does swift not at all support auth header?

there is another web and react native example with which i was able to successfully connect.

const socket = io('https://backend.com', {
  auth:{
    api_key:'dddasdas',
    app_id:"stidev"
    }

});

This works on web version of my app and in react native android as well

[Mike-Animal-Counseling]

Swift supports this. In your JavaScript example, auth is the Socket.IO CONNECT payload, rather than an HTTP header. The Swift equivalent is connect(withPayload:):

let manager = SocketManager(socketURL: URL(string: "https://backend.com")!)
let socket = manager.defaultSocket

socket.connect(withPayload: [
    "api_key": "your-api-key",
    "app_id": "os-dev"
])

Keep manager alive, for example as a property on the object that owns the connection. Register your event handlers before calling connect.

Those values reach the existing Node server as socket.handshake.auth.api_key and socket.handshake.auth.app_id, just like your working JS client. You don't need to move them to query parameters. .extraHeaders(...) and .connectParams(...) would send them in different places.

The API is documented here, and the released v16.1.1 client forwards the payload through the manager's CONNECT encoder. If your installed Swift package doesn't expose this method, check its version first.

AI-assisted. Checked against the Swift source and an equivalent CONNECT packet sent to a local Socket.IO 4.8.1 server; this wasn't an iOS runtime test.