ignoring mis-configured plug-in at /Path/To/Foo.appex: plug-ins must be sandboxed

544 Views Asked by At

I'm getting this message spammed in the console:

The error line repeated many many times in Console.app

Additionally, my extension doesn't show up in System Preferences: The System Preferences' Extensions pane, showing my extension wasn't installed (no, I'm not developing OneNote)


Here are the commands I use to install the extension, each of which claims it succeeded:

The terminal view of installing the extension

And here is proof that the extension is indeed sandboxed:

The Xcode project, showing the AppEx and its sandboxed nature


The only possible problem I can imagine involves our code signing process. For various reasons, it's codesigned after it's compiled, using a command like the following:

codesign --force --entitlements "$ENTITLEMENT" --sign "$CODESIGN_ID" --deep "$APPEX_PATH"

This is a requirement and, sadly, cannot be bypassed. Codesigning must be done after the appex artifact is generated.

However, this has not been a problem in the past. This is the say it's been done for a while and it worked fine. The only difference I can think of is that now we are bundling in two new .frameworks... but those are signed as well, so I'm not sure what to do.

When I remove the frameworks from the project and move codesigning to Xcode, it works... but that's not a permanent solution since we still need to manually codesign later on in our process.

What can I do to get this extension installed and preserve our codesigning requirement?

0

There are 0 best solutions below