Quill notarization failed
andrewhsu opened this issue · comments
Using quill
0.2.0 to sign and notarize an arm64 binary and I've been getting HTTP 400 error from the notarization server. Signing and notarization with quill
has worked without hiccups throughout this year, but last night started getting an error, but it ended up working after retry and no changes to the usage of quill
.
This morning started getting the error again even after retries:
* notarization failed: unable to start submission: http status="400 Bad Request": body="<HTML><HEAD>\n<TITLE>Bad Request</TITLE>\n</HEAD><BODY>\n<H1>Bad Request</H1>\nYour browser sent a request that this server could not understand.<P>\nReference #7.4c822c17.1692969095.ec8f4c44\n</BODY>\n</HTML>\n"
Is there something that could be done in quill
to address this or is this an issue on the apple web service for notarization?
Hi @andrewhsu! Thanks for the bug report. We're currently investigating.
I'm encountering the same issue. Traditional notorization methods appear to be working, so it doesn't appear to be an issue with Apple's service. The end of the logs are interesting:
[0004] INFO notarizing binary binary=/home/runner/_work/cnquery/cnquery/dist/macos_darwin_arm64/cnquery
[0004] DEBUG loading private key for notary
[0006] DEBUG starting submission name=cnquery-2a79da8a7c8c31f6644862492d5a73e506704c21ee4c149427928382623323e9-2724c814
[0006] ERROR 1 error occurred:
* notarization failed: unable to start submission: http status="400 Bad Request": body="<HTML><HEAD>\n<TITLE>Bad Request</TITLE>\n</HEAD><BODY>\n<H1>Bad Request</H1>\nYour browser sent a request that this server could not understand.<P>\nReference #7.de87645f.1692989352.172281fc\n</BODY>\n</HTML>\n"
[0;34mstatus="In Progress"
[0043] DEBUG submission status id=ab96eaef-67a3-41b2-bebe-5a1936c0b3d7 status="Accepted"
[0054] DEBUG submission status id=9f6dfed0-7d18-4540-bac4-0e4fddacad4b status="Accepted"
In Progress"
[0063] DEBUG submission status id=e8a6f85d-9211-459b-8dd5-10c5e502cd4f status="In Progress"
[0074] DEBUG submission status id=e8a6f85d-9211-459b-8dd5-10c5e502cd4f status="In Progress"
[0084] DEBUG submission status id=e8a6f85d-9211-459b-8dd5-10c5e502cd4f status="In Progress"
[0094] DEBUG submission status id=e8a6f85d-9211-459b-8dd5-10c5e502cd4f status="Accepted"
We are getting a release out in the next few minutes that will address this -- thanks for reporting!
Thanks @wagoodman!