Good to hear, did you need to mess with the framework search path order to make this misbehave the same way? So I guess your radar is enough or should I also create one?

Hi, thanks for answering! I'm already using otool, because I found an old post by you explaining a little bit about otool for a different question. I used it and I think I could pinpoint the problem. In my case I have two statements referring to the CoreData Framework: /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData (compatibility version 1.0.0, current version 1048.0.0) Which seems to be the correct entry. But at the very end I have an additional line: /System/Library/Frameworks/CoreData.framework/CoreData (compatibility version 300.0.0, current version 1775.118.101) Which I suppose is the problem. I have also checked the same for an old build that I did (which was still working on 10.13) and the output is basically the same but without the probably problematic last line. Right now I'm in the process of figuring out where this last line comes from. Thank you, again! I will post if I figure out the where this line comes from.

Thanks for the info. I did just that and it worked. So I guess it is something specific to my project. As far as I understood this is some kind of linkage error where the app doesn't find the provided CoreData libraries. So I'm asking myself how does macOS try to find the system provided libraries like CoreData? Might this be indicative of an error with the "System Framework Search Paths" (which is empty in my case)?

Some here on Xcode 12.5.