+1 here, it's happening with multiple apps in our business account

Thanks Matt, it took us over a month to get there but your reply pointed us in the right direction. For anyone struggling with this, it turns out NONE of the work in my original post was necessary, even though it did make the errors in our Bamboo xcodebuild logs go away. THE ANSWER I had to change the bamboo launch process on our Mac mini build nodes from a daemon to an agent AND ALSO move the plist file into the Bamboo user context instead of the default System context, ex: /Users/USER_NAME/Library/LaunchAgents) instead of the system (/Library/LaunchAgents/) We were trying this with both brand new M1 and Intel nodes, and for the M1 node we also need to set up Xcode to open via Rosetta. This doesn't seem necessary on the Intel node. I cried real tears over this so I hope it saves someone else the grief!