I have seen this error when switching away from unarchiveTopLevelObjectWithData (data) to secure coding for a nested object graph. In my case the useful information came before this, because it listed types which I haven't included in my list of valid classes, like NSNumber, NSString, etc… let classes: [AnyClass] = [KBGObject.self, KBGPath.self, KBGRect.self, KBGText.self, NSString.self, NSNumber.self, NSArray.self, NSDictionary.self, NSData.self] let decodedChilds = coder.decodeObject(of: classes, forKey: CodingKeys.childs.rawValue) as? [KBGObject] Hope it helps Klaus

I have the same when using a standard toolbar item within a toolbar, and Apple Pencil hovering over it.

To answer my own question: https://developer.apple.com/support/roles/ So, indeed developers have only read access to builds, and can not add the test information when uploading a build. So, it's writing an email to an App Manager each time, who has a lot to do and has to copy the information from the devs, which usually happens way after most testers have already installed the build. This is not a good workflow, to put it mildly.

Actually, the view hierarchy is always like this, it seems to be unrelated to my issue 😕

Have you tried cmd+ctrl+click? Works fine here, same configuration on a non-US system.The ^ symbol for ctrl as shown in the contxt menu is sometimes misread for shift – yes, its not a very good symbol… and a common source of misunderstandings.That said, generally a lot of key combos on non-US keyboards get far too little attention, and a significant number of them is non-functional since years.