The solution I found was to make sure the following build settings were configured correctly: in Deployment section, DEPLOYMENT_POSTPROCESSING = NO for debug, YES for release. in Sign section, CODE_SIGN_INJECT_BASE_ENTITLEMENTS = YES for debug, NO for release. After setting these correctly (Deployment Postprocessing was somehow set to YES for both, I have no idea how that happened), I was able to debug again.

I should note that I still cannot get the iOS 16.X simulators to work in any fashion, they just come up as a black screen on the simulated iPhone window. The above fix just allows me to debug on iOS 15.X simulators.

After a significant amount of time digging through online forums, I found a fix that works for me. You must have the following settings in the "Build Settings" in "Deployment" section, you must have "Deployment Postprocessing" == NO for debug builds and YES for release builds in "Signing" section, you must have "Code Signing Inject Base Entitlements" == YES for debug and NO for release builds. Most of the online help fail to mention the DEPLOYMENT_POSTPROCESSING part. I have no idea how it got reset to the wrong values, it is not something I recall ever changing, but that is what was wrong with my configuration. Once I changed those 2 values to be correct, I am able to attach the debugger to the simulator and debug my apps again.

Same issue (Ventura 13.3, XCode 14.3), cannot launch any iOS 16 simulators at all - they all come up blank and never start. I can launch iOS 15.2 simulators, but cannot get debugger to attach to code running in them so kinda useless for debugging. This is super annoying and has been going on for a long time. How come nobody from Apple can see that this is a serious issue?