Xcode 16 Support

[waltflanagan]

Xcode 16 beta has been released 🎉

We can list some of items that may be relevant to Tuist:

• Any Xcodeproj format changes that warrant support in https://github.com/tuist/XcodeProj
• Any fixes needed to support generating Xcode 16 compatible projects
• Any Xcode 16 features Tuist can support or leverage
• Feel free to comment if you spot anything relevant and we'll consolidate / group things.

References:

https://developer.apple.com/documentation/xcode-release-notes/xcode-16-release-notes

Some of the past year lists:

• Xcode 15 Support #5221
• Xcode 14 Support #4531
• Xcode 13 Changes #3074
• Xcode 12 Support #1497

(h/t @kwridan, I totally copy/pasted this and just changed 15 -> 16)

[kwridan]

Buildable folder references

Minimize project file changes, and avoid version control conflicts with buildable folder references.

Convert an existing group to a buildable folder with the “Convert to Folder” context menu item in the Project Navigator. Buildable folders only record the folder path into the project file without enumerating the contained files. This minimizes diffs to the project when files are added and removed, and avoids source control conflicts with your team.
To use a folder as an opaque copiable resource, the default behavior before Xcode 16, uncheck the “Build Folder Contents” option in the File Inspector. (123729918)

Most likely new pbxproj update for this. Interesting things to research

• What XcodeProj / pbxproj updates are needed to support this
• Is this for Swift only, does it work for ObjC too? What about headers? 😅

[pepicrft]

This will be the most notable change that we'll have to ship in XcodeProj. We'll have to also think about what we'd like the API to look like in Tuist.

[pepicrft]

swift-testing

I'd make sure that this framework works like a charm. I assume it does, but we should double-check since developers will start using it.

[waltflanagan]

Ensuring all the new macros work correctly across tests and reports will be key.

[waltflanagan]

General Xcode beta feature request: it would be nice to expose the ability to easily incrementally adopt new Xcode features when using that version, but not expose them to older Xcodes. In this thread we discussed wanting to link against SwiftTesting only when using Xcode 16 and not when using Xcode 15. This allows tuist users to validate new functionality without having to rely on brittle, long-running branches.

[pepicrft]

Quick question! How does one opt into Swift Testing? 😬 (I haven't caught up with WWDC yet)

[waltflanagan]

It is included in Xcode 16 and just imported via import Testing. I expect it to be possible to also use it via SPM on older Xcode versions.