We have a signed application which relies on communicating with a third party process and asking it to load some applescript code. This works fine in High Sierra. I understand there are big changes to security in Mojave. When our application runs in Mojave it fails to communicate properly with the third party process, even after clicking "allow" in the "Allow access" user dialog.
Looking at Console.app, it says:
"skipped scripting addition "/Library/ScriptingAdditions/[name of script]" because it is not SIP-protected."
Has anyone else seen this? Is there some way I can "SIP protect" my script so Mojave will let it load? Or is this approach simply forbidden in Mojave?
merlin
