Xcode 14 Announced
Discover the latest productivity and performance advancements in Xcode 14. We’ll introduce you to the fully redesigned SwiftUI canvas experience, explore enhancements to code completion and navigation, and take you through performance improvements we’ve made throughout the entire development process. We’ll also show you how you can now read and respond to feedback on your TestFlight builds without ever leaving Xcode.
This looks promising, though unfortunately it’s the only version of Xcode that runs on Ventura. It was easier to get my code building than with previous updates, but there are a bunch of “Could not create compact unwind for […] register 19 saved somewhere other than in frame” compiler warnings that I don’t know what to do with.
Xcode 14 beta is significantly smaller than Xcode 13
The watchOS and tvOS SDKs are no longer bundled.
I guess they decided [Bitcode] was a bad idea. Sounded like it had a lot of promise.
I was wondering about that.
A personal favorite:
Xcode now pins elements of your code structure to the top of the editor as you scroll through a document. To toggle this behavior, use “Show: Code structure while scrolling” in Xcode’s Text Editing preferences.
This is great.
Whoever has dealt with app icons are going to be happy to hear that in Xcode 14 we can just use a single image for the app icon.
[…]
There is a new build setting
ENABLE_USER_SCRIPT_SANDBOXINGfor turning on sandboxing in shell script build phases.[…]
The platforms State of the Union mentioned Swift and SwiftUI being the future of building apps. But on the other hand, there are multiple changes happening in Interface builder as well. More options and more supported views.
[…]
As Xcode Cloud is not any more in beta, Apple is removing Xcode Server from Xcode 14.
There are three new snippets to generate boilerplate for Codable.
Previously:
Update (2022-06-10): Philip Davis:
My 3 favorite Xcode features released at #WWDC22
Update (2022-07-01): See also: Hacker News.
There was another platform i will leave nameless. They performed additional “ahead of time” type optimization after a developer submitted a binary. That layer had bugs. I personally saw them surface. Since the AOT happened transparently on the platform vendor’s machine it was very hard for a developer to test, diagnose, confirm fixed, etc. The developer still got blamed for bugs hitting the end user. That layer one can also imagine could see changes on the platform vendor’s server so something could theoretically break later on and nobody would know until the bug reports came flooding to the developer.
Because it was a goofy idea. Sounds good superficially, but ill conceived at the design stage.
Moreover, that goofiness may also be why they don’t need it anymore. It wasn’t a solid idea to begin with, so your changing requirements wind up revealing that.
Update (2022-08-29): Apple (via Damien Petrilli):
The diagram view has been removed from the Core Data data model editor in Xcode 14.
