@rhythmicfistman Have you made any progress on this issue? I am also trying to develop a PCIDriverKit dext without having requested entitlements from Apple, but in Xcode 14 my dext always fails to launch due to a code signing error. I filed FB10590428 but have not heard anything.
@Drewbadour My issue seems to be the restricted entitlements are not part of the provisioning profile. How exactly are we supposed to add the PCI transport entitlement to the provisioning profile?
jeff_f
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
I am having this same problem when trying to get a third party kext to load during the boot process. I also am using "Local-Root" for the value of OSBundleRequired. Instead of loading my kext, macOS loads a builtin (native) kext that also matches my device. I am running macOS 10.15.7 (19H114) on a MacBook Pro (16-inch, 2019).
In the reply from Systems Engineer they say
If you are looking to simply have your device matched at boot (and don't need to boot the OS from a device supported by your driver), then there may still be a driver matching issue. What settings in the Info.plist of my kext will make it possible for my kext to match with my device at boot?
I am having this same problem when trying to get a third party kext to load during the boot process. Instead of loading my kext, macOS loads a builtin (native) kext that also matches my device. I am running macOS 10.15.7 (19H114) on a MacBook Pro (16-inch, 2019). Did you ever receive guidance from Apple about this problem?