We are building an iPadOS app that requires a DriverKit USB transport dext, and we have been waiting on the restricted entitlement for over three weeks with no movement on any of our requests.
Team ID: AKFY9W27HB Entitlements requested: com.apple.developer.driverkit and com.apple.developer.driverkit.transport.usb
┌────────────┬───────────────┬───────────┐ │ Request ID │ Requested │ Status │ ├────────────┼───────────────┼───────────┤ │ 633LBK79JF │ 25 July 2026 │ Submitted │ ├────────────┼───────────────┼───────────┤ │ 6N8PP3G6BA │ 6 August 2026 │ Submitted │ ├────────────┼───────────────┼───────────┤ │ Y8T72G8YJS │ 6 August 2026 │ Submitted │ └────────────┴───────────────┴───────────┘
All three are still showing "Submitted" with no response, the oldest for over three weeks.
What we actually need is one configuration, not three grants. The three requests cover three vendor IDs, but a single dext has to match all of them simultaneously:
- 0x1452 (5202)
- 0x1343 (4931)
- 0x0D16 (3350)
I believe this is the same situation as thread 826658 (https://developer.apple.com/forums/thread/826658), where multiple vendor ID requests were consolidated into a single entitlement configuration. If our three can be merged the same way, that is exactly what we need.
Any guidance on the status of these three requests, or on consolidating them, would be much appreciated.
Any guidance on the status of these three requests, or on consolidating them, would be much appreciated.
For any future readers, the best way to deal with this sort of DriverKit Entitlement configuration issue is to file a Code-level support issue. You'll end up dealing with the same person [1] and you won't need to put all of your app/team level details into the forum. FYI, The request form will ask for a forum post, and you can paste in this post.
All three are still showing "Submitted" with no response, the oldest for over three weeks.
I'm afraid there is a bit of a backlog, but the team is trying to get caught up. I believe your request was approved earlier today.
The three requests cover three vendor IDs, but a single device has to match all of them simultaneously:
For future readers, including both decimal and hex in your entitlement request like this:
0x1452 (5202) 0x1343 (4931) 0x0D16 (3350)
...can be quite helpful. USB vids/pids are typically written in hex but the entitlement structure means that they need to be entered in decimal. Including both values makes it clear that you're asking for EXACTLY what you need.
[1] Probably "me", but maybe someone else [2] if I'm on vacation.
[2] Possibly even Quinn!
__
Kevin Elliott
DTS Engineer, CoreOS/Hardware
