To be clear, TLS connection failures are not all the fault of ATS; ATS adds extra security checks on top of:
Both of these can fail independently of ATS.
You can check whether a TLS connection failure is related to ATS by turning off ATS for your entire process. To do this, remove any
NSAppTransportSecurity
you have and add one that contains just
NSAllowsArbitraryLoads
. If that fixes the problem, you need to look to ATS. OTOH, if the problem persists, you need to look lower.
Oh, and btw, to answer your direct question, I’m not aware of any ATS (or lower) changes that might trigger this change of behaviour in 10.1. The ATS changes that I know about — which are designed to make ATS behave as its documented to behave — are coming in 10.2. See this thread for more info.
Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
let myEmail = "eskimo" + "1" + "@apple.com"