我也有同样的问题。我不知道AFNetworking如何实现https请求，但对我来说，原因是NSURLSession的缓存问题。

在我的应用程序从safari跟踪回来后，然后发布一个http请求，“http加载失败1005”错误将出现。 如果我停止使用“[NSURLSession sharedSession]”，而是使用一个可配置的NSURLSession实例调用“dataTaskWithRequest:”方法如下，问题就解决了。

NSURLSessionConfiguration *config = [NSURLSessionConfiguration defaultSessionConfiguration];
config.requestCachePolicy = NSURLRequestReloadIgnoringLocalCacheData;
config.URLCache = nil;
self.session = [NSURLSession sessionWithConfiguration:config];

只要记住设置配置。URLCache = nil;。

On top of all the answers i found one nice solution. Actually The issue related to network connection fail for iOS 12 onword is because there is a bug in the iOS 12.0 onword. And it Yet to resolved. I had gone through the git hub community for AFNetworking related issue when app came from background and tries to do network call and fails on connection establish. I spend 3 days on this and tries many things to get to the root cause for this and found nothing. Finally i got some light in the dark when i red this blog https://github.com/AFNetworking/AFNetworking/issues/4279

据说iOS 12系统有漏洞。基本上，如果应用程序不在前台，你就不能期望网络调用完成。由于这个错误，网络呼叫被中断，我们在日志中得到网络故障。

我给你的最好的建议是，当你的应用从后台到前台有网络呼叫时，提供一些延迟。使调度中的网络调用具有一定的延迟。你永远不会得到网络呼叫掉线或连接丢失。

不要等待苹果在iOS 12中解决这个问题，因为它仍然没有修复。 你可以通过为你的网络请求NSURLConnection, NSURLSession或AFNetworking或ALAMOFIRE提供一些延迟来解决这个问题。欢呼:)

我在iOS 8设备上运行时也遇到了这个问题。 这里有更详细的说明，似乎是iOS试图使用已经超时的连接。 我的问题与那个链接中解释的Keep-Alive问题不一样，但它似乎是相同的最终结果。

我已经通过运行一个递归块纠正了我的问题，每当我收到一个错误-1005，这使得连接最终通过，即使有时递归可以在连接工作之前循环100+次，然而，它只增加了一秒钟的运行时间，我打赌这只是需要调试器为我打印NSLog的时间。

下面是我如何用AFNetworking运行递归块: 将此代码添加到连接类文件中

// From Mike Ash's recursive block fixed-point-combinator strategy https://gist.github.com/1254684
dispatch_block_t recursiveBlockVehicle(void (^block)(dispatch_block_t recurse))
{
    // assuming ARC, so no explicit copy
    return ^{ block(recursiveBlockVehicle(block)); };
}
typedef void (^OneParameterBlock)(id parameter);
OneParameterBlock recursiveOneParameterBlockVehicle(void (^block)(OneParameterBlock recurse, id parameter))
{
    return ^(id parameter){ block(recursiveOneParameterBlockVehicle(block), parameter); };
}

然后这样使用它:

+ (void)runOperationWithURLPath:(NSString *)urlPath
            andStringDataToSend:(NSString *)stringData
                    withTimeOut:(NSString *)timeOut
     completionBlockWithSuccess:(void (^)(AFHTTPRequestOperation *operation, id responseObject))success
                        failure:(void (^)(AFHTTPRequestOperation *operation, NSError *error))failure
{
    OneParameterBlock run = recursiveOneParameterBlockVehicle(^(OneParameterBlock recurse, id parameter) {
        // Put the request operation here that you want to keep trying
        NSNumber *offset = parameter;
        NSLog(@"--------------- Attempt number: %@ ---------------", offset);

        MyAFHTTPRequestOperation *operation =
            [[MyAFHTTPRequestOperation alloc] initWithURLPath:urlPath
            andStringDataToSend:stringData
            withTimeOut:timeOut];

        [operation setCompletionBlockWithSuccess:
            ^(AFHTTPRequestOperation *operation, id responseObject) {
                success(operation, responseObject);
            }
            failure:^(AFHTTPRequestOperation *operation2, NSError *error) {
                if (error.code == -1005) {
                    if (offset.intValue >= numberOfRetryAttempts) {
                        // Tried too many times, so fail
                        NSLog(@"Error during connection: %@",error.description);
                        failure(operation2, error);
                    } else {
                        // Failed because of an iOS bug using timed out connections, so try again
                        recurse(@(offset.intValue+1));
                    }
                } else {
                    NSLog(@"Error during connection: %@",error.description);
                    failure(operation2, error);
                }
            }];
        [[NSOperationQueue mainQueue] addOperation:operation];
    });
    run(@0);
}

您将看到我使用了一个AFHTTPRequestOperation子类，但添加了您自己的请求代码。重要的部分是调用递归(@offset.intValue+1));使该块再次被调用。

对于我来说，重置模拟器的内容和设置是有效的。 要重置模拟器，请遵循以下步骤:

iOS Simulator -> Reset Content and Settings ->按“Reset”(在iOS模拟器上) 即将到来的警告)

我们有这个确切的错误，它原来是NSURLRequest的底层HTTP实现的问题:

据我们所知，当iOS 8/9/10/11接收到一个带有keep - alive头的HTTP响应时，它会保留这个连接以供以后重用(这是应该的)，但它会保留它的时间超过keep - alive头的超时参数(它似乎总是保持连接活跃30秒)。 然后，当应用程序在不到30秒后发送第二个请求时，它会尝试重新使用可能已经被服务器丢弃的连接(如果超过了真正的Keep-Alive时间)。

以下是我们目前找到的解决方案:

Increase the timeout parameter of the server above 30 seconds. It looks like iOS is always behaving as if the server will keep the connection open for 30 seconds regardless of the value provided in the Keep-Alive header. (This can be done for Apache by setting the KeepAliveTimeout option. You can simply disable the keep alive mechanism for iOS clients based on the User-Agent of your app (e.g. for Apache: BrowserMatch "iOS 8\." nokeepalive in the mod file setenvif.conf) If you don't have access to the server, you can try sending your requests with a Connection: close header: this will tell the server to drop the connection immediately and to respond without any keep alive headers. BUT at the moment, NSURLSession seems to override the Connection header when the requests are sent (we didn't test this solution extensively as we can tweak the Apache configuration)

I was getting this error as well, but on actual devices rather than the simulator. We noticed the error when accessing our heroku backend on HTTPS (gunicorn server), and doing POSTS with large bodys (anything over 64Kb). We use HTTP Basic Auth for authentication, and noticed the error was resolved by NOT using the didReceiveChallenge: delegate method on NSURLSession, but rather baking in the Authentication into the original request header via adding Authentiation: Basic <Base64Encoded UserName:Password>. This prevents the necessary 401 to trigger the didReceiveChallenge: delegate message, and the subsequent network connection lost.