Hi,
I encountered an issue in my code where I directly used #import <CoreHaptics/CoreHaptics.h> without adding it to the "Link Binary With Libraries" section under Build Phases. My deployment target is iOS 12, and the code was running fine before; however, after upgrading Xcode, the app crashes immediately on an iOS 12 device with the following error message: DYLD, Library not loaded: /System/Library/Frameworks/CoreHaptics.framework/CoreHaptics | xx | Reason: image not found.
Did Xcode modify the default auto-linking configuration? When did this behavior change in which version of Xcode? Do I need to specify CoreHaptics.framework as Optional in "Link Binary With Libraries"?
Thanks for reply soon!
Did Xcode modify the default auto-linking configuration?
It’s hard to answer questions like this without more specific details, like the version of Xcode you were previously using and the version of Xcode you’re now using. However, in general, this sort of thing is supposed to work, so if you see a regression it’s reasonable to file a bug about it.
And if you do file a bug, please post your bug number, just for the record.
Do I need to specify CoreHaptics.framework as Optional in "Link Binary With Libraries"?
That’s what I’d do.
Autolinking in a technology with obvious pros but also some gnarly cons. If it doesn’t do the right thing, it’s fine to override it. Or even turn it off completely, via the various build settings that control its behaviour.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"