Re: Embedded binary is not signed with the same certificate as the parent app

> On Mar 3, 2020, at 08:51, Gabriel Zachmann via Cocoa-dev > wrote: > But I would also like to *understand* why things are not working (if they are > not working). > So, why would copying the app bundle to some other place > (using in Xcode's Copy Files phase) cause this weird error? Because

Re: Embedded binary is not signed with the same certificate as the parent app

> > Why are you copying that app you are trying to build? > OK, I could just use the app bundle under /tmp/Release , I give you that. But I would also like to *understand* why things are not working (if they are not working). So, why would copying the app bundle to some other place (using in

Re: Embedded binary is not signed with the same certificate as the parent app

Mar 2020, at 12:47, Alex Zavatone wrote: >> >> Please send a screenshot of your copy files phase so we can clearly see what >> you are trying. >> >> Thanks. >> >> Sent from my iPhone >> >>> On Mar 2, 2020, at 7:12 PM, Gabriel Zachmann via C

Re: Embedded binary is not signed with the same certificate as the parent app

lto:cocoa-dev@lists.apple.com>> wrote: >> >> I have a naked macOS app (created with Xcode's template "App"). >> >> I get this funny error message >> >> Embedded binary is not signed with the same certificate as the parent app >&g

Embedded binary is not signed with the same certificate as the parent app

I have a naked macOS app (created with Xcode's template "App"). I get this funny error message Embedded binary is not signed with the same certificate as the parent app but only, when I switch to Release *and* when I add a Copy Files phase with Destination = Absolute