FB15139430 It seems it's not just macOS 10.15, it's also Big Sur. In fact, it's not about the macOS version - it's crashing on Intel Macs. We've just received a crash report from Big Sur with the same issue: Code Type: X86-64 (Native) Parent Process: ??? [1] User ID: 501 Date/Time: 2024-09-18 12:48:44.261 +0700 OS Version: macOS 11.7.10 (20G1427) Report Version: 12 Anonymous UUID: FCCC50AB-71DC-4908-AD86-EE79F2A7EDFF Sleep/Wake UUID: FA9BC3F4-1F95-41BC-9153-EA509922FCFB Time Awake Since Boot: 44000 seconds Time Since Wake: 18000 seconds System Integrity Protection: enabled Crashed Thread: 0 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: DYLD, [0x1] Library missing Application Specific Information: dyld: launch, loading dependent libraries Dyld Error Message: dyld: Using shared cache: 3694F5E4-3E85-3CD5-A2B0-534E2DFC1355 Library not loaded: /System/Library/Frameworks/QuickLookUI.framework/Versions/A/QuickLookUI Referenced from:

@DTS Engineer Seeing the exact same behavior here. App crashes with "Dyld Error", "Library not found: QuickLookUI" on macOS 10.15 if compiled with Xcode 16 on Sequoia, but works fine if compiled with Xcode 15 on Sonoma.

Sorry, just to point out that this is not fixed, see latest remarks: https://developer.apple.com/forums/thread/761654

FB15151141 Xcode 16 built apps using withCheckedThrowingContinuation causing apps to crash on macOS 15 and iOS 18

This is not fixed - we're using Xcode's latest update (Version 16.0 (16A242d) Our macOS and iOS apps are both randomly crashing but always around withCheckedContinuation We cannot reproduce this on any of our devices, but there are dozens of users with repeated crashed at launch

Same here, our app is randomly crashing for many users all of a sudden and all stacks show "withCheckedContinuation" in them. We changed no code other than compiling with Xcode 16

We're seeing users on macOS 10.15 crashing too at launch with errors in the console "PLugins Folder not found" errors. The app was not changed in any way other than building with xcode 16 RC1.

It seems to be caused by enabling ENABLE_USER_SCRIPT_SANDBOXING. It was working fine in Xcode 14 beta 1 and 2 though. The Input Files and Output Files have been correctly specified though, yet it seems to be failing.

Here we go again.

Take a break, sip some tea, go out for a walk and come back and try later. Since this is the new norm, their servers seem to be okay at midnight (NY time). Try and submit builds then.

You just have to use a slightly different App Icon (use a different color for Admins). Green for Users and Blue for Admins for example.

It's starting to look like this: https://github.blog/2022-03-23-an-update-on-recent-service-disruptions/

And that's my point. If you click on one of them, they show you that the performance issues began roughly 2 hours ago. That's incorrect - if you scan through the forums, it's been at least 8 hours this way. Why have a status page if it's updated manually, and that too after several hours of reporting and then misreport the incident time?

See this: https://developer.apple.com/forums/thread/705825 https://developer.apple.com/forums/thread/705799

Just answering your original question - Core data is not the right choice for this at all.