I have had the same problem since the Xcode 15 betas last summer. Network debugging is a beautiful idea, but in practice there are too many variables, and for some of us it's not an option. Eg we are required to use VPNs which route everything and don't allow local traffic, or other network configurations that get in the way. Network environments are just too varied for a one-size-fits-all approach. I agree with those calling to revert this to the prior opt-in requirement for network debugging. And Xcode should prefer a usb connection if both are available. (We've indicated a preference by going to the trouble of plugging the thing in.) As a workaround, I have to disconnect the device from usb, then pull down control center on the device and disable wifi. Then plug in the device and Xcode connects over usb. Then I can reenable wifi. Repeat ad nauseam multiple times a day.

We had a similar issue. Turns out we were calling dequeReusableCellWithIdentifier: to create a cell in another method which we used for size estimates, and it seems like on ios 18 the UICollectionView really does not like that. If you deque a cell it expects you to give it that cell, eg in response to cellForItemAtIndexPath. Changing that other cell creation to just alloc/init fixed the crash for us. Try "self.collectionNameCell = [ .... alloc] init];" instead of deque.

No. PIE is only for executables (Position Independent EXECUTABLE). It won't show up on a framework, only the final binary in .ipa. The linker will ignore the option, it's not valid on a library type. https://github.com/aosm/ld64/blob/master/src/ld/Options.cpp#L3437-L3440

I'm getting an intermittent error when compiling storyboards. "error: Internal error. Please file a bug at feedbackassistant.apple.com and attach "/var/folders/kv/...." The workaround that I've found is that when it barfs, do "killall SWBBuildService" and restart the xcode build without cleaning the build folder. Then it's usually ok until it has to rebuild the storyboard. Lather rinse repeat. Please file feedback.

This is still an issue when building with Xcode 26 beta 5. https://feedbackassistant.apple.com/feedback/17929506