Developer ID notarization stuck "In Progress" for 1h+ — previous submissions took minutes

Two notarization submissions for a Developer ID–signed macOS app have been "In Progress" for over an hour. Earlier submissions from this same team, credentials and workflow were all Accepted within minutes.

Submissions

Created (UTC)IDFileStatus
2026-11-05 15:54:4802956de4-0ec7-4009-8f8e-1635f93a10d1ProxyPal.zipIn Progress
2026-11-05 16:37:25e38d47a1-6709-4008-9682-18f9b96af217ProxyPal.zipIn Progress

The second one is a resubmission of the identical zip, sent after
the first had been stuck for about 40 minutes.

What I've checked

  • xcrun notarytool info <id> returns In Progress.
  • xcrun notarytool log <id> returns "Submission log is not yet
    available".
  • Authentication and upload work, and notarytool history lists
    both submissions.
  • codesign --verify --deep --strict passes on the app.
  • Every executable in the bundle has the hardened runtime and a
    secure timestamp.
  • The zip is made with ditto -c -k --keepParent, the same command
    as the earlier accepted releases.
  • The bundle contents are essentially unchanged since the last
    accepted release. The differences are a small generated static HTML
    help folder and version-number changes.

Environment

  • Submitted with xcrun notarytool submit ... --keychain-profile ... --wait from a script.
  • macOS 26 (Darwin 25.6), Xcode toolchain notarytool.
  • Zip is 89 MB, 193 files, and includes two nested .apk files that
    were also in earlier accepted releases.

Questions

  1. Are these two submissions held for additional analysis, or stuck in the queue?
  2. Is there anything on my side I should change?

Update (2026-11-05, 18:17 UTC): still stuck, and it isn't specific to my app.

I've now run Apple's usual isolation test (as described in
https://developer.apple.com/forums/thread/714693), and it points
away from my app's contents.

Additional submissions

Created (UTC)IDFileStatus
2026-11-05 16:59:30c50b8b72-1e93-4cfc-8711-3a3df4498732ProxyPal.dmg (published v0.2.1 release)In Progress
2026-11-05 17:43:201efbff4c-14bc-475c-8691-a086d64c762dTiny.zip (trivial app)In Progress
  • Known-good file: c50b8b72… is the unmodified v0.2.1 release
    DMG (SHA-256
    d6dccadc312a6c4d6661f10a9e273272f281b460dd07382c7e0f31e440e6a1f9).
    Apple accepted this same file in minutes on 2026-10-29 (ID
    f935dd67-ff88-431a-8721-7e07367b1aa0).

  • Trivial app: 1efbff4c… is a ~100 KB universal "hello world"
    binary, Developer ID signed with hardened runtime and secure
    timestamp, zipped with ditto -c -k --keepParent. It has been in
    progress for over 30 minutes. Status of all four (still In Progress at 18:17 UTC)

  • 02956de4-0ec7-4009-8f8e-1635f93a10d1, about 2h 20m

  • e38d47a1-6709-4008-9682-18f9b96af217, about 1h 40m

  • c50b8b72-1e93-4cfc-8711-3a3df4498732, about 1h 18m

  • 1efbff4c-14bc-475c-8691-a086d64c762d, about 34m

notarytool log still returns "Submission log is not yet available" for every one.
Since a trivial signed app and a previously accepted build also hang, this looks like a problem with my environment or account (or a service-side hold), not with the contents of my app. I also noticed that the 0.3.0 zip has about 52 ._* AppleDouble entries from generated Help HTML files, but that doesn't apply to the DMG or the tiny app.

Could an Apple engineer check whether these four submissions are held, and release them? I'm happy to provide anything else.