Someone experiencing issues with Apple Notarization today too? It wasn’t easy yesterday but impossible today. Their system status page says everything is working, so I wonder if something changed I was not aware of?
{"code":-1011,"message":"Failed to authenticate for session: (\n \"Error Domain=ITunesConnectionAuthenticationErrorDomain Code=-24169 \\\"Error Description not available\\\" UserInfo={NSLocalizedRecoverySuggestion=Error Description not available, NSLocalizedDescription=Error Description not available, NSLocalizedFailureReason=Apple Services operation failed.}\"\n)","type":"troubleshooting/issuesAppleSubmission.html","resolution":"Check your connection to apple.com servers."}
i got the same error a few days ago using AppWrapper… but shortly after got the email from Apple that my app was properly notarized.
I sent it to Sam and he responded: “I suspect this error is a failure from the segment at Apple end that allows App Wrapper to verify if the Notarization succeeded or not, at least that’s the impression I get from the message.”
I have this too. Been on and off for a couple of days.
Im not getting the notarisation message… App Wrapper stops playing.
"Error Domain=NSCocoaErrorDomain Code=0
\"Status code: 0\
" UserInfo={NSLocalizedDescription=Status code: 0,
NSLocalizedFailureReason=The auth server returned a bad status code.}"
)
So it worked yesterday.
Out of curiosity, I just tried myself and got the same behaviour as Jeff. Even the “check” function of AppWrapper fails with being not able to get a login.
I have been using App Wrapper for about 2 years and I have not changed anything with my configuration since I started. In all this time, things have worked seamlessly. In the past two months, I’ve distributed a signed beta about twice a week.
Today, I get the following error when trying to sign my app for distribution on my website:
⚠️ failed Unable to code sign dmg archive. Developer ID Application:
Steve Albin (xxxxxxxxxx): ambiguous (matches "Developer ID Application:
Steve Albin (xxxxxxxxxx)" and "Developer ID Application: Steve Albin
(4NA35JB38T)" in /Users/stevea/Library/Keychains/login.keychain-db)
To be honest, I don’t fully understand how all this works, but App Wrapper makes things so easy so I don’t have to. After reading the docs and looking at what I can find on Apple’s developer site, I notice that there are two entries for the Develop ID Application certificate and they are identical. As far as I know, this is how it was set up originally and I don’t what I did to add the same cert twice. I do know that I have haven’t touched anything on the developer account since I started using App Wrapper.
I took a chance and deleted one entry and that solved my problem. Maybe Apple is tightening things up on their end. At any rate, something changed somewhere and this fixed things for me.
If you followed the thread, you’ve seen that there have also been issues at Apple’s end. I too just had a successful notarization run after repeated failures this morning (and Wednesday.)
This is not to say that you didn’t find something of your own—but if so, it took more than one fix.
Too late…
I am , however, waiting patiently.
The Apple sites reported ‘All A-OK’ for days, even when it was failing.
( I can imagine the Apple folks now:
‘Cant recreate that here, chum’… ‘Thats Odd’… ‘Nobody else has reported it’)
Isn’t it worrying how much we rely on this fragile chain of stuff in order to be able to even ship our own software?.
Well, this thread inspired me to go ahead and update my DMGCanvas. It’s a little moot, as I use it mainly in my AppWrapper workflow and the latter handles all the signing/notarization. And as of a little while ago, the issue seems resolved, at least temporarily.
I do agree that it could be coincidence that I got a successful notarization after deleting the duplicate cert, but I it was only a few minutes after I tried something else and got the same error. The error message is not very clear, but the word “ambiguous” led me to try deleting the duplicate entry.
BTW, I did note that some folks were reporting intermittent problems. My problem may or may not be directly related - I just thought it may shed some light.
Yeah, I woke up at 1:30 am with Stomach ache. Took the dog for a walk, had a cuppa, watched some TV, went online for a bit until it calmed down. Might have been the Sizzling Beef curry I had for lunch in the big City.
I assume this is when it signs the DMG, when signing the application App Wrapper sends the certificate UUID to handle this, but when it comes to DMG, it’s not an option. Stupid really, but that’s sadly how things roll.
Oh it happens, Apple sometimes simply doesn’t report errors on their own site and yet I have a bunch of people who can’t Notarize and can’t release updates.
Yes it is, it is worrying and frustrating, on the plus side at least we don’t have go through App Review and get a asinine rejection for a critical bug fix release.
