OSSystemExtensionsWorkspace on iPadOS

Question

Created Jan ’26

Replies 6

Boosts 2

Participants 3

Hello!

I have app (macos and iPadOS platforms) with empbedded DEXT. The DEXT executable runs fine on both platforms (ver 26.2). Trying to execute from iPad App code:

let sysExtWs = OSSystemExtensionsWorkspace.shared
let sysExts = try sysExtWs.systemExtensions(forApplicationWithBundleID: appBudleId)

but always getting OSSystemExtensionError.Code.missingEntitlement error.

Which entitlement am I missing? Thank You!

Answered by DTS Engineer in 880669022

For future reference, I'd recommend replying by posting as a fully reply instead of using the "comments" feature, as full replies are harder to mess in our tooling than comments.

Thanks for the update, the bug is already created: FB16923149

Perfect! Please try adding the entitlement again, as this should now be fixed in both the portal and Xcode. Note that you may need to quit and relaunch Xcode for it to pick up the new entitlement option.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

Boost

Answer 1

DTS Engineer OP

Apple

Jan ’26

but always getting OSSystemExtensionError.Code.missingEntitlement error.

Which entitlement am I missing? Thank You!

I believe it's looking for "com.apple.developer.system-extension.install".

Hopefully that gets it working, but please let me know if you run into any problems.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

1

Answer 2

DTS Engineer OP

Apple

3w

I would like to note that both the documentation you have linked and our developer portal for enabling this entitlement both mention this API is macOS only.

The documentation and portal are both wrong. I'm working on getting the portal fixed (r.162380702) and I'll try and let you know once that's done. On the documentation side, I'd appreciate you filing your own bug on that issue and then posting the bug number back here once it's filed.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

0

Answer 3

DTS Engineer OP

Apple

2w

Recommended

For future reference, I'd recommend replying by posting as a fully reply instead of using the "comments" feature, as full replies are harder to mess in our tooling than comments.

Thanks for the update, the bug is already created: FB16923149

Perfect! Please try adding the entitlement again, as this should now be fixed in both the portal and Xcode. Note that you may need to quit and relaunch Xcode for it to pick up the new entitlement option.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

1

Answer 4

Maff OP

1d

Thank you. After some issues with installing the certificate we were able to properly add the entitlement. I am now seeing a new error:

0

Answer 5

Maff OP

1d

Thank you. After some issues with installing the certificate we were able to properly add the entitlement. I am now seeing a new error:

Remote object proxy error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.DriverKitExtensionServer was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction." UserInfo={NSDebugDescription=The connection to service named com.apple.DriverKitExtensionServer was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction.}

0

Answer 6

DTS Engineer OP

Apple

2h

Thank you. After some issues with installing the certificate we were able to properly add the entitlement. I am now seeing a new error:

Looks like there's another bug here, this time in the system itself. We're looking into this as part of your existing bug (FB16923149), but it's probably going to require a system update to get this fixed.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

0