Hi everyone,
For the past three days I've been unable to notarize my app — every attempt fails with an HTTP 500 error from Apple's notarization service. What's unusual is that the error occurs not only during submission, but also when simply validating credentials via store-credentials.
Example:
$ xcrun notarytool store-credentials "notarytool-password" \
--apple-id <id> --team-id <team> --password <app-specific-password>
Validating your credentials...
Error: HTTP status code: 500. Internal Server Error
Request ID: K6NYCMIFNM66OI2WRG3ORZEDUE.0.0
Please try again at a later time.
Since the failure happens at credential validation — before any package is even uploaded — I'm fairly confident this is a server-side issue, not something wrong with my setup or the binary. I've tried across different network connections, same result.
Has anyone else been hitting this? Is there a known outage or incident on Apple's notarization infrastructure? Any way to escalate or get a status update beyond checking developer.apple.com/system-status/?
Thanks
First up, please re-test to confirm that you’re still having the problem. The notary service is quite reliable IME, and when I do see errors like this they often get fixed based on internal monitoring.
If you confirm that you’re still having the problem, please file a bug about it and then post the bug number here.
Finally, I often find that folks can work around issues like this by switching from app-specific password authentication to key-based authentication. So, in addition to filing that bug, you should try that switch to see if it can get you back notarising again.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"