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
| 2026-11-05 15:54:48 | 02956de4-0ec7-4009-8f8e-1635f93a10d1 | ProxyPal.zip | In Progress |
| 2026-11-05 16:37:25 | e38d47a1-6709-4008-9682-18f9b96af217 | ProxyPal.zip | In 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>returnsIn Progress.xcrun notarytool log <id>returns "Submission log is not yet
available".- Authentication and upload work, and
notarytool historylists
both submissions. codesign --verify --deep --strictpasses 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 ... --waitfrom a script. - macOS 26 (Darwin 25.6), Xcode toolchain
notarytool. - Zip is 89 MB, 193 files, and includes two nested
.apkfiles that
were also in earlier accepted releases.
Questions
- Are these two submissions held for additional analysis, or stuck in the queue?
- Is there anything on my side I should change?