Lately Apple seems slower to respond to accept the upload through SD Notary. During peak times I get errors in SD Notary before Apple Responds an obvious time-out. However when I “Fetch history” all shows accepted. Is there a way you can either increase the timeout waiting for response from apple or help figure out how to prevent this? My Enhanced Applet can be sizable at times? Any advice is appreciated.
The timeout is set to 1800 seconds. That should be plenty – when it takes longer than that, it’s usually a problem at Apple’s end that can take any amount of time to fix.
That said, you can change the default value using defaults in Terminal. The key to use is prefSubmitTimeout and the value should be in seconds.
It stops responding after 5-6 mins. I’ve never seen it wait that long. I’ll see what setting is.
That sounds like something drastic has gone wrong. SD Notary uses the prefSubmitTimeout value along to notarytool. According to its documentation:
[–timeout duration]
notarytool will exit after polling for duration. The Notary service will continue processing the
submission even if the timeout is reached.
Agreed. It happens to me enough to be an annoyance during assumed peak submission times later in the day. It happens after signing, uploading and while Awaiting result from Apple… appears in the Log.
@ShaneStanley sees like since I moved to Sequoia 15.1, I have been experiencing a ton of failures on submitting my enhanced app to apple. I test the app signing /usr/sbin/spctl --assess --type exec -vv and it comes back good. It always fails early on waiting for apple. Any suggestions?
the end of the submission log says:
Termination status: 10
StandardOut: (null)
StandardError: (null)
09:20:23.933: Error 105553134970960 in notarytool submit.
Anyone else experiencing errors submitting app today to Apple through SD Notary 2?
Network issues? SD Notary is simply reporting what Apple’s notarytool is returning – it has no visibility beyond that.
@ShaneStanley …so I finally worked out the issues:
Got a new Mac and copying the Developer Certs from the old keychain to a new one thinking should be fine but exporting them from the old keychain and importing them from the P12 file was the correct procedure. That resolved the notary submit. Not sure why I couldn’t see in any log there was a certificate signing issue. I even tested the signing prior to submitting to Apple. If anyone has insight here from you where I could have seen the issues or how I could have identified the issue using logs is very welcome!
Welcome to Apple’s opaque land 
1 Like