Socket disconnects automatically and after disconnect it's not reconnect. Get lots of logs in console.

[bhautikmobileappdev]

I tried to reconnect but got following logs

Got event: statusChange, with items: Optional([SocketIO.SocketIOClientStatus])
Got event: reconnect, with items: Optional(["Ping timeout"])
Got event: reconnectAttempt, with items: Optional([-1])
Got event: statusChange, with items: Optional([SocketIO.SocketIOClientStatus])
Got event: statusChange, with items: Optional([SocketIO.SocketIOClientStatus])
Got event: reconnectAttempt, with items: Optional([-2])
Got event: statusChange, with items: Optional([SocketIO.SocketIOClientStatus])
Got event: statusChange, with items: Optional([SocketIO.SocketIOClientStatus])
Got event: reconnectAttempt, with items: Optional([-3])
Got event: statusChange, with items: Optional([SocketIO.SocketIOClientStatus])
Got event: disconnect, with items: Optional(["Got Disconnect"])
Got event: error, with items: Optional(["Session ID unknown"])

Please check and let me know if i did anything wrong.

Thanks in advance.

[nuclearace]

Can you provide more detail? What version are you using on the client/server, what configs are used, server settings (ping info.)

[bhautikmobileappdev]

@nuclearace

pod 'Socket.IO-Client-Swift', '10.0.1'

[kinza88]

Hey.. did you get any solution to this problem?
@nuclearace @bhautikmobileappdev

[ambrose40]

Same problem for me I constantly get "Session ID unknown" error:
My Podfile:

source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '8.4'
use_frameworks!
target 'Votecast' do
pod 'Socket.IO-Client-Swift' # Or latest version
pod 'Fabric'
pod 'Crashlytics'
pod 'MBProgressHUD'
pod 'PNChart'

end

My SocketIO swift class:

import Foundation
import SocketIO
@objc public class SocketProvider : NSObject {
    
    let str = "https://dev.votecast.dk/" //Prod server
    
    var descr = "SocketProvider class"
    var socket : SocketIOClient
    var manager : SocketManager

Init of Socket Manager:

        self.manager = SocketManager(socketURL: URL(string: str)!, config: [.log(true), .connectParams(["user_id": id])])
        self.socket = manager.defaultSocket
        self.socket.on("connect") {data, ack in
            
            let dict = [["sid":self.socket.sid]]
            
            loggerHandler(dict, "connected")
            print("socket connected")
        }

When I try to connect using forceWebsocket I get: "Invalid HTTP upgrade" socket error and connection drops abruptly.
When I switch to default configuration or forcePolling I get:
2018-01-03 17:39:46.374430+0200 Votecast[38357:921519] LOG SocketEnginePolling: Got poll message: 97:0{"sid":"9Ln0tyN13zNfDQx_AAnx","upgrades":["websocket"],"pingInterval":25000,"pingTimeout":15000}

I attach both logs to this comment.
socket_io_swift_13_1_websocket.log
socket_io_swift_13_1_default.log

[nuclearace]

@bl82 I'm not sure, there's a lot going on in your logs. What kind of connection management are you doing. I see a lot of manager being released and client being released messages.

[ambrose40]

@nuclearace Here is my full code for connection management:

    @objc public func connectSocketIOSimple(loggerHandler: @escaping (Array<Any>?, NSString?) -> Void) {
        self.manager = SocketManager(socketURL: URL(string: str)!, config: [.log(true), .forceNew(true), .connectParams(["user_id": id])])
        self.socket = manager.defaultSocket
        
        self.socket.on("connect") {data, ack in
            
            let dict = [["sid":self.socket.sid]]
            
            loggerHandler(dict, "connected")
            print("socket connected")
        }
        
        self.socket.on("reconnect") {data, ack in
            
            let dict = [["sid":self.socket.sid]]
            
            loggerHandler(dict, "connected")
            print("socket connected")
        }
        
        self.socket.on("user connected") {data, ack in
            print(data)
        }
        
        self.socket.on("disconnect") {data, ack in
            self.manager.reconnect()
            
            print("socket diconnected")
        }
        
        self.socket.on("error") {data, ack in
            self.manager.reconnect()
            print("socket error")
        }
        
        self.socket.on("chapter.update") {data, ack in
            print(data)
            loggerHandler(data, "chapter.update")
        }
        
        self.socket.on("event.update") {data, ack in
            print(data)
            loggerHandler(data, "event.update")
        }
        
        self.socket.on("event.transition") {data, ack in
            print(data)
            loggerHandler(data, "event.transition")
        }
        
        self.socket.on("chapter.transition") {data, ack in
            print(data)
            loggerHandler(data, "chapter.transition")
        }
        
        self.socket.on("chapter_member_status.update") {data, ack in
            print(data)
            loggerHandler(data, "chapter_member_status.update")
        }
        
        //New events handlers
        
        self.socket.on("event.started") {data, ack in
            print(data)
            loggerHandler(data, "event.started")
        }
        
        self.socket.on("event.stopped") {data, ack in
            print(data)
            loggerHandler(data, "event.stopped")
        }
        
        self.socket.on("event.restarted") {data, ack in
            print(data)
            loggerHandler(data, "event.restarted")
        }
        
        self.socket.on("chapter.vote.started") {data, ack in
            print(data)
            loggerHandler(data, "chapter.vote.started")
        }
        
        self.socket.on("chapter.vote.cancelled") {data, ack in
            print(data)
            loggerHandler(data, "chapter.vote.cancelled")
        }
        
        self.socket.on("chapter.vote.completed") {data, ack in
            print(data)
            loggerHandler(data, "chapter.vote.completed")
        }
        
        self.socket.on("chapter.approve.started") {data, ack in
            print(data)
            loggerHandler(data, "chapter.approve.started")
        }
        
        self.socket.on("chapter.approve.cancelled") {data, ack in
            print(data)
            loggerHandler(data, "chapter.approve.cancelled")
        }
        
        self.socket.on("chapter.approve.completed") {data, ack in
            print(data)
            loggerHandler(data, "chapter.approve.completed")
        }
        
        self.socket.on("chapter.values.reset") {data, ack in
            print(data)
            loggerHandler(data, "chapter.values.reset")
        }
        
        self.socket.on("chapter_member.update") {data, ack in
            print(data)
            loggerHandler(data, "chapter_member.update")
        }
        
        
        self.socket.connect()
    }

[ambrose40]

@nuclearace I am not sure as well, it was working in just before I returned to develop new feature and updated from cocoapods, let me know, what I can investigate further? it is a blocker for me right now. feature I was working on is done, but during testing sockets no longer communicate properly. btw I was running test from simulator.

[ambrose40]

@nuclearace server is set to both transports:

transports: [
            'websocket',
            'polling'
        ]

And version of Socket IO on server is 2.x

[nuclearace]

So the error event shouldn't need a reconnect call, if something breaks the connection it should automatically reconnect. Beyond that, I'm not sure, I haven't been able to reproduce this. So a sample server/client that shows the issue happening would help.

[ambrose40]

@nuclearace Hmmmm.... Magic happened. I don't know how guys I am working with set up their server connection. Nobody notified me of any changes there, neither before the event nor today. But currently connection and sockets are working perfectly! And correctly switching between polling and websockets 👍 Although I did pod deintegrate and pod install again, switching to previous version 13.0.0, and when I found out that it is working just fine, I tried to reproduce the issue and did one more pod deintegrate and pod install again with 13.1.0 version, after that it worked like charm! 🥇

[nuclearace]

Very strange. I wonder if it was some server or networking issue.