Error Domain=NSURLErrorDomain Code=-1005 “The network connection was lost.”

前端 未结 30 2973
悲哀的现实
悲哀的现实 2020-11-22 05:51

I have an application which works fine on Xcode6-Beta1 and Xcode6-Beta2 with both iOS7 and iOS8. But with Xcode6-Beta3, Beta4, Beta5 I\'m facing network issues with iOS8 but

相关标签:
30条回答
  • 2020-11-22 06:28

    I was getting the error on an iOS 7 device when I was using Xcode 6.2 beta.

    Switching back from Xcode 6.2 beta to 6.1.1 fixed the issue, at least on an iOS 7 device.

    0 讨论(0)
  • 2020-11-22 06:29

    If the problem is occurring on a device, check if traffic is going through a proxy (Settings > Wi-Fi > (info) > HTTP Proxy). I had my device setup to use with Charles, but forgot about the proxy. Seems that without Charles actually running this error occurs.

    0 讨论(0)
  • 2020-11-22 06:29

    On 2017-01-25 Apple released a technical Q&A regarding this error:

    Apple Technical Q&A QA1941

    Handling “The network connection was lost” Errors

    A: NSURLErrorNetworkConnectionLost is error -1005 in the NSURLErrorDomain error domain, and is displayed to users as “The network connection was lost”. This error means that the underlying TCP connection that’s carrying the HTTP request disconnected while the HTTP request was in progress (see below for more information about this). In some circumstances NSURLSession may retry such requests automatically (specifically, if the request is idempotent) but in other circumstances that’s not allowed by the HTTP standards.

    https://developer.apple.com/library/archive/qa/qa1941/_index.html#//apple_ref/doc/uid/DTS40017602

    0 讨论(0)
  • 2020-11-22 06:31

    Restarting the computer fixed the issue for me with Xcode9.1. I had restarted the simulator and Xcode, it doesn't work.

    0 讨论(0)
  • 2020-11-22 06:31

    I was having this issue for the following reason.

    TLDR: Check if you are sending a GET request that should be sending the parameters on the url instead of on the NSURLRequest's HTTBody property.

    ==================================================

    I had mounted a network abstraction on my app, and it was working pretty well for all my requests.

    I added a new request to another web service (not my own) and it started throwing me this error.

    I went to a playground and started from the ground up building a barebones request, and it worked. So I started moving closer to my abstraction until I found the cause.

    My abstraction implementation had a bug: I was sending a request that was supposed to send parameters encoded in the url and I was also filling the NSURLRequest's HTTBody property with the query parameters as well. As soon as I removed the HTTPBody it worked.

    0 讨论(0)
  • 2020-11-22 06:32

    Opening Charles resolved the issue for me, which seems very strange...

    Charles is an HTTP proxy / HTTP monitor / Reverse Proxy that enables a developer to view all of the HTTP and SSL / HTTPS traffic between their machine and the Internet. This includes requests, responses and the HTTP headers (which contain the cookies and caching information).

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