This is the correct answer and the reason that NSURLSession really came into existence - there is a need to partition behaviors between different frameworks and

This is the correct answer and the reason that NSURLSession really came into existence - there is a need to partition behaviors between different frameworks and subsystems and the previous NSURLConnection model relied on a smattering of process global configuration options. I'd be surprised if AFNetworking didn't also offer the ability to create a "private" NSURLSession with custom storage objects. I'd also recommend looking into debugging these types of issues using, eg, Charles Proxy. There's more information on logging at: https://developer.apple.com/library/content/qa/qa1887/_index.html https://developer.apple.com/library/content/qa/qa1887/_index... See also: https://developer.apple.com/videos/play/wwdc2013/705/ https://developer.apple.com/videos/play/wwdc2013/705/ Disclaimer: NSURLSession contributor...