team 29ZP95Z3NX, a new Developer ID account whose first notarization was yesterday. Three submissions, none has ever reached a terminal state:
cefe29b8-628c-4aaf-84f2-bb376dbce5b6 2026-08-05 15:12 UTC now 15h 044fdff5-2a8a-4fe7-8572-c1569b7c56cc 2026-08-05 17:32 UTC now 13h 45185356-2b9f-4d1f-93d1-76521b606553 2026-08-05 19:36 UTC now 11h
notarytool log returns "not yet available" for all three. The middle one is a control I built to rule my own bundle out: four lines of C, universal, 100 KB, signed with the same Developer ID certificate, --options runtime --timestamp, no nested code, no entitlements, no provisioning profile. It hangs exactly like the real app.
What makes me post rather than just wait is that three other teams are describing the same thing right now:
· Kamyab, team XBX2Z359B8 — first three submissions succeeded on 2026-07-31, every one since has been stuck, earliest now well past 26h. Independently reports that a 16 KB signed hello-world hangs exactly like their 40 MB DMG. Developer Program Support case 20000125886455 open since 2026-08-02, no reply yet. · ruththapa, team FYSU26MR78 — two submissions stuck at 68h and 57h, while two others from the same team, same day, same build pipeline and signing configuration were accepted normally. · Dom_W, team TSH4QXMCU8 — brand-new membership, first submissions, 24h+.
I've read the additional-analysis answer in the thread from ruththapa, and I understand that first submissions from an unknown account can be held while the system learns to recognise them. That fits my case and Dom_W's. It doesn't seem to fit the other two: Kamyab's first three went through and everything after stopped, and ruththapa had submissions accepted on the same day as the ones that stalled. Those two look like requests entering the queue and not leaving it, rather than an unfamiliar app being examined.
Two observations that might narrow it down. Size and content appear to be irrelevant — two of us have now independently confirmed that a signed hello-world of a few kilobytes behaves identically to a full application bundle. And the earliest stuck request anyone has reported is Kamyab's from 2026-07-31 22:40 UTC, which would make this roughly six days old rather than something from today.
For completeness on my side: macOS 26.5.2, Xcode 26.6, notarytool 1.1.2 (41). The app is a universal x86_64/arm64 bundle, hardened runtime, secure timestamp, codesign --verify --strict passes and it satisfies its designated requirement. Certificate valid until 2027-02-01, membership active, no pending agreements. Uploads always succeed and return a submission ID; only processing never finishes. Developer ID Notary Service has shown as operational throughout.
What would actually help: could someone look at whether these requests are genuinely queued or stuck, and if they are stuck, release or cancel them so the queues can drain? notarytool has no cancel command, so there's nothing any of us can do from the outside. Several of us are blocked on shipping.
Happy to provide anything further.
