First of all, it's only for Developer ID App, not for Mac Store App.
We have legacy Cocoa Application A. We don't want to embed the System Extensions in it because the changing would be too much. Instead, we're thinking of developing the other container App B to embed the System Extensions, and adding B to A as Helper App (like Build Phase->Copy Bundle Resources). Then A application can simply launch B application to enable the System Extensions. I want to know if it's actually feasible? Could it pass Notarization?
Thanks,
Xin
Could it pass Notarization?
Notarisation won’t be a problem. The notary service will happily accept deeply nested code like this as long as it’s correctly signed.
like Build Phase->Copy Bundle Resources
Do not nest code in
Content/Resources/See the Nested Code section of TN2206 for info on where your app should be nested. This will likely involve you creating a new Copy Files build phase to copy the app to the right place, but that’s not hard.
As to whether this will actually work, it’s hard to say. The system extension subsystem was designed on the assumption that the sysex is embedded within a top level app, so I’ve no idea how it’ll react to your proposed setup.
Honestly, I think you’d be better off grasping the nettle and updating app A.
Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
let myEmail = "eskimo" + "1" + "@apple.com"