Code Monkey home page Code Monkey logo

Comments (7)

Crysis21 avatar Crysis21 commented on June 9, 2024

I am facing the same issue. I did the configuration similar to socket.io on android, but I can't connect.

from socket.io-client-swift.

Crysis21 avatar Crysis21 commented on June 9, 2024

@muk-y use this

       var config = SocketIOClientConfiguration()
        config.insert(.extraHeaders(["authorization" : "Bearer \(token)"]))
        config.insert(.path("/socket.io/"))
        config.insert(.useCustomEngine(false))
        config.insert(.forceWebsockets(true))

from socket.io-client-swift.

nuclearace avatar nuclearace commented on June 9, 2024

@Crysis21 are you able to test with the latest development branch? I'm having trouble reproducing on that branch. Screenshot shows server upgrading from polling to WS
Screenshot 2024-03-19 at 12 07 37 PM

My basic test code:

func connectSocket() {
    socket.connect(withPayload: ["hello": "world"])
}

manager = SocketManager(socketURL: URL(string:"http://localhost:8087/")!, config: [])

socket = manager.defaultSocket

connectSocket()

from socket.io-client-swift.

muk-y avatar muk-y commented on June 9, 2024

@muk-y use this

       var config = SocketIOClientConfiguration()
        config.insert(.extraHeaders(["authorization" : "Bearer \(token)"]))
        config.insert(.path("/socket.io/"))
        config.insert(.useCustomEngine(false))
        config.insert(.forceWebsockets(true))

I don't have the useCustomEngine property in Socket.IO-Client-Swift 15.2.0. Which version has the property? I have used all the codes besides useCustomEngine but the error is still the same.

from socket.io-client-swift.

TannazParsa avatar TannazParsa commented on June 9, 2024

@muk-y did you find any solution?
I have the same issue

from socket.io-client-swift.

vkhadyka avatar vkhadyka commented on June 9, 2024

I have the same issue on the latest version of the library.

from socket.io-client-swift.

muk-y avatar muk-y commented on June 9, 2024

@muk-y did you find any solution? I have the same issue

I passed my parameters through string concatination instead of using connectParams. This solved my issue.

from socket.io-client-swift.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.