Application signed with ability to load system extensions started failing due to signature issue

Question

chapo213 OP

Created Sep ’24

Replies 2

Boosts 0

Participants 3

Hi,

I've developed an application which reside under /Applications.

Inside the main application bundle (/Applications/mainApp.app) there are sub-app that contain security extension. Here's the relevant path

/Applications/mainApp.app/Contents/Helpers/subApp.app/Contents/Library/SystemExtensions/com.myComp.type.systemextension/

So far I could load the extension by running the subApp and make sure it calls the extension activation API. but seems like starting from Sonoma (i'm using version 14.6.1 )it stopped working, and I get crash dump on signature failure which trying to open the subApp.app.

in the crash log I get reason of invalid code sign. I also get the following hints

Binary Images:
0x1050a0000 - 0x10512bfff dyld_path_missing (*) <f635824e-318b-3f0c-842c-c369737f2b68> /dyld_path_missing
0x104d9c000 - 0x104d9ffff main_executable_path_missing (*) <1df5f408-cb16-304f-8b38-226e29361161> /main_executable_path_missing

Is it possible that new OS version have new validation rule that enforce something about the location of the app that can start extensions ?

Boost

Answer 1

DTS Engineer OP

Apple

Sep ’24

I’ve not heard of such a thing, and I don’t think it makes logical sense. In general, if your setup doesn’t meet the requirements of the System Extensions framework, it returns an error.

The most likely cause is that your app isn’t signed correctly. I have a bunch of advice on how to debug such issues in Resolving Trusted Execution Problems.

Inside the main application bundle (/Applications/mainApp.app) there are sub-app that contain security extension.

What do you mean by “security extension”? You tagged your thread with System Extensions and Network Extension, suggesting that you’ve created a NE provider and packaged it as a sysex. Is that right?

Can you also post the full crash report? See Posting a Crash Report for advice on how to do that.

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

0

Answer 2

technology_support OP

Sep ’24

We've had this problem before, but we have a solution,

0