Developer ID notarization submissions disappear from notarytool history — Team 8786B65DT4

Update — I retried once today using the same existing, locally verified v0.9.6 signed macOS app. I did not create a new Developer account, Team ID, or certificate.

New submission ID: 84a9d943-a2e5-461d-b6de-dc5fbec0549e

Created: 2026-09-04T19:59:09.758Z

The upload was accepted and notarytool info currently reports:

status: In Progress

I will not submit further duplicates unless Apple staff recommends doing so.

Update — the third submission has now reproduced the same failure.

Submission ID: 84a9d943-a2e5-461d-b6de-dc5fbec0549e

It was created on 2026-09-04T19:59:09.758Z and initially showed “In Progress.”

Today, xcrun notarytool info returns:

“Submission does not exist or does not belong to your team.”

And xcrun notarytool history --keychain-profile BELLE_EPOQUE_NOTARY again returns:

“No submission history.”

This is now the third separate submission from the same signed v0.9.6 macOS app to disappear without reaching Accepted or Invalid. Please investigate this as a team-level Notary Service backend issue.

The most common reason for requests to just disappear like that is beacuse the upload never completed. If you submitted the request via the notary API, then there are all sorts of reasons why that can happen. However, if you submited the request via notarytool there’s really one one reason: notarytool failed to run to completion.

Are you submitting these requests manually? Or from some sort of CI/CD server? I often seen problems like this where the person is using a CI/CD server and notarytool fails but their server doesn’t capture that failure accurately.

So, if you’re using a CI/CD server I recommend that you submit by hand, passing in the --verbose flag to see what it reports.

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

Update: I manually submitted a new one, this issue is the new one still in progress after more than 48 hours.

The current submission is still visible to notarytool and remains In Progress:

Submission ID: ddb5c464-38db-4329-ae0c-2e9456f13997

Submitted: 2026-09-09T19:40:40Z

Archive: BelleEpoque-v0.9.7-beta-mac-notary-retry-20260908-complete.zip (~942 MB)

This upload was performed manually with xcrun notarytool submit --wait --verbose. The verbose log confirms that all 189/189 multipart-upload parts completed successfully and that Apple reported “Successfully uploaded file” before processing began.

A minimal probe submitted earlier by the same team was accepted successfully:

Probe submission ID: 2ddbbfb4-283a-494c-8355-4f39b7c67429

Status: Accepted

This seems to rule out basic team provisioning, certificate, and credential issues. Could Apple DTS / the notary service team please inspect why the full submission remains In Progress rather than completing as Accepted or Invalid?

The current submission is still visible to notarytool

Cool. That, and your view of the verbose logging, suggests that the upload is complete, which brings us to second common issue that folks bump in to, namely, additional analysis. I have a standard spiel about that, which I’ve included below.

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

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for additional analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays.

For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive.