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.

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 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 have the exact same problem, I made a Technical Support Incident report to Apple, I hope it will get some answers.

Yeah, having exactly the same problem with simulators, Xcode 12.4 (12D4e). Have not figured out a fix yet, previously erasing content from simulator or making new simulator helped, does not seem to help anymore...

I had this problem too, it helped when you put the Info.plist file as input file to your custom build phase the "Process Info.plist" will always be executed before that phase.

I had this problem too, it helped when you put the Info.plist file as input file to your custom build phase. The "Process Info.plist" will always be executed before that phase.

Same here, it seems random as we have multiple apps published from same codebase, but with different content and styles and some of the apps go through but some of them are rejected based on this error.