Alamofire Error Domain=NSURLErrorDomain Code=-999 “cancelled”

前端 未结 5 1113
既然无缘
既然无缘 2021-01-05 14:15

I already have successfully got keychain for my token and passing it to AccessTokenAdapter class shown below. http127.0.0.1:8000/api2/projects/?format=json is passed as proj

相关标签:
5条回答
  • 2021-01-05 14:57

    This error usually caused by the SessionManager you created falling out of scope and being deinited, and your requests will be cancelled. Keep a reference to it, my solution is using a variable to store SessionManager in your APIService class

      public lazy var sharedManager: SessionManager = {
        let configuration = URLSessionConfiguration.default
    
        configuration.timeoutIntervalForRequest = 60
        configuration.timeoutIntervalForResource = 60
    
        let manager = Alamofire.SessionManager(configuration: configuration)
        return manager
    }()
    
    0 讨论(0)
  • 2021-01-05 15:06

    Just solved. Looks like it's required to set httpmethod beforehand.

        let url = URL(string: "http://127.0.0.1:8000/api2/projects/?format=json")
        var urlRequest = URLRequest(url:url!)
        urlRequest.httpMethod = HTTPMethod.get.rawValue
        urlRequest.addValue("JWT \(self.keychain["token"]!)", forHTTPHeaderField: "Authorization")
        urlRequest.addValue("application/json", forHTTPHeaderField: "Accept")
        Alamofire.request(urlRequest)
            .responseJSON { response in
                debugPrint(response)
        }
    
    0 讨论(0)
  • 2021-01-05 15:06

    In case other run into this as well as I did and it wasn't a https issue or other answer given in the many other SO posts that I found, I was getting this and found the cause to be a controller that was making a request but the controller was not to be shown. Kind of like if you have some controller that appears only on specific conditional and it, itself makes a request which is done in the viewWillAppear or other. I used a base class that determines if the call in the conditional controller should attempt the request or not. This fixed the problem for me.

    0 讨论(0)
  • 2021-01-05 15:10
    self.getSessionManager()
                     .request(urlstring, 
                              method: methods, 
                              parameters: parameters, 
                              encoding: JSONEncoding.prettyPrinted, 
                              headers: Header
                      ).responseJSON(
                             queue: nil, 
                             options: JSONSerialization.ReadingOptions.allowFragments
    ) { (responseObject) in
     // response parsing code is here
    }.session.finishTasksAndInvalidate() 
    

    Just put the method of invalidate after task finish, means session.finishTasksAndInvalidate()

    All works great.

    0 讨论(0)
  • 2021-01-05 15:12

    When you make sessionManager a let constant it won't live longer than the embracing it function, thus the session ends as soon as the manager is deallocated.

    To fix this, make sessionManager live longer. For example in my case I made it a class property:

    class NetworkRequest: {
    
       var sessionManager = Alamofire.SessionManager()
    
       ...
    
       func performRequest(_ call: APICall, customLink: String = "", parameters: Dictionary<String, Any> = ["":"" as Any]) {
    
            let sessionConfig = URLSessionConfiguration.default
            sessionConfig.timeoutIntervalForRequest = call.suggestedTimeout()
            sessionConfig.timeoutIntervalForResource = call.suggestedTimeout()
            sessionManager = Alamofire.SessionManager(configuration: sessionConfig)
            sessionManager.adapter = AccessTokenAdapter()
    
            sessionManager.request(urlString,
                          method: call.method(),
                          parameters: parameters,
                          encoding: call.chooseEncoding(),
                          headers: [:])
            .responseJSON
            { response in
              ...
            }
    

    }

    The solution might be different according to your situation, but the idea is to keep sessionManager alive until the network request ends.

    0 讨论(0)
提交回复
热议问题