Xcode 14 and later requires a DriverKit development profile enabled for iOS and macOS. Visit the developer website to create or download a DriverKit profile.
I have the same issue.
My driverkit driver is for macOS. I do not know how to create a profile for iOS&macOS exactly. HELP!!!
Post not yet marked as solved
I got the same problem. Need help.
Post not yet marked as solved
Hi,
I can't add
com.apple.developer.driverkit.userclient-access
into my provision profile. Is this entitlement need to request?
Thanks.
Post not yet marked as solved
Hi Every body,
I have the approved entitlement now and I download the .provisionprofile to embed it into my dext before sign it.
Now I see this article, does it mean I can ignore this .provisionprofile during development?
Thank you so much. And DriverKit is tough!
Appreciate for you guys big support!
Post not yet marked as solved
Please tell me,
Is the Apple approved entitlement necessary for dext living? If it take exactly 2 month to get,
How can I continue my porting?
Post not yet marked as solved
Excuse me!
So the entitlement approved by Apple is required? I signed my app and dext then tried to load my dext, it seems loaded successfully.
But in console I can't see any log printed by my dext, the only one log is in the crash report appears after I plug-in usb device, and the content is:
dext crash report - https://developer.apple.com/forums/content/attachment/296fe143-fd05-404c-914a-90c8b9b5c67c
Can anyone help? Thanks!
Thank you Quinn for such efficiently response, to be honest we are developing an application to control PowerPoint/Keynote, we found that the AppleScript is the only way controlling PowerPoint and we developed many AppleScript macros to control it.I will replace current method by the mothod you are suggesting me, but some other function we've implemented might still not work(I am afraid of it). For instance, Play slide/Stop play slide, draw, blackout screen...,etc.Anyway I will take your suggestion first then go forward and update my status, thanks!
Thanks Quinn, finally I did it. Yes the key point is on how we handle these libraries...Sort all my working out below:1. The libraries all must be only embedded in Frameworks. So we should make LC_ID_DYLIB and LC_ID_DYLIB correct. A success Mach-O path content should be like this:@executable_path/../Frameworks/<Library name itself>
@loader_path/<Refer Library name> (compatibility version 3.0.0, current version 3.1.4)The first line is the library itself execute path, and the second line is the path of other library referred by this library.2. In the project setting, all library should choose “Embed and sign”. The library itself doesn’t need to be signed manually first. All of them will be auto signed when exporting to notarize service.That’s it, due to some reason we have limited resource to be authorized from 3rd party again, but thanks Apple we still can use these libraries 🙂Thank’s Quinn’s strong support!!
Where have you placed the library? The usual location for such things is Contents/Frameworks/.
-->I'm afraid of this, the libraries are dependencies with each other, they are located in /usr/local/bin, I don't have source code and I find they should be inside here because I got these information by otool -L:libhidapi.0.dylib:
/usr/local/lib/libhidapi.0.dylib (compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1349.8.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1238.60.2)I tried change the path by using install_name_tool but I failed. My install package project installs these libraries in /usr/local/lib originally.Did you re-sign it using your Developer ID? That’s pretty much required, and it makes sense when you step back and think about it. You’re shipping this code to customers, so you take on the responsibility for how it behaves, so you sign it as your code.-->Yes I re-signed the library using my company's Developer ID application.And there's update here...I manually signed these libraries by codesign with developer ID, then I replace the original with these new signed files, there's no more "library not loaded" message shows, it seems running( but crashes on IOHIDManager api that's never happens on 10.14), but somehow when I move all files(application+libraries) to 10.14.6, the message "library not loaded" still appears...So I got 2 difficult questions:1. The "Library not loaded" seems resolved on 10.15 but still appears on 10.14.62. The IOHIDManager api will run fail on 10.15.Thanks Quinn's time and helpful anwsers!--Another discovery--I found the built binary behavior are not the same between debug and deploy version. Here's a crash report comparison:https://imgur.com/dF1qU5ZI am wondering why? How do I make the environment the same? Thanks a lot!
I got sililar issue and I've tried couple ways don't work at all.Would you please take a look into this?(Posted here and n StackOverflow)Thank you so much!!https://forums.developer.apple.com/message/390019#390019https://stackoverflow.com/questions/58515410/library-not-loaded-after-runtime-hardened-enabled
Post not yet marked as solved
I have the same problem. I don't know how to solve this issue.
