Has something changed in how to write macOS Action Extensions since 10.15? In a text editor supporting Action Extensions, as as Text Edit, you could select text, and a small menu indicator would present itself. Activating it, you'd see a list of Action Extensions you could invoke. Since 10.15 and currently on 11.2, this still is the case, except every Action extension is disabled (greyed out) on the menu, including the More… option. Example image (remove the space): https: //imgur.com/F2ehj82 My own app's Action Extensions, when run in 10.14 and earlier, compiled in Xcode 12, still work fine, but produce a menu similar to the image on 10.15 and 11.x. The sample image, incidentally, uses Apple's own sample project available here - https://developer.apple.com/documentation/appkit/app_extensions/add_functionality_to_finder_with_action_extensions, with a couple of Action Extensions added as I try to troubleshoot this issue. The "Convert Text to Upper Case" extension is untouched, and the other two I've added from Xcode's "new target" button, also untouched. This is not a case of these being incompatible; they wouldn't be in the menu if that were the case, and in any case I can see in Console when other extensions are rejected for the menu or approved for the menu. One of the tests even uses TRUEPREDICATE, so, really, it's not an activation rule (speaking of which, they're enabled in System Preferences). This also doesn't appear to be specific to my machine, as I've spun up default VM's with stock 10.15 and 11.0 installs. Sometime's Apple's documentation and samples are out of date, so I've also combed github for other Action Extensions, but I can't see that anyone is doing anything different. They're there. They're detected as being compatible. They're in the menu that pops up. They menu is simply disabled. What's going on here? Do Action Extensions on selected text in NSTextField simply no longer work?

Is there a known issue with the value binding being missing from NSButton in Xcode 12? Here's the Bindings Inspector shown an a fresh NSButton (top image), and shown on an existing button that probably goes back to Xcode 9 or so: (Hmmm, I can't link to imgur, but you might see an example at their domain plus this top-level path: /a/tElLv9I) What's worse, when I modify the existing button in most ways, the binding to value breaks completely. NSButton 0x7fb233f965d0 valueForUndefinedKey:]: this class is not key value coding-compliant for the key value. Even more worse, if I delete the binding, close the nib, and re-open it, then there's no way to re-add the value binding to a button that had been already working. The Cocoa Bindings Documentation - https://developer.apple.com/library/archive/documentation/Cocoa/Reference/CocoaBindingsRef/BindingsText/NSButton.html#//apple_ref/doc/uid/NSButton-SW1 indicates that the value binding isn't deprecated and should still be supported. Did I miss a fundamental breaking change somewhere?

I'm using the latest and greatest Xcode: Version 11.2.1 (11B500). When I add a properly built and tested xcframework to a project -- even a new, empty project, either iOS or macOS -- There's no disclosure triangle to reveal the contents of the xcframework.Is it just me, or is this happening to others? I'm trying to determine if this is a bug, id-10-t error, or working as intended.When I look at the WWDC2019 "Binary Frameworks in Swift" video, I see that there's a disclosure triangle for Harlan's "FlightKit.xcframework" and other tutorials with screenshots show the same.I know I can browse the headers in BBEdit, but it's kind of PITA to leave the environment.Any ideas?Postscript: latest and greatest public release of Catalina, too: 10.15.1 (19B88), and occurs on three different computers of mine.