Socket.connect() is not consistent when using connectParams with JWT

I'm using https://github.com/auth0/socketio-jwt to connect the user to my node.js/socket.io server and I'm using one round trip

My problem right now is that whenever user logs in on the IOS part, the socket.connect() is not consistent, my theory is that the token is not yet ready even before the socket.connect() gets invoked.

I'm using Singleton design for my Socket.io class as many people pointed that out.

Here's the code on the SocketManager.swift part

import SocketIO  class SocketIOManager: NSObject {      static let sharedInstance = SocketIOManager()     var socket = SocketIOClient(socketURL: URL(string: mainURL)!, config: [.log(false), .compress, .connectParams(["token": getToken()])]) // getToken() I got it from other file which is Constant.Swift      func establishConnection() {         socket.connect()     }      func closeConnection() {         socket.disconnect()     }    } 

I'm using KeychainAccess to store the token and Constant.Swift file store all the global variables and functions so that I could call it on any Swift files.

Constant.Swift

import Foundation import KeychainAccess  let keychain = Keychain(server: "www.example.com", protocolType: .https)  func getToken() -> String {     if let token = keychain["token"] {         return token     }     return "" } 

LoginViewController.swift

 @IBAction func facebookButtonClicked(_ sender: UIButton) {        Alamofire.request("/login", method: .post, parameters: parameters, encoding: JSONEncoding.default)             .responseJSON { response in                 if let value = response.result.value {                     let json = JSON(value)                      self.keychain["token"] = String(describing: json["token"])                     SocketIOManager.sharedInstance.establishConnection()                      self.segueToAnotherVC() // Segue to another screen, to simplify things i put it in a function                 }         }   } 

So technically what is happening in this controller is, when the user logs in, I will store the token into KeychainAccess (it is equivalent to NSUserDefaults), then only I will make a socket connection because the socket connection needs a token beforehand.

What should I do to make the connection consistent all the time, whenever user logs in? Any methods that I could use?

0 Answers

If You Enjoyed This, Take 5 Seconds To Share It

• Facebook
• Twitter
• Google+
• StumbleUpon
• Digg
• Delicious
• LinkedIn
• Reddit
• Technorati