The best way to package Endpoint Security extension

Question

Ere0n OP

Created Aug ’24

Replies 1

Boosts 0

Participants 2

I have developed an Endpoint Security extension which works with my normal Mac APP.

For now, there are two independent projects, one is ES extension project, and the other is my normal APP. I want to distribute my APP as a pkg, so I need the ES extension in the package.

I wonder to know what is the best way to package the ES extension with my normal APP? Should I add an Endpoint Security target in my normal APP project and copy the codes from ES project? Then, when user launch my APP, at some point, I need register the ES extension by OSSystemExtensionRequest?

Answered by DTS Engineer in 801691022

There are a bunch of different ways you can set this up, but the simplest is to have a single project with two targets: one for app and the other for your ES sysex.

If you do that then, yes, your app will code that calls the System Extensions framework to activate your ES sysex.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Boost

Answer 1

DTS Engineer OP

Apple

Aug ’24

Accepted Answer

Recommended

There are a bunch of different ways you can set this up, but the simplest is to have a single project with two targets: one for app and the other for your ES sysex.

If you do that then, yes, your app will code that calls the System Extensions framework to activate your ES sysex.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

1