The answer to the first is straightforward: iOS 17 has new debugging infrastructure such that all debugging goes over the network. That’s not the same thing as going over Wi-Fi. If you have the device attached via USB, the network requests will go over a virtual network interface running over USB. When changing anything that impacts standard workflow, Apple should clearly state that at WWDC. I missed the Appleseed for IT presentation (if there was one), but was it mentioned there? Which brings us to the the second issue: Why is this slow? This seems to only affect some folks. If it were affecting everyone, there’d be a lot more activity on this thread |-: Now I think you have your answer: everyone is affected! When this was the case during the beta testing during the summer, I attributed this issue to the beta itself and although annoyed, ignored it hopping for the final release to fix it... I'm working with about 80 iOS devs in our team and EVERYBODY with iOS 17 devices can't deploy apps since our Macs are isolated on the network (stealth mode with VPN). My colleague had a call two days ago with someone at Apple after we reported that through our Apple Care Enterprise program. It has been escalated, but I wonder if that will help since it's a corporate decision... (And no, the issue is not the VPN providers as I've read Apple is replying to some customers) I have done a lot of testing on an iPhone 15 Pro (not MDM managed) connected to my personal MacMini M1 (repeated deploy of the same app "NIPeekaboo" Apple sample code, never ran clean folder as I don't want compiling affecting the results): When wifi is activated on the phone and not connected with cable, it takes in average 15.0" to deploy (median: 11.53") When wifi is activated on the phone and plugged in with the USB-C cable, it takes 11.53"" to deploy and the median is 9.6". Sometimes I even get an error (timeout or "could not attached to device"). When I switch off wifi, it takes in average 5.03" to deploy the same app (median: 2.7"). (The first try got a "Preparing..." so it took 17", otherwise constantly about 2.6") So clearly, as long as wifi is activate, with or without cable it takes 250% more time to deploy an app (9.6"-2.7"/2.7 x100). Bored of: "Message from the debugger: Xcode has killed the LLDB RPC server to allow the debugger to detach from your process. You may need to manually terminate your process" "Timeout while connecting to remote device." (domain: com.apple.mobiledevice. Code: -402652910) -> Radar sent to Apple FB13246000. "Browsing on the local area network for XXXXX, which has previously reported preparation errors. Ensure the device is unlock [of course it is!] ans attached with a cable or associated with the same local area network as this Mac [yes it is]. The device must be opted into Developer Mode to connect wirelessly [again, yes it is!]" Caching symbols take about 25-30 minutes with iPad Pro attached over USB-C. (So process started over WiFi then I attached cable but nothing changed, still very slow). Same here. With each update it took roughly 25 minutes to collect the symbols. Next time I'll switch wifi off to force debugging through the cable, I will certainly gain a factor 10 in transfer speed. I hope my feedback with countless others will be sent to Apple for direct actions. I don't see any benefit for us developers to use debugging through wifi as it has been demonstrated being 250% slower than with cable on an iPhone 15 Pro. Hence please revert that "new debugging architecture" to one that is similar to iOS16's and its predecessors. As an engineer we use to say: why changing something that works? (Here I get the feeling Apple tries to force gathering information of the surrounding devices connected through wifi. Sorry if that's how I feel. As many have already express here: please give us the choice to activate the "connect via network". Don't force us.)

Same for me. Feedback sent: FB10202371 Hope they fix it in the next beta.