We have now a DriverKit software related to a Teensy 4.1. The driving force works high quality on macOS, however we’re trying to get it working in iPadOS. All the things builds, the motive force appears to be putting in accurately, and I’ve enabled it in settings. Upon connecting the Teensy, it locates the proper dext and tries to launch it, however then fails with error:
DK: CDCDriver-0x100002543: supplier entitlements verify failed
I’ve executed my finest to confirm we now have entitlements configured accurately however I am new to DriverKit and it is not clear to me what I am lacking. Might be one thing apparent.
We have now targets for iOS and macOS. We’re utilizing completely different code signing and entitlements within the construct settings for every SDK.
The native entitlements plist file for the iPadOS constructed driver is simply:
<?xml model="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist model="1.0">
<dict>
<key>com.apple.developer.driverkit.communicates-with-drivers</key>
<true/>
<key>com.apple.developer.driverkit</key>
<true/>
</dict>
</plist>
I’ve additionally tried including/eradicating App Sandbox = YES primarily based on Apple’s instance mission to no avail.
ID Capabilities enabled for the motive force on developer.apple.com:
- DriverKit (Improvement)
- DriverKit Communicates with Drivers
- DriverKit USB Transport (Improvement)
Signing identification on iOS is Apple Improvement.
Provisioning Profile was set to DriverKit App Improvement with the above talked about ID and capabilities.
The bundle ID prefix is identical because the mother or father app.
Any apparent errors right here or concepts of issues I might verify?
