Thankfully, shortly after writing the above, I found a working solution. Inside your app project (that wants to use shared SwiftUI views) you cannot use folder references or create "new group without folder" that will contain the shared items. Instead, I created a regular group inside my app project (just for organization). Then, dragged in the shared views/items. File system: IIKit Views IIAboutView.swift MyApp MyApp.xcodeproj MyApp IIKit + Views (note that this folder is empty; doesn't contain a copy of the IIKit items) Xcode main window: MyApp IIKit Views IIAboutView.swift (location of this is the "real" IIKit shared folder items) MyApp Views ... Completely non-intuative. Going to file a bug since in all my trials, the shared code resides in the same location on disk. Xcode should have worked with either folder references are when placing the shared items inside folders created with "new group without folder".

Just stumbled upon this myself. I know I have recently created fresh projects and set the deployment to 14.0. I want to say it was with earlier Xcode 12.x versions? Anyhow, I haven't done any testing with such a setting, but you can select 'Other' and type in a version. e.g. 14.0 or 12.0 Still, it's curious as to why Apple is hiding those initial versions. Perhaps those OS versions are not recommended to have anymore? e.g. enough serious issues found where they are hoping developers will just target the dot versions instead. Just a guess. For me, I'll just pick 14.1 for my new projects. By the time I'm done, iOS 15 release will be right around the corner. For iOS 12.0, I see no problems in requiring 12.1 or even 12.3. The quantity of iOS 12 years is very small and for those that cannot update past 12.x, I would assume they'd probably at least be applying all the security and other updates.

Thanks for finding that highlighting issue, BabyJ. You're correct in that it appears that when initially presented, an alert or action sheet will not be using the proper accent for the button normal states. But during interaction, the accent is then used. I have created a sample Xcode project showing the issue and filed feedback: FB8994751