Conclusion: iOS 17, with iPhone 15 Pro Max, does not support DriverKit drivers. More info: I published an updated and fixed example project that works to install and use a DriverKit driver for both macOS and iPadOS. I created a new branch and added iOS as a supported destination, but it did not work the same as it did on iPad. You don't have any control over driver installation on iPad, you simply enable iPad as a destination, setup a settings bundle, and iPadOS finds, installs, and surfaces the switch to enable your driver in your application's settings at the iOS level. That process does not happen on iOS, see the images for the iPad settings bundle, and then iOS-- it is simply missing on iPhone. https://github.com/DanBurkhardt/DriverKitUserClientSample/tree/ios-support-testing Even if you successfully compile and run a target that embeds a working DriverKit driver to your iPhone, the driver will never be seen or installed upon app installation by the system (as of Oct 2023, iPhone 15 Pro Max, iOS 17). (iOS, no driver setting) (iPadOS, driver setting toggle enabled)

You will not be able to run a DriverKit driver on iOS because it can't actually install or run your driver, even if it compiles and installs your app successfully. I published a sample project that works, and this branch demonstrates that the driver will never be seen or installed upon app installation (as of Oct 2023, iPhone 15 Pro Max, iOS 17) https://github.com/DanBurkhardt/DriverKitUserClientSample/tree/ios-support-testing

Update: you also can get around this by selecting "Xcode (Standard Input)" when you edit the scheme. See this in my working example that also adds iPadOS support alongside macOS and updates to the latest driverkit version: https://github.com/DanBurkhardt/DriverKitUserClientSample Should be immediately runnable, but you will have to ensure you disable SIP and enable developer mode, as per the original instructions (required without DriverKit entitlement permission from Apple). You will also need to change the bundle ID to your own name (replace "gigabitelabs" with something that is specific to your dev account / business).

I have published a fully working client sample app example that adds iPadOS support alongside macOS and updates to the latest driverkit version: https://github.com/DanBurkhardt/DriverKitUserClientSample Should be immediately runnable, but you will have to ensure you disable SIP and enable developer mode, as per the original instructions (required without DriverKit entitlement permission from Apple). You will also need to change the bundle ID to your own name (replace "gigabitelabs" with something that is specific to your dev account / business).

I had this exact issue. Solution: I tried every single possible thing to fix this and nothing at all worked. It was maddening-- I have NO IDEA what was proventing me from just embedding a new DriverKit driver target into my app-- I tried EVERYTHING possible, including re-installing Xcode completely, with a full purge and re-load, full reload of xcode-select --install as well. The only thing that worked: Create a new application target, embed / link the new DriverKit target to the new application target Select every single file from the original project and add them all to the new application target using the Attribute Inspector After adding all source code, manually update the new target's application info.plist, entitlements, etc. After re-making the application target, this error stopped blocking me from compiling with the DriverKit driver. I must underline though that literally everything I could possibly check between these two targets is configured identically. It still is, and it still doesn't work with the original app target, and does with the new one. This one cost me a few hours, but tbh it seems like it is just a troll in the machine. TL;DR: This was solved (for me) by just starting over with a new application target. ** Local Env Application: macOS application (Cocoa / AppKit, not Catalyst) developed using a .xcworkspace so I can simultaneously work on a requried, private SPM Package application has other OSS package dependencies, all incorporated by a mix of local forks and remote branches / releases Macbook Pro, model Mac14,10, (M2 Pro, 16GB) macOS Ventura 13.5.1 (22G90) Xcode 15 (latest, and latest Swift version) macOS app target version: 12.*^

For anyone else: I have added instructions in Xcode 14+ to open CppUserClient in the terminal instead which will allow you to input a selection. See comment on youtube link above.