I have the exact same problem, I made a Technical Support Incident report to Apple, I hope it will get some answers.

I got a response from the support team, they wanted me to make a Feedback Assistant issue that they promised to prioritise. https://feedbackassistant.apple.com/feedback/9970709

I managed to get this fixed, in my case the root cause was a library that was distributed in binary form and had somehow managed to put extra framework searchpaths in the library configuration. The search paths were relative to the developers computer home folder so they did not work properly. There were also some extra flags that were used for their internal debugging. I managed to find the root cause by using swift-healthcheck on the debugger and comparing it to a version that did not have this problem. There is not too much information about the swift-healthcheck available currently, but you can just type it in the debugger and see the output. Debug Swift with LLDB (WWDC 2022) session had some information.

I managed to get similar problem fixed, in my case the root cause was a library that was distributed in binary form and had somehow managed to put extra framework searchpaths in the library configuration. The search paths were relative to the developers computer home folder so they did not work properly. There were also some extra flags that were used for their internal debugging. I managed to find the root cause by using swift-healthcheck on the debugger and comparing it to a version that did not have this problem. There is not too much information about the swift-healthcheck available currently, but you can just type it in the debugger and see the output. Debug Swift with LLDB (WWDC 2022) session had some information.

I managed to get similar problem fixed, in my case the root cause was a library that was distributed in binary form and had somehow managed to put extra framework searchpaths in the library configuration. The search paths were relative to the developers computer home folder so they did not work properly. There were also some extra flags that were used for their internal debugging. I managed to find the root cause by using swift-healthcheck on the debugger and comparing it to a version that did not have this problem. There is not too much information about the swift-healthcheck available currently, but you can just type it in the debugger and see the output. Debug Swift with LLDB (WWDC 2022) session had some information.