Looks like it is possible to work around this by adding a firewall exception for both XCode and the simulator; see the answer I just posted.