Notarization server down?

The status page at https://developer.apple.com/system-status/ indicates that the "Developer ID Notary Service" is up.

But I've had a notarization "in progress" for more than an hour. Usually it takes a few minutes.

Anyone else having problems?

Anyone else having problems?

I just notarised a simple test app promptly and without incident.

I’m not sure what happened to your original notarisation request. If it’s still stuck you should retry. If that works, please file a bug against the notary service, including the request UUID of both the original stuck request and the new working request.

If your new request also gets stuck you should try notarising a trivial test app and post the results back on this thread.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@apple.com"
@eskimo, We have experienced slowliness on ntoarization requests starting on Sunday. We send several requests per day for the last months without any major issues but on these last days response is very slow and we are getting errors returned due to duplicate whereas in the past this was managed differently. Is there any documentation of any changes on the notarization end that we can get? We serve several major apps that are getting impacted by this. We don't have any clue of what is happening as the status shows as available.
AFAIK nothing has officially changed here. We do, however, see issues with the notary service in production from time to time. If you have specific issues then I recommend that you file a bug against the notary service. Make sure to include the UUIDs of the requests where you saw the problem.

Please post your bug number, just for the record.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@apple.com"
@eskimo - thanks for the reply. Digging into our logs we found there was a change on the preferred methods for uploading the file for notarization. This change started to reflect on 11/7/2020:

Then:
[2020-10-27 14:32:40 PDT] <main> DBG-X: parameter PreferredTransports = [HTTP, Signiant, Aspera, DAV]

Now:
[2020-11-09 17:47:03 PST] <main> DBG-X: parameter PreferredTransports = [HTTP, DAV]

Why the change? We are not controlling this. Signiant is way faster than DAV. Is there a plan to bring Signiant and Aspera back?

FYI - We logged this (FB8893559)

Thanks!!!


Notarization server down?
 
 
Q