It is not only that you have unsigned libraries, but there are two other issues:
1. The Chromium Framework is not correctly structured, but must have the structure described in https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPFrameworks/Concepts/FrameworkAnatomy.html <https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPFrameworks/Concepts/FrameworkAnatomy.html> to be properly signed for notarization. 2. The plugins must be signed with --options runtime or the notarization request comes back with the error status "The executable does not have the hardened runtime enabled." ...and you can sign it with that option - which will let the viewer be notarized, as I managed to do once before February 3 and they tightened the rules. The problem is then that the plugin (particularly the SL Plugin) does not communicate with the main application at all as they are both executing in their own sandboxes. I have an open issue with Apple Developer support on notarization, but the only thing they say are: build in Xcode, sign properly and enable hardened runtime on everything. They cannot provide any support for building with third party systems like cmake etc.
_______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
