Notarisation stuck "In Progress" 15h on a new Developer ID cert — even a hello-world is stuck (same pattern as the recent multi-day threads?)

Question

Created 16h

Replies 1

Boosts 0

Participants 2

I'm hitting what looks like the same service-side notarisation issue reported recently (e.g. the "submissions stuck In Progress for days" thread / FB22939442), and would appreciate having my submissions looked at on the backend.

Since 2026-06-25 ~12:00 UTC, every notarytool submission from my team goes to "In Progress" and never reaches a terminal state — no Accepted, no Invalid, no log (Submission log is not yet available, though info resolves the ID fine). The oldest is ~15 hours.

Signing checks out: codesign --verify --strict passes and satisfies the Designated Requirement, hardened runtime with a secure timestamp, no get-task-allow, Developer ID Application. My builds notarised normally yesterday (e.g. 1ad9878b, Accepted 2026-06-24) — but those were on my previous Developer ID certificate. That cert's private key was lost (orphaned login keychain after a reboot), so I re-issued the Developer ID cert on 2026-06-25, and every submission on the new cert has been stuck since.

Key data point: a trivial 5.8 KB signed "hello world" CLI binary (8c138308 below) also hangs "In Progress", so this is account/team-level, not app content. This lines up with the new-Developer-ID evaluation described in the Notarisation Resources Q&A, but several of mine are now past the usual window.

Team: Creative Machines Limited (V95N2B8X7A) Feedback: FB23407538

Stuck submission UUIDs (oldest first):

ef4af6d3-5750-4213-a108-584c75a861cc – 2026-06-25 ~11:59 UTC (oldest)
2d435abc-af77-4447-b2c8-94572b723f34
404a7d9d-9713-42df-99b6-1f144bc27ba1
8c138308-f23f-4df1-85f9-29095587f42b – the 5.8 KB hello-world

This is the only blocker before I can distribute. Is there any way to get these specific IDs cross-referenced against the notary backend queue? Happy to share signed artifacts or the full notarytool poll log.

Environment: macOS 26.4.1 (25E253), Xcode 26.5, notarytool 1.1.2 (41).

Answer 1

DTS Engineer OP

Apple

12h

I'm hitting what looks like the same service-side notarisation issue reported recently

Just so we’re all on the same page here, you’re referring to this thread.

That’s not the same issue you’re seeing. Notably, in that case the developer’s subsequent requests have completed, so it’s just some historical requests that are stuck. In contrast, in your case all requests are stuck. That’s the canonical symptom of the “additional analysis” path. It’s likely you’ve seen this before, but I’ve included a copy of my standard response to such reports at the end of this reply.

My experience is that this state usually clears within a couple of days. If a week passes and your requests are still stuck, feel free to write back here and I’ll take another look.

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.