@ssmith_c Thanks you. That is helpful information, but I'm still unsure what provisioning profile to use for the release build's DriverKit Extension target. Can you clarify that for me? Let me clearly layout my issue: We have an Xcode project that contains two Targets: The Core App (meaning the main application that contains all views and most functionality) and the USB DriverKit target (which is just the USB driver). I have a development certificate and two development provisioning profiles. One for the Core App, and one for the the USB DriverKit target. I can run the development build just fine out of Xcode. I can sign them manually or automatically in the Xcode and run them. I can also create a build for development using XcodeBuild from the terminal. BUT For release I currently only have one provisioning profile for the Core App. There is no way to create a Release provisioning profile for a DriverKit target. How do I sign the build for release using XcodeBuild? What is that process? Can you break it down step-by-step? Do I simply use the same DriverKit development profile and just change out the entitlements.plist? That seems like it would still block the app from running on iPads that aren't registered in the development profile. Thanks in advance for you help with this.

@statemachinejunkie Can you layout, in a step-by-step way, how you were able to sign the release build of your app containing a DriverKit extension? We're struggling on our team trying to work through this process. We've tried archiving the build, and then resigning on export but it complains that our entitlements aren't set up correctly in the provisioning profile (but we know they are). What kind of provisioning profile are you using to sign the release version of your DriverKit target? Our process so far: Set signing to automatic for the main app and the driverkit targets. Archive the build. Attempt to "distribute" the archive using the "Custom" option (trying for an enterprise build) Attempt to set the profile in the "Select certificates and iOS In House profiles:" step. Set the main app to its In House profile. Try to set the driver to an In House profile with "DriverKit" and "DriverKit USB Transport - VendorID" entitlements And that's where we get stuck. Setting the DriverKit target to the In House profile causes it to throw errors about not being set with the correct entitlements. I'm assuming this has to do with the fact that the entitlements plist is using the wildcard "*" instead of a proper vendor id. But when I try to Archive using the correct vendor ID it throws errors about the dev profile not having the correct entitlements. Any help would be greatly appreciated. Thanks!