Mac Codesigning stops working. (revSecurity.dylib)
kee.nethery at elloco.com
Sun Sep 29 15:58:50 EDT 2019
My lesson on app signing isn’t automated, it has the terminal commands detailed. The reason I do that is because it’s a moving target. Things change as the codesign process updates.
If my lesson steps fail, you’ll probably see the exact reason as an error message. That should be the clue.
> On Sep 29, 2019, at 12:46 PM, Tony Trivia via use-livecode <use-livecode at lists.runrev.com> wrote:
> Hi all.
> I had the whole Mac codesigning thing under control, notarization, all
> that. Was successfully signing, notarizing and distributing (as third
> party) my MacOS app as recently as a week ago. But about two days,
> AppWrapper 3 started reporting "Failed to sign" blaming the subcomponent
> revSecurity.dylib. App Wrapper diagnosis says "code object is not signed
> at all in architectur: x86_64.
> My build is in LC 9.5 using 64-bit.
> I built a minimalist stack with one "go url" button to trigger inclusion of
> revSecurity and TSnet. Attempts to sign that minimal stack as a Mac
> standalone gets the same errors.
> Codesigning via Terminal also fails.
> Anyone else have this problem? Suggestions?
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode