Post

Replies

Boosts

Views

Activity

Reply to DriverKit USB Transport entitlement pending 6+ weeks (DNP + HiTi photo printers) - same VIDs already approved for another team
Confirmed, thank you Kevin. Resolved, for future readers: the entitlement was approved the day after this post (requests 72B5P53K28 and 4Z76G958GF, submitted July 24/25, approved September 10). What moved it was following the advice in https://developer.apple.com/forums/thread/842434: filing a Code-level Support request with a link to this forum post. The Developer Support case I had open for weeks never reached the DriverKit team. Notes that may save others time: The grant was one configuration covering all three vendor IDs (3350, 4931, 5202) in a single dext, as needed. On the App ID, enable BOTH "DriverKit" and "DriverKit USB Transport - VendorID". With only VendorID enabled the App Store profile lacks com.apple.developer.driverkit and export fails. No user-client entitlement was needed: the dext is only opened by our own app (same team), per https://developer.apple.com/forums/thread/774297. xcodebuild -exportArchive with signingStyle manual and an explicit provisioningProfiles mapping for both the app and the dext bundle IDs distribution-signed the USB dext correctly. The manual codesign re-sign flow from thread 809202 was not required in Xcode 26.6. App Store Connect rejects a dext unless its bundle is named .dext and its Info.plist has CFBundleDisplayName. The resulting TestFlight build prints from an M1 iPad Pro to both DNP and HiTi printers.
Topic: App & System Services SubTopic: Drivers Tags:
Sep ’26
Reply to DriverKit USB Transport entitlement pending 6+ weeks (DNP + HiTi photo printers) - same VIDs already approved for another team
Confirmed, thank you Kevin. Resolved, for future readers: the entitlement was approved the day after this post (requests 72B5P53K28 and 4Z76G958GF, submitted July 24/25, approved September 10). What moved it was following the advice in https://developer.apple.com/forums/thread/842434: filing a Code-level Support request with a link to this forum post. The Developer Support case I had open for weeks never reached the DriverKit team. Notes that may save others time: The grant was one configuration covering all three vendor IDs (3350, 4931, 5202) in a single dext, as needed. On the App ID, enable BOTH "DriverKit" and "DriverKit USB Transport - VendorID". With only VendorID enabled the App Store profile lacks com.apple.developer.driverkit and export fails. No user-client entitlement was needed: the dext is only opened by our own app (same team), per https://developer.apple.com/forums/thread/774297. xcodebuild -exportArchive with signingStyle manual and an explicit provisioningProfiles mapping for both the app and the dext bundle IDs distribution-signed the USB dext correctly. The manual codesign re-sign flow from thread 809202 was not required in Xcode 26.6. App Store Connect rejects a dext unless its bundle is named .dext and its Info.plist has CFBundleDisplayName. The resulting TestFlight build prints from an M1 iPad Pro to both DNP and HiTi printers.
Topic: App & System Services SubTopic: Drivers Tags:
Replies
Boosts
Views
Activity
Sep ’26