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

Read all. Same problems here. Debug is really slow on certain operations if i keep the ipad's wifi enabled, simple breakpoints are really really slow. Turning off wifi on ipad is faster. The problem is that I have to debug some remote api :-/ I agree with the last post: that's unbelievable.

save problem what I met. Xcode has become a fat tool which made a bad taste now. Why we can not use cable debug not choose via network, we need alternative choice.

@eskimo Are there plans to revert this change? I have not seen any reference to this on the Xcode beta update notes. Between the VPN issue and speed of the debugger, I am spending an order of magnitude more time dealing with the reliability of my tools versus being productive.

@eskimo Been strugging for months with an abysmally slow debugger in Xcode 15, and only now realized that the always-on “Connect via network” causes this issue. So much time wasted waiting for Xcode. When I turn off Wi-Fi and Bluetooth on my iOS and iPadOS devices debugger works just fine, and works A LOT faster. I wish Xcode prioritized USB debugging over network or let me disable network debugging for my devices.

Just to add my name to the list, I'm facing the exact same issues when debugging on iOS 17/Xcode15.

The app freezes at launch for a long time, waiting for the debugger. Usage is affected as well, with all the most verbose actions taking a long time to display on terminal and being rendered on screen.

Adding my voice here as well to report that Xcode 15 makes debugging sessions slow and painful, and that I wish a future release makes the debugging experience good and snappy.

On top of that, unplugging the device while a debugging session was on has triggered the nastiest iOS bug I've ever seen (twice):

1. The UI of the debugged app is unresponsive.
2. I can't go back to the Home Screen (the gesture does not work).
3. I can swipe down the notification panel, but can't switch to any other app from there.
4. I can swipe down the control center, but can't switch to any other app from there.
5. I can take a screenshot, but can't switch to any other app from there.
6. The standard shutdown (click buttons on both sides) does not work.

Basically I'm completely stuck on a unresponsive app, without any possibility to do switch to any other app.

The only solution was the very-little-known reboot gesture (short press on the sound up button, short press on the sound down button, long press on the button on the other side). This means that I had to find a computer until I could google for the solution and bring my phone back to life. And you know how phones are important nowadays.

Really not a pleasing experience, Xcode 15 :-/

Xcode15 is like shit, the experience is too bad

I have been struggling with this for months, its been like this on betas as well. I feel that there has been filed enough feedback that this could be prioritized.

Development for us has completely stopped. We need the network in order to control musical instruments. Worse, I cannot roll back my Xcode version because I am running Sonoma and Xcode 14.2 cannot be installed? Please fix.

Last week Apple published TN3158 Resolving Xcode 15 device connection issues that addresses this topic in depth.

IMPORTANT While this technote is associated with changes in macOS 14.4 and Xcode 15.3, both currently available as release candidates, installing these builds will not automagically fix all device connection problems. Read TN3158 for more backstory on this.

Because I want to separate the pre- and post-TN3158 discussion of this issue, I’ve locked this thread. If you have more to say on this subject, I’ve created a new thread for that discussion, namely Xcode 15.3 device connection issues.

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

Pre-TN3158 bugs

FB13198191 FB13203790 FB13204677 FB13208687 FB13210513 FB13211128 FB13231882 FB13246000 FB13256031 FB13267950 FB13278689 FB13350507 FB13380011 FB13474705 FB13513987 FB13601388

Revision History

• 2023-03-05 Made major changes to reference TN3158.

• 2024-02-09 Added more bug numbers.

• 2024-01-09 Added more bug numbers.

• 2023-11-09 Added more bug numbers.

• 2023-11-08 First posted.

groue wrote:

On top of that, unplugging the device while a debugging session was on has triggered the nastiest iOS bug I've ever seen

Yikes! Please do file a bug about that, per my advice above. I’m glad you found a way out of this problem. Thanks for sharing that here.

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

I can live very well with the solution that I first connect the iPhone and then start Xcode. Then the data is transferred via USB. As long as it stays that way, I'm happy.

I'll put my 2 cents in here.

This has drastically hurt development for countless people along with my own company. Install times are very slow and causing many headaches.

On top of that the following issues have shown up for me personally.

• Debugging offline functionality is completely broken.
• The apps now have to be verified by the internet before you can run them on the install device. This makes development impossible for anyone without an internet connection. The simulator is not a fallback when using hardware specific features.

Due to just those two points creating new features for a client specific app has come to a crawl. And those of us who work remotely and may lose internet are left in a state where we cannot work.

This needs to be reversed in a timely manner. There is no excuse in my mind as to why Apple would do this. The only thing I can think of is they plan on taking away the port all together, which I think is a terrible idea. It looks like many enterprise developers who are required to work under a VPN are blocked as well. Can't imagine that will look good for Apple.

Per @eskimo's comment above, I've "piled on" by submitting a Feedback Assistant bug report (FB13350507). Reiterating that I do not see how this is not an extremely high priority issue and I think that it is unreasonable to expect developers to continue working with these issues for months on end. Most notable issues stemming from this for myself and my team are:

• Debugging has become extremely slow. Breakpoints take 30-45 seconds to populate with information (such as variables in the current scope). Executing a command via LLDB takes a similar amount of time while Xcode is waiting to execute the command on the device. "Debug View Hierarchy" takes a very long amount of time as well.

• It is not possible to debug an app while a VPN is running.

• Our test devices will periodically lose connection or time out. This makes debugging a long running app session difficult if not impossible.

• Possibly unrelated, but we've noticed a spike in issues relating to code signing failures which necessitate the entire app to be reinstalled (which is particularly frustrating because Replace Container functionality is broken - see FB13253099).

None of these apply if the device is connected via USB.

+1 running apps on my phone has become such a painful and frustrating experience. I'd love to be able to disable the network connection again.