Xcode 15, how to uncheck "Connect via network" for physical device?

Could [data security type software] interfere with Xcode/the virtual network when an iPhone is connected via USB causing connection and slowness issues?

That’s certainly a possibility. In cases like this I recommend that you work with your IS department to try to isolate the cause. For example, you could set up a test Mac with none of your IS software installed, verify that Xcode works, then add your IS software one item at a time, repeating the Xcode test each time.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

All respect eskimo, but "working with your IS department" is not a feasible solution for those of us that work in large companies. Using a VPN is a very common requirement for corporate work, and intentionally breaking that workflow is a slap in the face to those of us in the corporate world that are passionate about iOS development.

I'm hopeful that Apple sees this and walks back this requirement.

To Apple devs/support/product: As it's been several months since this issue has been open and still gaining traction, how do we get the ball rolling here to get this addressed? Does your team not have enough bug reports/logs to work with? If so, please let us know and we can provide the needed artifacts. How do we, the corporate iOS dev community, escalate the importance of this issue to your product/business team?

If there are any traffic rules to config in VPNs to allow the connection to iOS devices, please let us know. There must be something Apple is doing internally to make this work with your corp VPN.

I have the same issue even on the latest Xcode and I'm just freelance dev working in coworking places or hotels. I have to keep turning off wifi (which is annoying and not a solution) on my phone to force using USB. On top of that I have to turn off my mullvad VPN on macbook so that xcode can then connect via USB. This whole thing drives me nuts and completely kills any enjoyment of coding in Xcode. Wish Apple listen to their dev community and just roll back previous way even for time being until their figure out what's wrong. Still I prefer to having control of forcing USB - this is the most reliable and fastest way especially if someone working on hotel wifi. WIFI should be only used as fallback if device is not connected by wire. Together with other issues in Xcode I have (debugger broken and I constantly I have to clean project to make it work) wastes too much of developer time...

I'm experiencing a similar issue when I plug my iPhone with iOS 17 into my MacBook Pro and build a run.

My app hangs on the launch screen for a long time (~10 seconds) then once the app UI shows up, it's unresponsive to touches for about 20 seconds.

If I turn wifi off on my iPhone while it's plugged in, it works as I expect it to work: fast build and run, quick launch screen, and instantly responsive once past the launch screen.

However, turning off wifi is not ideal, because if I don't have good cell service it's hard to test my app (which requires internet). Ideally I'd like to be able to build and run at plugged-in speeds when my iPhone is plugged into my computer, even when I have wifi turned on on the iPhone.

I have a test iPhone with iOS 16, and I have connect via network enabled for that device. That devices works as expected: when I have it connected via a cable, it builds and runs quickly, and is instantly responsive to touches when the app starts, like I'd expect. Even when I don't have a cable connected, it takes a little longer to install, but then it starts right up with quick launch screen, and responds to touches immediately, unlike on my iOS 17 device.

I don't have a VPN installed on my iOS 17 device or my MacBook Pro.

It would be great to be able to build and run at a normal speed on iOS 17 devices with wifi enabled again. Hopefully someone on the Xcode team will fix this issue soon! 🤞😢

If I disable Wifi and Bluetooth on the device and connect it to the MacBook via cable, it works fine. However, Apple engineers claim that it should use Cable over the Wifi debugging if it is already connected, which is not True. As soon as I turned Wifi & Bluetooth back on and reconnected my phone with cable, it again chose wifi, and Debugging became so painful. :(

Waiting a solution. This issue its really annoying.

Same thing here...since I started using Xcode 15.. debugging has been a nightmare. Really surprised this still hasn't been fixed, we are at 15.2 version now.

I just tried the solution for https://forums.developer.apple.com/forums/thread/744083 and this fixed the issue for me. Initial investigation and it doesn't seem to matter if I have flight mode on or off. Cable connection is working.

@eskimo This is likely to remain a more annoying problem on Vision Pro where binary sizes could be larger and there is no hardware connection on the consumer device. What's the right feedback categorization for requesting a purchasable connector?

@eskimo As one commented above pointed out, deleting /Library/Developer and letting Xcode redownload everything fixes the problem. It did that without much expectation as I figured I had nothing to lose, and launching my projects with the debugger attached is once again lighting fast.

Same here, Apple SW still not in favour of developers....

Same here

For Apple Vision Pro, the USB-C developer strap can now be purchased via this page: https://developer.apple.com/visionos/resources/

I guess I'll chime in with a "me too" reply. I would like to uncheck the box to Connect via Network. I investigated reverting back to Xcode 14. Of course, Apple blocks you from easily running Xcode 14 on macOS 14, and it's not easy to downgrade macOS or iOS. If you run the Xcode executable directly a couple times, it will run ok, but it will say it's missing DeviceSupport for the iOS 17 device. Apparently, Apple has stopped using the DeviceSupport folders, so there's nothing available in Xcode 15 to copy from to enable iOS 17 support. I found the new method for DeviceSupport is "CoreDevice". If you defaults write a special flag on the CLI, it will tell Xcode 14 to use CoreDevice. And that must be part of the problem, because once it's trying to run with CoreDevice, it fails to connect to the iOS device while on VPN, just like Xcode 15.