Issue with code signing Mac standalones with hardened runtime
May 20 2020 | 5:14 pm
I am having an issue code signing Mac standalones created in Max 8 on Catalina using the hardened runtime option (which is required for notarizing the resulting application).
Even the simplest standalone (made from the attached maxpatch) results in an application that cannot load externals (see attached screenshots before and after code signing).
I am code signing from Terminal using the following command (as recommended at https://cycling74.com/articles/max-8-1-mac-os-10-15-catalina-support-and-notarization):
codesign -s [my developer ID] --options runtime --timestamp --force --deep -f [path/to/SimpleStanalone.app]
If I remove "--options runtime" the code-signed standalone opens fine but the signed application cannot be notarized by Apple which requires the application to be "runtime hardened". If I leave "--options runtime" the application does not load needed externals as shown in the attached screenshot.
I also ran the following command (as recommended on https://cycling74.com/articles/using-unsigned-max-externals-on-mac-os-10-15-catalina):
xattr -d -r com.apple.quarantine [path/to/SimpleStanalone.app]
to remove the quarantine attribute from the app bundle components but that did not fix the problem.
Any insight or recommendations will be greatly appreciated.