Closed rurza closed 5 years ago
Not sure. But feel free to re-sign DevMateKit with own certificate.
Don't know how to make it. DevMateKit isn't visible as a target in Xcode project settings for some reason :/
In your main app target you can add additional "run script" phase (it should be after pod's one that copies resources/frameworks to corresponding folders). New script phase should contains script that uses codesign
to re-sign necessary resources.
Thanks :)
@rurza Not sure if you're still having this issue (I ran into this recently), but for the benefit of others whom may encounter this in the future, this is what I did to resolve this error:
dyld: Library not loaded: @rpath/DevMateKit.framework/Versions/A/DevMateKit
Try adding --deep
to Other Code Signing Flags
in Build Settings
Forgot to close the issue 🤦♂️
Hey, I've found that the only way to run the app with DevMateKit and hardened runtime enabled is to select "Disable Library Validation" in Runtime exceptions. That's because the DevMateKit is signed by you, unlike the rest of app. Is it okay?
DevMateKit (1.9.2)