Notary server down - 500 internal server error

I'm also seeing the same issue today.

I tried to run xcrun notarytool store-credentials again, but I get:

[13:23:26.009Z] Debug [API] Received response status code: 500, message: internal server error, URL: https://appstoreconnect.apple.com/notary/v2/asp?, Correlation Key: EFNNWSQB2XZUUYA2EBWMOVQUMY

I saw a few posts above suggesting using altool, and after a little bit of trial and error, this seemed to work for me:

xcrun altool -t osx -f "/path/to/app.dmg" --primary-bundle-id --output-format xml --notarize-app -u apple-id-goes-here -p "app-specific-password"

...then take the RequestUUID and you can check the status using:

xcrun altool --notarization-info RequestUUID-goes-here -u apple-id-goes-here -p "app-specific-password"

...this once that's done you can staple:

xcrun stapler staple "/path/to/app.dmg"

Hope this helps others who are running into the same issue!

I'm seeing the same issue. Does this have something to do with a recent update?

NLTeo's post on page 1 of this thread solved the issue for me.

I'm having the same issue - using electron-builder to build electron app and signing it fails with this error

Error: HTTP status code: 500. Internal server error. Error communicating with authentication service. Please try again at a later time. 40 failedTask=build stackTrace=Error: Failed to notarize via notarytool

At the end of this day, we still don't have a legal working resolution:

• notarytool and app-specific password -> still not working, HTTP 500
• altool -> not contained in newest xcode command line tools (xcode-select --install), depreciated by notarytool
• App Store Connect API -> not legal to use (as far as I understand the license)

@Apple Developer Support: We paid for a membership but are still unable to create running apps.

PLEASE FIX IT!

Just wanted to share my results as well:

So when using the older xcrun altool, I don't get the 500 error, and when using the Xcode notarization GUI I don't get the 500 error. 

However, as soon as I try and use the newer xcrun notarytool I get the 500 error (I'm specifically passing in an Apple ID/Team ID/App-Specific password). I also get the same 500 error when I attempt to perform a store-credentials command with notartytool. 

Seems like this is a recent serverside issue, as this is happening across Xcode versions 13.2.1 and 13.4

This is a disruptive problem for us as well. Same 500 errors. Had to spend time yesterday re-implementing altool with polling, which seems to take much longer than using notarytool with --wait. Lots of time wasted troubleshooting and updating build scripts, when I have product updates I need to distribute.

How does Apple not see the 500 errors, which are internal server errors. How do you get a "local" 500 error, unless from terrible programming? ¯_(ツ)_/¯.

Happening to me, too.

I am experiencing the same issue:

xcrun notarytool history -p notarytool_Notarize_Credentials --verbose

[20:58:24.738Z] Debug [MAIN] Running notarytool version: 1.0.0 (21), date: 2022-05-24T20:58:24Z, command: /Applications/Xcode_13.4.app/Contents/Developer/usr/bin/notarytool history -p notarytool_Notarize_Credentials --verbose

[20:58:24.752Z] Debug [KEYCHAIN] Attempting to load Keychain data for profile name: notarytool_Notarize_Credentials

[20:58:24.761Z] Debug [KEYCHAIN] Found Keychain password item "notarytool_Notarize_Credentials" with ID XXXXXXXXXX:myemail_gmail.com.

[20:58:24.764Z] Info [API] Initialized Notary API with base URL: https://appstoreconnect.apple.com/notary/v2/

[20:58:24.764Z] Info [API] Preparing GET request to URL: https://appstoreconnect.apple.com/notary/v2/submissions?, Parameters: [:]

[20:58:24.765Z] Debug [AUTHENTICATION] Delaying current request to refresh app-specific password token

[20:58:24.766Z] Info [API] Preparing GET request to URL: https://appstoreconnect.apple.com/notary/v2/asp?, Parameters: [:]

[20:58:24.766Z] Debug [AUTHENTICATION] Authenticating request with Basic Auth. Username: myemail_gmail.com, Password: private, Team ID: XXXXXXXXXX

[20:58:24.767Z] Debug [TASKMANAGER] Starting Task Manager loop to wait for asynchronous HTTP calls.

[20:58:25.354Z] Debug [API] Received response status code: 500, message: internal server error, URL: https://appstoreconnect.apple.com/notary/v2/asp?, Correlation Key: K5WIK7YU5TDMH5GUROU3DHII6M

[20:58:25.356Z] Error [TASKMANAGER] Completed Task with ID 2 has encountered an error.

[20:58:25.357Z] Debug [TASKMANAGER] Ending Task Manager loop.

Error: HTTP status code: 500. Internal server error. Error communicating with authentication service. Please try again at a later time.

Hi all, thank you for reporting the error to us.

This is indeed an error on our end that we are actively working on. Sorry for the inconvenience in the interim.

same here.

Earlier I wrote:

As to the current situation, it’s working for me right now:

I have some specific info to share about that, although it’s really only confirming things that other folks on this thread have worked out already.

The reason why it was working for me, and for some folks but not others, relates to the authentication mechanism. I always authenticate with the notary service using an API key rather than an app-specific password, and this problem only showed up when using an app-specific password.

My understanding is that the app-specific password issue is now resolved. That’s reflected in the Developer > System Status page and by the latest posts on this thread. If you continue to have problems, please let us know.

If you temporarily switched to using altool, please revert back to notarytool. As we announced at WWDC 2021, altool has been deprecated for the purposes of notarisation.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

...and we're back!

Cool.

Just ’cause I’m curious, was this with:

• notarytool or altool?

• Password or key authentication?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Just an FYI that this is occurring once again-- use of notarytool w/ app-specific password is consistently failing today ("Error: HTTP status code: 500. Internal server error. Error communicating with authentication service. Please try again at a later time."), whilst altool is still available and working using app-specific password.