As an update: this KEEPS happening. So far 3 times my manager had to remove my account from the apple portal and re invite me again.

I get this with the iOS simulator as well in the middle of debugging sessions which is very frustrating.

So I don't know if this will help anyone else but I was able to fix this in my project as follows - Remove the reference to the frameworks. If your frameworks are in a folder, get them out of the folder and into the same folder that contains your project file. Deleted derived data content. Re-add your frameworks. That fixed it. I don't understand why that would fix it beyond a toolchain bug affecting upgraded projects.

So I don't know if this will help anyone else but I was able to fix this in my project as follows - Remove the reference to the frameworks. If your frameworks are in a folder, get them out of the folder and into the same folder that contains your project file. Deleted derived data content. Re-add your frameworks. That fixed it. I don't understand why that would fix it beyond a toolchain bug affecting upgraded projects.

Hi all, For those still facing the issue, I'm still in the same boat. I tried the steps from the last poster before and still got nowhere. I also get this on multiple machines.

Hi, My apologies for the delay in responding. I'm all set actually: The crash log from Devices and Simulators was mentioning a third party framework. I use Cocoapods both for my main XCFramework and my demo workspace that this crash was occurring in. The problem was that the two pod files were using different versions of the same frameworks. Once I got everyone on the same framework version things worked out fine. Thanks for your help - now and in previous years and questions, more to come I'm sure. :) Ahmad

Yes. This is an excerpt from the crash log in Xcode under Devices & Simulators. Exception Type: EXC_CRASH (SIGKILL) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: DYLD 4 Symbol missing missing symbol called (terminated at launch; ignore backtrace)

Update - ran this on an Intel Mac and had the same issue.

Additional information - happens in debug and release modes, targeting simulator and device, on an Intel and M1 Mac.