I've noticed this as well and filed a bug report to Apple exactly 6 months ago, still without answer. It is easily reproducible with this code:         let url = Bundle.main.url(forResource: "art.scnassets/texture.png", withExtension: nil)!         plane1.firstMaterial!.diffuse.contents = url.path         let node1 = SCNNode(geometry: plane1)         node1.position.x = -5         scene.rootNode.addChildNode(node1)         let plane2 = SCNPlane(width: 10, height: 10)         plane2.firstMaterial!.diffuse.contents = SKTexture(image: NSImage(byReferencing: url))         let node2 = SCNNode(geometry: plane2)         node2.position.x = 5         scene.rootNode.addChildNode(node2)

That's great to hear. Can anybody reply to see if I receive anything?

Also happening to me. Restarting the Mac didn't help, restarting the iPad did help.

I've already filed a bug report months or years ago, I don't remember exactly, but never got a response. Why should it be up to us to keep track of what's solved and what not? After all, for some of them I get a response asking to verify if it still happens in the newest OS release, so they have a mechanism for tracking what they are working on. I don't know about you, but checking regularly if any of the thousands of bug reports that I filed have been solved would take many days (I actually did this last January, during the holidays). I would have thought that since we're helping them in finding bugs in their products it shouldn't be our burden to keep checking them. How inefficient that would be!

I think it's extremely sad that nobody at Apple wants to help me out here. Is it intended that we install official things that leave garbage around and not even the developers are keen to point out what it is, or to show that they even care about what happens to our machines after installing their software? (Yes, I submitted a bug report 1.5 years ago, in June 2020, obviously without response.)

I think it's extremely sad that nobody at Apple wants to help me out here. Is it intended that we download official installers that cannot be deleted anymore?

I’m experiencing the same issue. It’s sad that no one at Apple feels the need to give us more information about this issue.

Well, I quickly discarded that idea since as far as I know there's no way of checking at compile-time that a selector has a specific signature.

I'm having the same issue, only that I'm using $(ARCHS_STANDARD). lipo -archs only returns x86_64 and Xcode only shows the option to run the project with My Mac (Rosetta), where all my other projects can also be run on Mac and have the same architectures set.

Thank you for the workaround. Yes, this issue was solved, according to the message I got in Feedback Assistant, with iOS 14.5.1.

When running my FinderSync target in Xcode, in the debug navigator it reads "Waiting to attach". I have to manually select "Debug > Attach to Process > My FinderSync target" (listed at the top under Likely Targets). I don't understand how Apple never cared to comment on this issue, which could easily be avoided by improving Xcode, and chose to let us find this out by ourselves.

I was wondering about the same thing. The release notes for Xcode 14 say only macOS 10.13 and newer are supported, but running all my projects that have deployment target macOS 10.10 works fine. Except for one of them, the only one which has a dependency installed with Swift Package Manager, which now complains that the dependency, which got its last commit over 1 year ago, only supports macOS 10.13 and newer (this was working fine with Xcode 13).

I asked the same exact thing in Feedback Assistant 4 years ago, and they told me that they have no plans on making old macOS installers available. Apparently they have no interest in allowing developers to support older macOS systems, which, assuming that their main interest is maximizing profit from Mac sales by pushing people to abandon old Macs that don't support the software they need anymore, totally makes sense.

I'm experiencing the same warning when using a NSOutlineView without SwiftUI, but only a few rows. I opened a new topic here.

Yes, on the Mac in a sandboxed app. It succeeds.