It turns out, I needed to add @executable_path/../Frameworks to the "runtime search paths" in the executable I'm trying to invoke with NSTask.

It appears related to an error: NSLocalizedDescription=exportOptionsPlist error for key "method": expected one of {}, but found development

My situation is different but similar. I am building a Mac app that invokes a command line utility using NSTask. I am also building the command line utility. So I have it set up as a dependency and copied into my app bundle as an auxillary executable into the MacOS folder and then I locate it using NSBundle and run it with NSTask. If this executable is present, then the kind of Archive that is created when I "Archive" does not work with App Store Connect and Xcode Cloud fails. But if I remove the executable, Xcode Cloud builds and it creates the kind of archive that works with App Store Connect. And voila, it works with Xcode cloud. But alas, without that executable the app won't actually work. So unless Apple wants to support auxiliary executables invoked in this manner in Xcode cloud, I have to change how I'm building and deploying my app to work differently than it currently does. Or else build with Jenkins.

I also tried going to the Testflight tab in App Store Connect and did not see Xcode cloud builds appear there, nor did I see a way to select them from there.

So it turns out that there is something in the workflow you add as an action/post action to integrate with TestFlight users. I was finally able to get it to work after adjusting some settings related to code signing and adding the ITSAppUsesNonExemptEncryption key to my Info.plist file.

Eventually three builds happened which is the number I triggered using git push. I just needed to be more patient.