Page 1 of 1

"Adding ad-hoc signature failed with error" [SOLVED]

Posted: Thu May 21, 2020 3:12 pm
by bangkok
MacBook Air with Catalina 10.15.4

LC Indy 9.6 rc 2

A simple stack with one button, compiled for MacOS X 64 bits gives a long error msg (see screen).

So is it a bug with LC Indy 9.6 rc 2 ? Or do I miss something ?

I've tried with LC Indy 9.5.1. It works. I can create the standalone for "MacOS X 64 bits"

Re: "Adding ad-hoc signature failed with error"

Posted: Thu May 21, 2020 3:49 pm
by richmond62
I just made a stack with a single button and ran off a standalone for Mac-64 on MacOS 10.15.5 beta 4
using 9.6.0 rc 2 and had no problems at all.

Re: "Adding ad-hoc signature failed with error"

Posted: Thu May 21, 2020 7:01 pm
by bangkok
richmond62 wrote:
Thu May 21, 2020 3:49 pm
I just made a stack with a single button and ran off a standalone for Mac-64 on MacOS 10.15.5 beta 4
using 9.6.0 rc 2 and had no problems at all.
I opened a ticket, because with LC Indy 9.6 dp4... it's okay. The standalone for MacOS is created correctly.

But 9.6 rc2 and 9.6 rc1 (i've tried this one too) : same error message while saving the standalone.

Re: "Adding ad-hoc signature failed with error"

Posted: Fri May 22, 2020 8:48 am
by bangkok
Solved.

Following Panos advice :

"opening a terminal and type:

sudo xcode-select --install
"

Fixed the issue.

Re: "Adding ad-hoc signature failed with error" [SOLVED]

Posted: Sat Jun 20, 2020 6:41 am
by ludo
Hello,

I had the same error but the command lines tools were already installed.
It was the presence of accents in the standalone name that caused the problem (9.6 final).

https://quality.livecode.com/show_bug.cgi?id=22791

Re: "Adding ad-hoc signature failed with error" [SOLVED]

Posted: Thu Jul 30, 2020 2:03 am
by MJLew
I have this problem with 9.6.0 on MacOS 10.14.6 and there are no accents in my standalone name.

Before I try the solution suggested by Panos I'd like to know what it does. I do not have XCode installed and I do not have space for it. Is it required?

I'll also note that the solution(s) are not mentioned in the bug report https://quality.livecode.com/show_bug.cgi?id=22791