Posts

Post not yet marked as solved
6 Replies
1.1k Views
Runtime crash on macOS 10.13 (High Sierra) with this dyld message: "Incompatible library version: Application requires version 300.0.0 or later, but CoreData provides version 1.0.0" Project configured for 10.12 deployment, and loading seems to work in 10.14 or later - and worked properly built with Xcode prior to 12.5. How do I accommodate 10.12 deliveries? Include the CoreData framework? How's that handled in this case (where included isn't needed for current systems)?
Posted Last updated
.
Post not yet marked as solved
1 Replies
596 Views
Have an i386 / x86_64 built library that can't be re-built as universal, but it's needed to support (for some time to come) Intel boxes back to macOS 10.12 Sierra. Provided I don't use the library on Apple Silicon, why can't I include the library (and its header) for use in the x86-64 slice of the app for Intel or Rossetta 2? Xcode immediately identifies the library as a problem when compiling for universal, but I can't (or there doesn't seem to be a method to) incorporate that library anyway. If there's no work-around, I'd like to hear the technical reason the lib can't be included in the universal build. The prohibition may keep me from accommodating Apple Silicon for quite a long time. This is an eSellerate serial number validation lib - no longer supported - and it's needed for older customers (guaranteed to be running on Intel boxes) who purchased our application outside the App Store. These customers still upgrade their software and hardware appropriately and as long as they keep their Intel box, I'd like to support them (except demo copies, all recent customers must originate from App Store). The algorithm embedded in the lib is proprietary, so I can't reproduce it.
Posted Last updated
.