I've read Quinn's response on thread 827096 about Developer ID notarization submissions held for "in-depth analysis" on new teams. That guidance fits the general shape of what I'm seeing, but I'm posting a separate thread because (a) my situation does not involve an app transfer — these are the first-ever notarizations under a newly activated team, and (b) I've passed the "usually clears in a day or two" expectation and want to ask a few specific questions that thread didn't cover.
Setup
macOS app distributed outside the App Store
Rust universal binary (aarch64-apple-darwin + x86_64-apple-darwin, merged via lipo)
Binary signed with Developer ID Application, hardened runtime (--options runtime) and Secure Timestamp (--timestamp)
.pkg built via pkgbuild + productsign with Developer ID Installer
Team was activated 2026-05-29 — these are our first notarizations under the account, no prior submission history
Submissions
Submission A — submitted 2026-05-29T19:18:02Z, currently 100+ hours In Progress
Submission B — submitted 2026-06-01, currently 30+ hours In Progress, identical polling behavior
(Submission IDs available to DTS on request — happy to share via DM or via the Apple Developer Support case we have open on the same issue.)
I submitted B specifically to test whether A was a one-off stuck queue entry. Both stalling identically rules that out and points at a team-level condition rather than a per-submission issue.
xcrun notarytool log returns Submission log is not yet available or submissionId does not exist for both — same as the OP's experience on 827096.
Local verification — every check in TN2206 passes
$ pkgutil --check-signature .pkg
Status: signed by a developer certificate issued by Apple for distribution
Signed with a trusted timestamp on: 2026-05-29 19:15:36 +0000
Certificate Chain:
Developer ID Installer: ()
Developer ID Certification Authority
Apple Root CA
$ codesign --verify --strict --verbose=2
valid on disk
satisfies its Designated Requirement
$ codesign --display --verbose=4 | grep -E '^(Authority|Timestamp|Runtime|TeamIdentifier)='
Authority=Developer ID Application: ()
Authority=Developer ID Certification Authority
Authority=Apple Root CA
Timestamp=May 29, 2026 at 12:13:40 PM
TeamIdentifier=
Runtime Version=26.5.0
xcrun notarytool history returns successfully and lists both submissions, so authentication and connectivity to the notary service are healthy. Developer System Status has shown the Developer ID Notary Service as "Available" throughout.
Questions for DTS (Quinn or whoever picks this up)
Quinn's 827096 reply describes "in-depth analysis" for new teams clearing in a day or two. Is there a known long-tail beyond that window, and is there anything a team can do to flag itself as ready for processing rather than waiting passively?
Does resubmitting (as I did with submission B) extend, restart, or sit independently from the review of submission A?
Is the review-completion clock driven by the team's activation date, the first submission, or the cumulative submission history? In other words, does each new submission help the team's signal, or does the system wait for the first to fully clear before evaluating subsequent ones?
If we hit the 1-week mark Quinn referenced as the escalation tripwire without resolution, what's the recommended channel — a follow-up reply here, a new thread, Feedback Assistant, or another route?
We also have an open Apple Developer Support case on this, currently silent for 4 days. Working that channel in parallel.
Thanks in advance for any guidance — and thanks to Quinn for the public visibility he's given this pattern on 827096; it's the most useful documentation on it I've been able to find.
