I'm seeing this as well on the macOS 13 beta. It's making it so I can't style the selection color of a NavigationList sidebar.

Can anyone show an example of how this works? The WWDC sessions doesn't show the code, and I can't get the Variation Attributes I'm adding to a system font to do anything.

I've thought this is weird too. The documentation for the origin is pretty cryptic, but the way it shrinks/scales definitely doesn't seem right. Also, just a heads up, the GKVoronoiNoiseSource seed doesn't do anything and is broken.

In Xcode Beta 6 there's a new API added to Scene: @available(iOS 14.0, macOS 11.0, *) public func handlesExternalEvents(matching conditions: Set<String>) -> some Scene Based on the doc comments I don't think this will let me limit the window count, but I'm not sure. I'll report back after macOS Beta 6 is released and I play around with it.

In Xcode Beta 6 there's a new API added to Scene: @available(iOS 14.0, macOS 11.0, *) public func handlesExternalEvents(matching conditions: Set<String>) -> some Scene Based on the doc comments I don't think this will provide the behavior I'm looking for. I'll report back after macOS Beta 6 is released and I play around with it though.

This was fixed in Xcode 12 beta 5.

Claude31, thanks for that idea. It does seem that I can use the following code to hide the New Window menu item:     .commands {         CommandGroup(replacing: CommandGroupPlacement.newItem) {       }     } Unfortunately this affects my other scenes/windows, one of which is using DocumentGroups, and needs that menu option. I've also noticed that I can't seem to customize commands per-scene/window. The last .commands block I supply is used regardless of what Scene I apply it to.

The release notes say this is fixed now.

I'm also waiting for this functionality. It's a little worrisome we're at Beta 5 and this hasn't appeared though. I don't see the example you mention in the headers, which makes me worry they removed it?

I'm still having this issue with macOS SwiftUI previews in Swift Packages. Running Xcode 12 Beta 2, macOS 11 Beta 2.

Stumbled upon this question, but I've noticed other stuff is using 10.16. Just wanted to mention in case this is blocking you.

The video materials look pretty interesting, but they look a lot more effort to create (for a developer anyway) than shaders, and less powerful. I'm happy it's something dynamic though. I really wish RealityKit had shaders and a particle system. The Entity-Component (and other APIs) are so nice, I'd love to use it for non-AR and possibly AR. But without those features, it doesn't quite match what SceneKit can do. I'll file feedback requesting the features, and hopefully others will too.

After looking more closely at https://developer.apple.com/forums/thread/651547 I realized I didn't rename or delete the default struct {Package Name} created by Xcode. After doing that, previews work on iOS/tvOS. Unfortunately they are still broken on macOS. I also tested macOS 11, with the same results. The error is still the same, something about how it can't attach to the process: HumanReadableNSError: connectToPreviewHost: Failed to connect to 4083: Error Domain=com.apple.dt.ProcessAttachUtilities Code=0 "Failed to get task for pid 4083: 0" UserInfo={NSLocalizedDescription=Failed to get task for pid 4083: 0} com.apple.dt.xcodepreviews.service (17):

Incase someone stumbles upon this, there are now design resources for all of the platforms: https://developer.apple.com/design/resources/ The macOS 11 beta UI appears to be macOS 10.15 (Catalina) UI though. Hopefully it's updated soon.

This appears to be fixed in Xcode 11.4.1. The release notes in feedback assistant say:Swift PackagesResolved IssuesFixed an issue where an error like "Swift package product A is linked as a static library by B and C. This will result in duplication of library code." was incorrectly emitted if an app and an embedded app extension or helper tool statically linked the same package product. If you previously set the DISABLE_DIAMOND_PROBLEM_DIAGNOSTIC build setting to work around this issue, you can delete this setting now. (59310009, 61227255) I wish the communication from Apple was better about things like this. Do I ask about this bug in the SPM section of the Swift.org forums? Probably not, I'd be told that Xcode issues should be posted here. But then nothing really happens. I wish we could just tag teams like @Xcode @SPM to get their attention about issues like this.Another gripe is that the Xcode 11.4.1 release notes inside the Mac App Store just say "Bug fixes and stability improvements". Why don't they at least mention to check the Feedback Assistant for the full release notes? Since the release notes in the App Store were empty, and the new iPhone SE was released that day, I figured Xcode 11.4.1 was just to add the iPhone SE simulator. It was luck that I tried compiling the project again - and dug deeper looking for actual release notes.I just feel like this could have easily been resolved before Xcode 11.4 was even released if we had a better way to communicate with people working on these tools.Anyway, thank you to everyone who offered workarounds.