Hello, We are experiencing an issue where two recent notarization submissions are stuck indefinitely in the "In Progress" status, with no notarization logs available to inspect. Details for the impacted submissions:
- Team ID: FYSU26MR78
- Submission ID 1: afb11f83-06c2-40c8-89ef-ad7042d1f309 (Submitted: 2026-08-02 05:21 UTC — 68h)
- Submission ID 2: 65aeb3d0-c204-4906-84c3-f08487989f3f (Submitted: 2026-08-02 16:23 UTC — 57h)
Two details that may help narrow this down:
- Two OTHER submissions from the same team, made within hours of these on the same day, were ACCEPTED normally — including a .dmg of the same application from the same build pipeline and signing configuration. Submission ID 1 has therefore been overtaken by both submissions made before it.
- Submission ID 2 is a resubmission of the exact same file as Submission ID 1 (byte-identical), made after the first stalled. It is now also stuck, so this does not appear specific to a single upload.
The build is a universal (arm64 + x86_64) app signed with a Developer ID Application certificate, hardened runtime enabled, secure timestamp present. codesign --verify --deep --strict passes and the bundle satisfies its Designated Requirement. It is a large bundle — roughly 465 MB .dmg with several thousand nested Mach-O binaries. Uploads succeed and return a submission ID every time; only processing never completes. Is there a known backend delay with the notary service, or can an Apple engineer assist in checking the status of these submission tickets? If they are stuck rather than queued, is there any way to have them cancelled so we can resubmit cleanly? notarytool does not appear to expose a cancel command.