A few details to save a round-trip, since the first question is usually the state of the oldest request.
Oldest stuck submission, 258583f0-2322-4048-a97c-f290c63d849c (Compliance Vine.zip, created 2026-10-02 17:45 UTC), checked 2026-10-05 21:02 UTC:
% xcrun notarytool info 258583f0-2322-4048-a97c-f290c63d849c <credentials>
Successfully received submission info
createdDate: 2026-10-02T17:45:04.544Z
id: 258583f0-2322-4048-a97c-f290c63d849c
name: Compliance Vine.zip
status: In Progress
% xcrun notarytool log 258583f0-2322-4048-a97c-f290c63d849c <credentials>
Submission log is not yet available or submissionId does not exist
id: 258583f0-2322-4048-a97c-f290c63d849c
Points that I think distinguish this from the failed-upload case in thread 829204:
The requests have not disappeared from notarytool history; they've stayed "In Progress" for 3+ days and info still resolves them.
Submissions come from a GitHub Actions macOS runner via notarytool submit --wait. Small hello-world uploads from the same pipeline complete, and two of them were eventually Accepted (after hours, not minutes), so upload and credentials work.
Three builds of the same app are now held: 258583f0… (10-02 17:45 UTC), a7d7b1b1… (10-02 19:41 UTC), 1274bb4c… (10-03 13:27 UTC). Per the notary Q&A I've stopped resubmitting; a new version will upload once and wait.
The App ID co.joyofwine.compliancevine is registered under the team.
If this is the additional-analysis path for a new Developer ID team, understood, but after three days I'd be grateful if someone could check the internal state of 258583f0… to confirm it's progressing rather than wedged. Happy to file a Feedback report if that's the right vehicle; please let me know the component.
