Notary service never completes our team's submissions: "In Progress" for 3+ days, even a hello-world binary

Question

Created 7h

Replies 2

Boosts 0

Participants 1

Our team (Team ID WQS88HK2V3) began notarizing with a new Developer ID Application certificate on October 2nd. Since then, no submission has completed. Every one sits at "In Progress"; two production app uploads from October 2nd are still there after three days.

To rule out our app, I submitted a minimal signed hello-world binary (a main that returns 0, signed with hardened runtime and a timestamp, zipped with ditto). Today's one, 151fa89a-f115-4b8b-9713-d3c733f7b3ad, submitted 2026-10-05 15:32 UTC, was still "In Progress" after 20 minutes with --wait. Earlier hello-world tests took many hours to reach "Accepted"; one from October 3rd (1274bb4c-a0a5-4af6-a991-ac8fc3194656) is still "In Progress".

What we've verified:

notarytool history authenticates and lists every submission under the team, so credentials and upload are fine.
codesign -dv shows TeamIdentifier=WQS88HK2V3 and the Developer ID chain.
The Apple Developer Program License Agreement was accepted on 2026-10-02; nothing is pending on the Membership page.
System Status shows the Developer ID Notary Service as available.
No App Store Connect app record exists, which I understand is expected for Developer ID distribution.

Stuck production submissions:

258583f0-2322-4048-a97c-f290c63d849c — 2026-10-02 17:45 UTC
a7d7b1b1-286f-47ae-ab51-f20b0634f27e — 2026-10-02 19:41 UTC

We have a Developer Support case (102984780721); so far the guidance has been to upload to App Store Connect, which doesn't apply to Developer ID notarization.

Is there a known hold on first submissions from a newly provisioned team, and is there anything on our side that would clear it? This is blocking a release to our customers.

Answer 1

JoyArchivist OP

2h

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.

Answer 2

JoyArchivist OP

2h

Filed as FB25073190 (Developer Tools & Resources; the area list has no Notarization entry, so it's under "Something else"). It carries the same submission IDs and references this thread and support case 102984780721.