Alamofire实现后台下载

咔咔咔，敲完一个Alamofire的下载实现：

func downLoadFile() {
    SessionManager.default.download(urlString) { (url, response) -> (destinationURL: URL, options: DownloadRequest.DownloadOptions) in
        let docUrl = FileManager.default.urls(for: FileManager.SearchPathDirectory.documentDirectory, in: FileManager.SearchPathDomainMask.userDomainMask).first
        let fileUrl = docUrl?.appendingPathComponent(response.suggestedFilename!)
        return (fileUrl!, [.removePreviousFile, .createIntermediateDirectories])
        }.downloadProgress { (progress) in
            print("\(progress)")
        }.response { (respond) in
            print("\(respond)")
    }
}
复制代码

切到后台时，下载不继续执行，切回后，下载继续执行，后台下载的目的没有达到啊。。。 一一般规操做，目的没有达到啊，为何？确定哪里忽略了，default有木有很刺眼？看下呗

public static let `default`: SessionManager = {
    let configuration = URLSessionConfiguration.default
    configuration.httpAdditionalHeaders = SessionManager.defaultHTTPHeaders
    
    return SessionManager(configuration: configuration)
}()
复制代码

• 是SessionManager的一个单例
• URLSessionConfiguration是default模式
• 后台下载须要的模式是background

再看下SessionManager的init方法

public init(
    configuration: URLSessionConfiguration = URLSessionConfiguration.default,
    delegate: SessionDelegate = SessionDelegate(),
    serverTrustPolicyManager: ServerTrustPolicyManager? = nil)
{
    self.delegate = delegate
    self.session = URLSession(configuration: configuration, delegate: delegate, delegateQueue: nil)

    commonInit(serverTrustPolicyManager: serverTrustPolicyManager)
}
复制代码

• 第一个参数configuration的默认值仍是URLSessionConfiguration的defualt模式

这个时候咱们就须要从新配置为background模式了：

func downLoadBackground() {
    let configuration = URLSessionConfiguration.background(withIdentifier: "com.zimi")
    let backgroundManager = SessionManager(configuration: configuration)
    backgroundManager.download(urlString) { (url, response) -> (destinationURL: URL, options: DownloadRequest.DownloadOptions) in
        let documentUrl = FileManager.default.urls(for: .documentDirectory, in: .userDomainMask).first
        
        let fileUrl = documentUrl?.appendingPathComponent(response.suggestedFilename!)
        
        return (fileUrl!, [.createIntermediateDirectories, .removePreviousFile])
    }
        .response { (response) in
            print("\(response)")
        }.downloadProgress { (progress) in
            print("\(progress.fractionCompleted)")
    }
}
// 控制台打印：<1> load failed with error Error Domain=NSURLErrorDomain Code=-999 "cancelled"
复制代码

竟然报错了。。。

原来是SessionManager在downLoadBackground方法中是局部变量，进入后台下载时被释放了 改为这样

let backgroundManager: SessionManager = {
    let configuration = URLSessionConfiguration.background(withIdentifier: "com.zimi")
    let sessionManager = SessionManager(configuration: configuration)
    
    return sessionManager
}()
复制代码

URLSession的官方文档关于后台下载有四步，在Swift - 网络 URLSession中有介绍，固然不能忘了这个重要的步骤了：

func application(_ application: UIApplication, handleEventsForBackgroundURLSession identifier: String, completionHandler: @escaping () -> Void) {
    BackgroundDLViewModel().backgroundManager.backgroundCompletionHandler = completionHandler
}
复制代码

否则在控制台会打印一个警告，切回的时候也会出下卡顿

Warning: Application delegate received call to -application:handleEventsForBackgroundURLSession:completionHandler: 
but the completion handler was never called.
复制代码

那么重点来了，在用URLSession来处理后台下载的时候，须要经过urlSessionDidFinishEvents(forBackgroundURLSession session: URLSession)代理方法来执行completionHandler的回调，那么，既然SessionManager的属性backgroundCompletionHandler帮咱们保存了completionHandler这个闭包，它是怎么帮咱们来调用的呢？ 在前面贴出的init方法中有commonInit这个方法的调用，那么咱们来看下：

private func commonInit(serverTrustPolicyManager: ServerTrustPolicyManager?) {
    session.serverTrustPolicyManager = serverTrustPolicyManager

    delegate.sessionManager = self

    delegate.sessionDidFinishEventsForBackgroundURLSession = { [weak self] session in
        guard let strongSelf = self else { return }
        DispatchQueue.main.async { strongSelf.backgroundCompletionHandler?() }
    }
}
复制代码

• sessionDidFinishEventsForBackgroundURLSession代理的闭包声明里，作了backgroundCompletionHandler闭包回到主线程异步的回调
• Alamofire中有一个专职delegate的类SessionDelegate，对URLSession的代理方法urlSessionDidFinishEvents(forBackgroundURLSession session: URLSession)进行了实现

open func urlSessionDidFinishEvents(forBackgroundURLSession session: URLSession) {
    sessionDidFinishEventsForBackgroundURLSession?(session)
}
复制代码

• SessionDelegate重写了NSObject的responds方法，经过sessionDidFinishEventsForBackgroundURLSession闭包是否为空来判断是否执行urlSessionDidFinishEvents(forBackgroundURLSession session: URLSession)方法

open override func responds(to selector: Selector) -> Bool {
    #if !os(macOS)
        if selector == #selector(URLSessionDelegate.urlSessionDidFinishEvents(forBackgroundURLSession:)) {
            return sessionDidFinishEventsForBackgroundURLSession != nil
        }
    #endif
   //省略了一些代码
}
复制代码

是否是很6啊？不用咱们再写代理，也不用再写代理方法的实现了，Alamofire帮咱们省了这一步了。

像Alamofire这些优秀的框架能帮咱们省不少的代码，但咱们也不能忘了原生API的基础哦