This is so crazy. Is it normal to have the "Disable Library Validation" option turned on? Is it best practice? It's the only way I can get my little CLI app to build after I included swift-argument-parser. Seems like there's some incongruity with the security policy and with using SPM. I certainly don't want to hate developing on Apple's platforms, but everything that has happened since the Swift announcement, every year, there's more and more little paper cuts you have to dance around in order for things to just get out of your way so you can do some actual thinking and building. I really, truly, do not want to have such a negative attitude, but I'm sitting here wondering how this is even an oversight. I'm sitting here wondering if I should be building this as a web app just to avoid this mess. In any case, checking that option to on allows the cli app to build and run.

I'm running into the same problem referencing that same WWDC video. I have ensured that: App intents file is included in the target The intent is added to the Supported Intents section of the target/General tab There's only one copy of my app on disk using the handy command Peter posted above. The only copy listed is the build in /Xcode/Derived-Data/... The app builds and launches cleanly, and I see the intent code getting generated in the compiler log, but I still cannot find my shortcut in the shortcuts app. This is a fresh AppKit-Swift MacOS app, not much else to consider in terms of complications.