DriverKit driver doesn't appear in Settings when installed with iPad app

Question

Created Feb ’23

Replies 6

Boosts 2

Views 1.9k

Participants 6

I'm working on a DriverKit driver. I have it running on macOS, including a very simple client app written in SwiftUI. Everything is working fine there. I've added iPadOS as a destination for the app as demonstrated in the WWDC video on DriverKit for iPadOS. The app builds and runs on my iPad, as expected (after a little work to conditionalize out my use of SystemExtensions.framework for installation on macOS). However, after installing and running the app on an iPad, the driver does not show up in Settings->General, nor in the app-specific settings pane triggered by the inclusion of a settings bundle in the app.

I've confirmed that the dext is indeed being included in the app bundle when built for iPadOS (in MyApp.app/SystemExtensions/com.me.MyApp.MyDriver.dext). I also can see in the build log that there's a validation step for the dext, and that seems to be succeeding.

I don't know why the app isn't being discovered -- or in any case surfaced to the user -- when the app is installed on the iPad. Has anyone faced this problem and solved it? Are there ways to troubleshoot installation/discovery of an embedded DriverKit extensions on iOS? Unlike on macOS, I don't really see any relevant console messages.

Boost

Answer 1

tuple_cat OP

Jun ’23

I have the same issue. Did you make any progress with this?

1

Answer 2

statemachinejunkie OP

Dec ’23

I also have the same issue. Did the entitlement from Apple solve the problem?

0

Answer 3

NanoCarlos OP

Jun ’24

I've got the same problem, did anyone got to fix the problem?

0

Answer 4

statemachinejunkie OP

Sep ’24

This is now an issue with iPadOS 18. In iPadOS 17.7 my driver shows up in settings just fine. After recompiling with Xcode 16 and installing my app (containing my driver) on iPadOS 18, the app shows up in settings but the driver-enable button is missing from Settings. When I plug-in my custom USB device, the app cannot detect it.

0

Answer 5

MingJD OP

Apr ’25

I've got the same problem, did anyone got to fix the problem?

0

Answer 6

statemachinejunkie OP

Apr ’25

The Apple defect for iOS was solved last year. If you are still having issues on iOS, make sure you are running the latest version of iOS as a first step. If that requirement has been met, you have some other technical issue prevent preventing your driver from properly being recognized by the system.

If you are using macOS, there may be other issues such as your Xcode configuration, or not having your system properly set up for driver development. I don't have all the details for macOS, but the documentation provided by Apple should help in this instance. It might help if you created a separate issue perhaps linked to this one where you completely describe your situation and the problem you're experiencing. Be sure to include the code and configuration snippets so we can see exactly what you are doing in order to properly register and activate your driver.

0