Our version N is not code signed (code object is not signed at all) and to meet the notarisation requirements, N+1 is code signed and meets the DR, we see the following messages when codesign -v -v -R run on N+1 valid on disk satisfies its Designated Requirement explicit requirement satisfiedThe issue here is System Prefernces showing as checked but API(AXIsProcessTrustedWithOptions) returning not trusted, after the update if app is not trusted for any reason(code signture compatibility etc), System Prefereces is expected to show it as unchecked so that user can check it .Right now what is happening, when we guide the users to check the box next to our app, they see it as already checked and not doing anything resulting in app not trusted.

Install version N then update to N+1 (C) is failing, Yes our tests are on a VM, each time reverting to a snapshot where product is never tested.

I am also seeing the similar behaviour that sudo commands are failing from post or pre install scripts.

This is a legacy code and I don't think there is any specific reason for using /Resources/Components/We tried placing the legacy extension in Content/PlugIns, but the warning is still not resolved. (***.safariextz is not a valid product / component package.)Any other inputs that we could try.