Seeing this for our app. FB9970868

@Cibergato I would recommend that you raise a radar with Apple and leave feedback. Without feedback and simply returning the machine may not prompt them to fix this. It seems no one's comparing compilation times on these macs - everyone's raving about their GPU and Video rendering performance (every reviewers is a video editor, go figure). No suggestion would help - Mac Studio is just slow and not an iota faster than a M1 Max when it comes to building large projects on Xcode.

FB12925643 reported

We are seeing the same thing since these updates. Users complaining about this daily. Unable to use the app.

I'll update it with a crash report from another user. We are unable to reproduce this on any of our macs or devices ourselves. However, I've spent a good part of the day (over 12 hours) preparing no less than 22 builds with tweaks and shared it with users experiencing crashes and each crash log has the same thing - reference to withCheckedContinuation. When we commented out the entire sub-section of the app that uses withCheckedContinuation, the app stopped crashing

@DTS Engineer shared some crash logs just now

This answer only raises a hundred more questions. I’m sorry for sounding emotional, but this is an unsatisfactory answer and an unacceptable change - this is a severe overreach. Are Mac users unable to prevent the urge of downloading malware to their machines? This change hampers productivity and disregards the needs of professionals who rely on these functionalities daily. FB15199812: please kindly revert this change.

Why just non sandboxed apps? That's the exact opposite of a safe, notarized app that cannot perform functions outside its given scope. We demand that this change simply be reverted. It's ineffective in its purpose. It hampers productivity and limits the users ability to customize third party apps.