Notarization submissions stuck "In Progress" for 4 days (new Team ID)

Question

Created 1d

Replies 2

Boosts 0

Participants 2

Title: Notarization submissions stuck "In Progress" for 4 days (new Team ID)

Every notarization submission from my team has been stuck "In Progress" since 11 September 2026. The first one went through; everything submitted after it has never reached a verdict.

Team ID: T36RPB6Z2G Tool: xcrun notarytool (Xcode command line tools), app-specific password App: a Tauri desktop app, Developer ID distribution outside the Mac App Store

Submissions (UTC):

2026-09-11 11:17:19 76bd3fd2-657c-4c3c-9c6b-6e7bc789fb4e In Progress (~92 h) 2026-09-11 11:18:30 1becd424-2ede-4044-b432-7f3afc646270 Accepted (minutes) 2026-09-11 14:39:38 3058ba57-d546-4e82-a781-02a1494eef71 In Progress 2026-09-12 07:24:20 b9568de2-6504-4d83-adc6-40e44f08ba44 In Progress 2026-09-12 09:29:07 572cff54-0e90-4e0d-9908-4ad82759dc9a In Progress (control test)

What I have ruled out:

Credentials and signing are fine — 1becd424 was accepted within minutes with the same certificate, the same password and the same tooling.
It is not my app: as a control I signed a 14 KB Mach-O (a copy of /bin/echo) with the same Developer ID Application identity, hardened runtime and a secure timestamp, submitted it on its own, and it has been "In Progress" for ~70 hours as well.
xcrun notarytool log <id> returns "Submission log is not yet available" for all four, so processing appears to have never started.
codesign --verify --deep --strict passes on the app bundle; the certificate chains to the Developer ID G2 intermediate and shows as valid in Keychain.
The Developer System Status page reports the Notary Service as operational.

This looks like the documented behaviour where an upload is held for in-depth analysis and every later submission queues behind it — but four days with no movement, including on a 14 KB binary, seems beyond the usual delay. I have deliberately stopped submitting so as not to lengthen the queue.

Could someone from Apple check whether 76bd3fd2 is being held, and release it? This is blocking the first signed release of the app.

Answer 1

mathpoem OP

22h

Update: filed as FB24786941.

Still no movement — the oldest submission (76bd3fd2-657c-4c3c-9c6b-6e7bc789fb4e) has now
been "In Progress" for over 96 hours, and so has a 14 KB control binary signed the same
way, so this is not about my app or my credentials.

syspolicy_check distribution Kernally.app reports the expected consequence:

App has failed one or more pre-distribution checks.
Notary Ticket Missing — Severity: Fatal
Suggested Fix: … please make sure to attach the ticket with stapler staple.

There is nothing to staple: the app has been uploaded five times and not one of those
uploads has returned a verdict. I have stopped submitting so as not to lengthen the queue.

Could someone from Apple check whether that first submission is being held, and release
it? This is blocking the first signed release.

Answer 2

DTS Engineer OP

Apple

37m

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.

four days with no movement, including on a 14 KB binary, seems beyond the usual delay.

That’s longer than normal, yes, but it’s not completely unprecedented. If your requests are still stuck after a week, reply here and I’ll take a proper look.

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