How is Development-Signing Supposed to Work with DriverKit on macOS?

Question

Created Aug ’22

Replies 3

Boosts 0

Views 3.6k

Participants 4

The release notes for Xcode 14 say: "Automatic signing is now supported for development-signed DriverKit drivers."

But when I try to get the sample code to work, Xcode 14 beta 5 complains that "Ad Hoc code signing is not allowed with SDK 'DriverKit 22.0'".

Explicit signing wants to have an entitlement that Apple seems to be very reluctant to hand out, but I think there should be no hurdles to just playing with DriverKit on my dev machine.

Is this a bug with the beta or am I missing something here?

Boost

Answer 1

jbrisbin OP

Aug ’22

A few days ago, I reported substantially the same issue as feedback item FB11064423 (which you probably cannot see). Having no workaround to allow debugging until real entitlements are available, in some indeterminate time, will put a kink in my development, for sure.

0

Answer 2

OP

Apple

Aug ’22

Accepted Answer

In order to build the sample with Xcode 14, you'll need to change the "Code Signing Identity" of the sample away from "Sign to Run Locally." This will allow you to use automatic signing with your developer account. We are in the process of updating the DriverKit samples to better support this change.

Alternatively, if you still wish to use ad hoc codesigning, you can add the AD_HOC_CODE_SIGNING_ALLOWED user-defined setting to your Dext's "Build Settings." Setting it to YES will allow you to continue running ad-hoc builds on macOS only. This behavior will not work for iPadOS.

3

Answer 3

nsc OP

Aug ’22

Thanks, allowing adhoc signing works! I have tried to use automatic signing with my developer account, but then the client fails to launch and taskgated says: "Unsatisfied entitlements: com.apple.developer.driverkit.userclient-access"

0