site_archiver@lists.apple.com Delivered-To: macnetworkprog@lists.apple.com On 15 Jun 2018, at 18:16, Jens Alfke <jens@mooseyard.com> wrote:
at what level does the simulator connect to the host Mac?
That’d be option (a), that is, it connects at the system call level. This has two important consequences: * You can’t test code that affects the TCP/IP, like Network Extension providers * You don’t get the user-space TCP/IP stack that’s present on iOS 11 and later Outside of the TCP/IP stack there are other differences: * Wi-Fi level code, like `NEHotspotHelper` and `NEHotspotConfigurationManager`, can only be tested on a real device. * HTTPS trust evaluation is done inside an iOS-style security daemon but there are places where that behaves differently than a real device (for example, when dealing with revocation). Having said that, my experience is that for run of the mill apps that use `NSURLSession`, testing on the simulator is very effective. Share and Enjoy -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40lists... This email sent to site_archiver@lists.apple.com