Re: anyone have any work arounds for Error 57 : "Socket is not connected" since iOS 10
Re: anyone have any work arounds for Error 57 : "Socket is not connected" since iOS 10
- Subject: Re: anyone have any work arounds for Error 57 : "Socket is not connected" since iOS 10
- From: "Quinn \"The Eskimo!\"" <email@hidden>
- Date: Wed, 08 Feb 2017 08:27:00 +0000
On 7 Feb 2017, at 23:11, Howard Shere <email@hidden> wrote:
> Subject: anyone have any work arounds for Error 57 : "Socket is not connected" since iOS 10
57 is a BSD Sockets error, `ENOTCONN`, so you’re unlikely to see it being returned by a high-level HTTP[S] API. I suspect the high-level API is giving you `NSURLErrorNetworkConnectionLost`, in which case you can find my advice in QA1941 “Handling “The network connection was lost”.
<https://developer.apple.com/library/content/qa/qa1941/_index.html>
It’s very likely that iOS 10 and friends have a bug that’s causing this to occur more frequently than before; that’s still being investigated under the aegis of <rdar://problem/29464993>, the bug mentioned in that DevForums thread, and others. If you see this more frequently on iOS 10 than iOS 9, you should definitely file your own bug about that. If you can include a packet trace [1] and a CFNetwork diagnostics log [2], that’d be grand.
Share and Enjoy
--
Quinn "The Eskimo!" <http://www.apple.com/developer/>
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
[1] QA1176 “Getting a Packet Trace”
<https://developer.apple.com/library/mac/#qa/qa1176/_index.html>
[2] QA1887 “CFNetwork Diagnostic Logging“
<https://developer.apple.com/library/ios/qa/qa1887/_index.html>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden