What evidence exists that it's safe to call nextDrawable() on CAMetalLayer off the main thread? I have seen developers claiming that it's OK, but the official docs are silent on the topic. Attempting to do so with Strict Concurrency Checking set to Complete complains that CAMetalLayer is not @Sendable. I want to call it off the main thread since there doesn't seem to be any way to prevent it from blocking the UI for up to a second. I have read hints and allegations that this won't happen if you avoid asking for too many drawables, but that doesn't seem to be true 100% of the time in my experience. Supposing it is allowed, I wonder how races are handled such as when the layer's size is changed on the main thread, or if the layer is removed from the layer hierarchy.

I'm trying to add support for Shortcuts to my Mac app. I followed the steps here: https://developer.apple.com/documentation/sirikit/adding_user_interactivity_with_siri_shortcuts_and_the_shortcuts_app?language=objc but my app does not show up in Shortcuts. In addition to those steps, I also added my intent to (main app target) > General > Supported Intents. This had no effect. I believe that I don't need to create a separate intents extension for mac as you would on iOS. I tried that as well, but it still didn't show up in Shortcuts. This is a pure AppKit app, not iOS, not Catalyst. Is there a magic Info.plist key I'm missing? This problem is frustrating because there doesn't seem to be any way to analyze it. If you want to see what I've done it's at https://github.com/gnachman/iterm2.git in these branches: intents_extension main_app_intent

I see that Big Sur added -[NSImage imageWithSystemSymbolName:accessibilityDescription]. Unlike its iOS countertpart, there is no UIImageSymbolConfiguration that allows me to choose a different size class. Have I overlooked this? Or is it coming in a future beta?