Somehow this is still an issue 5 years later. We're using client cert based authentication in our NSURLSession and finding that in some cases a 403 from the server will result in:
NSURLErrorClientCertificateRequired
It's pretty easy to prove, by just returning a 200 from the server instead and everything works (the full TLS handshake succeeds).
The fact that NSURLResponse is completely nil in a 403 and it appears that the TLS handshake is failing (when its not) is a bug that IMO should have been fixed years ago.
janders3
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Post
Replies
Boosts
Views
Activity
I also have this issue. Only solution I've been able to find is to first unpair the Apple TV from XCode. Then unpair the Mac from the Apple TV. Then restart BOTH. Then the pairing process will work.
This happens every time the Apple TV crashes. I'm currently investigating a memory issue in my application so crashes can be frequent while I debug what's going on. Unfortunately after every crash, XCode loses it's ability to deploy to the Apple TV and I have to run the steps above. Totally restarting the mac is very frustrating.