I recently began to code sign my applets, due to Mojave security behaviour, using Script debuggers convenient method for persistent code signing.
But I ran in to a problem: If the app have scripts in it’s resource folder (e.g. script libraries) those bundled scripts get locked – non editable – afterwards. I have so far solved that by going back: removing the code signing (after which the bundled script is still locked), then copying the code from the bundled script to a new script and then replacing the bundled script with the new one in Finder.
Can anyone give me advice about the best way to solve the problem with locked scripts so that I can continue to code sign my applets?
I figure I can save the bundled scripts as script bundles (scptd) and code sign them – but then there will be a lot of code signing to do…
To avoid that, do I have to store the scripts/ script libraries outside the bundle – and deploy them to my organisation that way? Or is there a better way?