Thanks for the excellent description of the problem Tim. It may help in
debugging my own “notarisation” issues in the future (tucked away for future
reference)!!
>
> It all makes me long for the days when we could easily pass around Hypercard
> stacks for the fun of it!!
And boy can I
Yes Matthias, I figured you had a good reason so I went back into the account
and checked every single thing very carefully. When I saw that my device was
not trusted I figured THAT had to be fixed!!
Then I just followed your suggestion to redo everything and that’s when I
learned about how
Congratulations. Good to know that you could resolve it.
And now you know why wanted to do a remote session to repeat all steps from
creating app-specific pw to connecting to apples services. ;)
We could have found out sooner. ;) Unfortunately your security office
prohibited the use of
Yes, this is the advantage of an. App specific password. It’s unrecoverable by
you, and so by anyone else.
Bob S
On Aug 25, 2023, at 1:34 PM, Timothy Bleiler via use-livecode
wrote:
This time I saw the second part when they send the actual password. I think you
need to copy this down
If you mean that the the link was shown normal and also in sharp bracktes, then
that seems to be normal here in the list.
I noticed this also in the past.
> Am 25.08.2023 um 22:41 schrieb Timothy Bleiler via use-livecode
> :
>
> It’s just not my day. The goofy links in my last post are just
It’s just not my day. The goofy links in my last post are just supposed to be
references to the appleID site. I don’t know how all the rest of that got put
in there.
I’ve got to be more careful with my copy and paste I guess.
> On Aug 25, 2023, at 4:34 PM, Timothy Bleiler via use-livecode
I think I’ve solved it. I’m very grateful to Matthias both for his code
signing tool and his personal help with this problem.
In the end it looks like the trouble was caused by a combination of my limited
experience with the process and a lack of helpful feedback from Apple’s online
tools at
I use Matthias' brilliant “mrSignNotarizeHelperV4.livecode” project regularly
and when I’ve had a problem in the past, ticking the “Debug mode” checkbox
(which places each step of the terminal commands in the message box when you
click the “Start” button) and then manually entering each of
Hi Tim,
Codesigning is (as you probably know) one of the tricker bits of building an
app for distribution (and I’ve certainly had my share of failures and
frustrations along the way). I am following this thread closely so if you don’t
mind sharing, I’d be interested in hearing what the
The Keychain.app does not have any influence on passwords entered in the
command line.
Passwords entered in terminal will not be replaced by Keychain.app.
> Am 25.08.2023 um 16:37 schrieb Timothy Bleiler via use-livecode
> :
>
> Thank you Heather,
>
> I’ll take a look. Matthias Rebbe is also
Thank you Heather,
I’ll take a look. Matthias Rebbe is also trying to help me find the problem.
Regards,
Tim Bleiler
> On Aug 25, 2023, at 4:13 AM, Heather Laine via use-livecode
> wrote:
>
> Tim - codesigning is not my expertise but failed password credentials I deal
> with frequently
Tim - codesigning is not my expertise but failed password credentials I deal
with frequently :). A possible gotcha is that your password is saved to your
keychain, and then, if you change it, the changed password is overwritten by
the saved password, invisibly since the password is hidden when
Timothy,
so running the following command from step 7.1.2 of that lesson
xcrun notarytool submit --apple-id "" --password
"" --team-id --wait ""
gives you the 401 error or are you using the parameter --keychain-profile
instead of the three parameters --password,--team-id and --apple-id?
If
Hi all,
I believe the problem I’m having is either on Apple’s end or something with my
local configuration but Apple has not been very helpful and I’m running out of
ideas, so I’m turning to the wealth of experience on this list in desperation.
I’ve been using the lessons from Matthias Rebbe
14 matches
Mail list logo
