The original question is not about opening apps in general but about opening the container app. Countless apps use 'openURL' for this, because 'completeRequest' does not open the container app.

This seems to be improved or fixed in macOS 15 beta 4. Hopefully some other SF Symbol 6 bugs will be solved too, so I can fully use and test the new rotation feature.

You can create max 1000 custom record zones in a private CloudKit database. This limit is active since 2016, before that you could create an unlimited number of record zones. The number of records within a record zone is unlimited.

I managed to add a resizeable NSTextField to NSToolbar with the following code: let item = NSToolbarItem(itemIdentifier: .titleItem) /* Or any other identifier */ let field = NSTextField() /* Do not use one of the new initialisers! */ field.isBordered = false /* This is essential */ field.lineBreakMode = .byTruncatingTail item.view = field

This problem seems to be solved in macOS 15.1 beta

The release version of SF Symbols 6 is now available, but it is still not possible to export rotatable symbols. The export file misses the 'Can Rotate' property and the anchor point. For me it is totally unclear why the app contains fancy controls to set the anchor point, mark layers as rotatable, but without the possibility to export this.

This answer may be helpful: https://forums.developer.apple.com/forums/thread/763246

It seems that this bug has been fixed in SF Symbols 7 beta.

The badge property is now available since beta 3. Unfortunately it's quite useless for me because the background color is hardcoded red.

The heavy blur may be caused by the backgroundColor of the UIPageViewController, which is default black. Changing that to another color may fix the problem, at least that did it for me.

I see the exact same weird class name in a 'purple' warning message when running one of my projects: Attempting to unarchive Swift class 'AppKit.NSScrollPocket.(unknown context at $19bd29ed8).BackdropView' with unstable runtime name '_TtCC6AppKit14NSScrollPocketP33_EC3F85FAB7755D56E669206D2B17725B12BackdropView'. The runtime name for this class may change in the future, leading to non-decodable data. You can use the 'objc' attribute to ensure that the name will not change: "@objc(_TtCC6AppKit14NSScrollPocketP33_EC3F85FAB7755D56E669206D2B17725B12BackdropView)" If there are no existing archives containing this class, you should choose a unique, prefixed name instead: "@objc(ABCMyModel)" The purple error line is on instantiation of a Storyboard. I have no idea which element in the Storyboard is responsible for this warning, which makes it hard to make an example project for a Feedback. Do you see the same kind of warning or something completely different?

Thanks for your reply! My question concerns only the UIToolbar. It works indeed as expected in a UINavigationBar. So Apple don't want us to use badges in the UIToolbar for whatever reason or it is a bug.

At my side it turns that removing a NSTouchBar from the Storyboard 'solves' the problem in two completely different projects. Unfortunately I didn't succeed yet in making a clean example project that proves this for a Feedback, so apparently the problem is NSTouchBar and something else.

I manage to reproduce it with a fresh Xcode project. Adding a NSTouchBar and NSOutlineView to a Storyboard was sufficient to get the weird runtime warning. FB19543241

The runtime warning (not error) I see, seems indeed to be caused by one or more NIBs that contains the infamous _TtCC6AppKit14NSScrollPocketP33_EC3F85FAB7755D56E669206D2B17725B12BackdropView class reference. Compiled storyboards results in a collection of NIBs, and I saw a few that contains each 2 references to said weird class. After removing the NSTouchBar objects from the storyboard, the resulting NIBs only contained 1 reference, without causing a runtime warning. If Apple doesn't solve this runtime warning then I think I just ignore it until it's solved or when I can give up support for NSTouchBar.