Just had this develop on an M1 Max Macbook Pro after upgrading to MacOS Sonoma - same project, different OS.

Quinn, I can't thank you enough! I followed your directions above, and everything worked perfectly. :) I don't know if it mattered, but the Signing Certificate was set to "Development" instead of "Run Locally". What you did sounds so simple and easy, but I never hit on quite the right combination of options before. Thank you so much for helping me out. :) Jeff

Thanks so much for your help, Quinn. I so appreciate it. :) There's many types of projects that I can imagine requiring more credentials, but I tried the simplest one (a common case for me) of just a Mac app that's a command line tool. It required me to supply info I don't have, like my developer prefix, so I just made up random names, and it still created the project and it built and ran with no signing issues. The biggest challenge is when I try to run developer example projects. Those typically are designed to run on iPhone, iPad and Mac (and I modify them to turn off the iPhone and iPad parts), but they all seem to require code signing I don't have. These sample projects are how I learn the latest Mac APIs, so being able to use them is important. Are they expected to automatically run, or is it expected that you go into them and change their information? I'm willing to pay for an official developer account, but I somehow doubt that will solve the problem? Thanks again, Jeff

Perhaps it would be useful to list the exact code signing build settings required to develop a Mac App with a Personal Team on XCode 13.3? Much appreciated. :)