Notary server down - 500 internal server error

Getting exactly the same right now. Good to know it's (probably) not my end.

Same here for the last 8 hours or so. But the Apple System Status page doesn't show any issues.

https://developer.apple.com/system-status/

I can understand that Apple System Status page might not automatically flag certain types of faults with this service... but I find it incredible that there is apparently not even a cursory monitoring service that can recognise that there are HTTP 500 faults occurring.

I need to issue an urgent app update to my users. This unacknowledged fault is causing me significant uncertainty and stress.

Super annoying...

Not that it's a great solution at all, but I commented out my changes to use notarytool from a few months ago and restored my use of the old process using altool and just successfully submitted and notarized my bundle! Haha. So @gpdawson that might be on the menu as a temporary workaround.

EDIT: confirmed -- I switched my release to use altool in order to get new builds available tonight. Seems like just a month back or so I was getting deprecated warnings and couldn't actually get a successful result with altool, and now it's back. Never a dull moment...

Same thing's been happening for me for several hours, with no indication from Apple that they know anything's wrong.

Same Issue as well. Started happening this morning.

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

The same here. I wonder why this happen again and again since last month.

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

Same for me, server seems down for 12 hours now. Same problem occured obviously earlier, see https://developer.apple.com/forums/thread/698401.

If altool is a valid replacement, could someone please post the substitution for these lines here?

xcrun notarytool submit "my.dmg" --wait --keychain-profile "my_profile"

xcrun stapler staple "my.dmg"

Same error since Monday on our side Error: HTTP status code: 500. Internal server error. Error communicating with authentication service. Please try again at a later time.

To start, see this post for general advice on this topic.

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

% date 
Tue 24 May 2022 09:41:08 BST
% xcrun notarytool history …credentials…
Successfully received submission history.
  history
    --------------------------------------------------
    createdDate: 2022-05-09T15:19:19.872Z
    id: 8ef67861-46f6-4f0a-9d71-00626ddf06e5
    name: hello.zip
    status: Invalid
    …

Given the latest update on this other thread, it seems that this is either intermittent or user-specific. They opened a bug about this and I’ll that to escalate the issue.

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

As to the current situation, I get the following, maybe it helps for debuging:

macmini:test$ xcrun notarytool history --keychain-profile "my_profile" -vvvv

[10:22:32.154Z] Debug [MAIN] Running notarytool version: 1.0.0 (21), date: 2022-05-24T10:22:32Z, command: /Library/Developer/CommandLineTools/usr/bin/notarytool history --keychain-profile my_profile -vvvv

[10:22:32.167Z] Debug [KEYCHAIN] Attempting to load Keychain data for profile name: my_profile

[10:22:32.180Z] Debug [KEYCHAIN] Found Keychain password item "my_profile" with ID XXXXXXXXXX:YYYYY.

[10:22:32.187Z] Info [API] Initialized Notary API with base URL: https://appstoreconnect.apple.com/notary/v2/

[10:22:32.188Z] Info [API] Preparing GET request to URL: https://appstoreconnect.apple.com/notary/v2/submissions?, Parameters: [:]

[10:22:32.189Z] Debug [AUTHENTICATION] Delaying current request to refresh app-specific password token

[10:22:32.191Z] Info [API] Preparing GET request to URL: https://appstoreconnect.apple.com/notary/v2/asp?, Parameters: [:]

[10:22:32.192Z] Debug [AUTHENTICATION] Authenticating request with Basic Auth. Username: YYYYY, Password: private, Team ID: XXXXXXXXXX

[10:22:32.195Z] Debug [TASKMANAGER] Starting Task Manager loop to wait for asynchronous HTTP calls.

[10:22:32.938Z] Debug [API] Received response status code: 500, message: internal server error, URL: https://appstoreconnect.apple.com/notary/v2/asp?, Correlation Key: RFD32TYXONHX7XXXXXTWFTT5RQ

[10:22:32.939Z] Error [TASKMANAGER] Completed Task with ID 2 has encountered an error.

[10:22:32.940Z] 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.

I also had the same problem, but found a solution. What did the trick for me was creating an AppStore Connect API key and use it with notarytool store-credentials (using the --key --key-id --issuer options). Using that method of authentication works, I managed to notarize 2 dmg images.

The xcrun notarytool history shows 500 error too. It looks it fails when app specific login is used and not for the other authorization methods.

It works via App Store Connect API:

1. Create API key and download it https://appstoreconnect.apple.com/access/api

2. Copy key-id and issuer from same page

3. Store to keychain

xcrun notarytool store-credentials Notarize --key apple-connect-api-key.p8 --key-id 1234567 --issuer 11f28c89-0bbc-47b8-bb65-ad719eb08e4c

1. Use to notarize

xcrun notarytool submit ParetoUpdater.zip --team-id 12345678 --progress --wait --keychain-profile "Notarize"

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