Seems like I was missing the trait: imageView.accessibilityTraits = UIAccessibilityTraitNone; That tells the system not to consider it an image and that fixes it!

Hi @eskimo Thank you for your response. So to make sure I understand the workflow: 1) My release bundle ID should match what they would use 2) From Xcode select archive 3) From the organizer select the app and pick distribute 4) pick App Store connect for method of distribution 5) Select export for destination 6) This is where I get stuck. It asks me for a certificate and profile. Is that because I need to change my project to not require signing? Or should I use my release bundle ID, cert, and profile in this process? If I need to change my project to not require signing how do I do that?

Hi @eskimo Thank you for your answer. There's even a hesitation to invite me to their team at the moment. Would it be possible to do the following: Use my own AppID and create the xcarchive, send it to them, have them replace the info.plist that's in the xcarchive with their own and distribute the app from there?

iOS and iPadOS.

I'm getting the same exact error under the same scenario...

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

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

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)

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

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.

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.

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

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.