Xcode constantly struggles with point updates.
I have to say that’s not my experience, and I regularly exercise this case.
I do work hard to make sure that I only use supported configurations. Specifically:
-
I never install Apple internal stuff; I always stick with what we ship (or seed) to developers.
-
I don’t modify my Xcode install [1].
-
I don’t run Xcode under Rossetta.
-
I don’t mix my betas. If I’m working with an iOS beta, I have to use an Xcode beta, but I run that Xcode beta on a production macOS and target a ‘victim’ iOS device running the beta. Similarly, if I’m working with a macOS beta I install it, and its matching Xcode beta, on a victim Mac (a victim virtual Mac, if I can get away with it).
I’m not saying that there aren’t real problems out there. However, my experience is that, if we accidentally ship an Xcode with broken device support, we hear about it really quickly. It’s not the small trickle of reports I’m seeing on this thread, it’s a torrent.
Finally, the last time I waded into a thread like this I posted a sets of hints and tips for how to investigate such issues. I encourage you to:
-
Resume installing dot releases (waiting a week or so after each release to let the early adopters flush out the problems :-).
-
If you hit problems, run through those steps to try to isolate the cause.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
[1] I regularly see folks recommend copying device support directories from one Xcode to another. That is unwise.