I'm distributing an open-source command-line tool outside the App Store. Every notarization submission from my team has been stuck "In Progress" since my very first one on 2026-08-01. Fourteen submissions across five days, and not one has ever reached a terminal state — not Accepted, not Invalid, not Rejected. notarytool log returns "not yet available" for all of them, so I have no diagnostic output to work from. Team ID: HYZ2FM38JG Representative submission IDs (all "In Progress"): 3bc8fa7b-f35d-4a70-9b82-4b23b176f746 — 2026-08-01 19:49 UTC, the first submission my team ever made 79455e8c-b1bb-4bc4-9268-5a81b35dfdb7 — 2026-08-03 17:56 UTC 4ecaae74-8b43-4e1d-b18c-c3786d1f8c1e — 2026-08-04 18:11 UTC Plus two fresh submissions made today, 2026-08-05, after a bundle identifier change (see below). Full notarytool history available on request; all fourteen read the same. What I'm submitting: a single Mach-O command-line executable (Rust, arm64 and x86_64 built separately), zipped with ditto -c -k --keepParent <binary> <zip>. No app bundle, no DMG. Each zip is about 2 MB. Signature (codesign -dvvv, today's arm64 build): Identifier=dev.puchalla.trot Format=Mach-O thin (arm64) CodeDirectory v=20500 flags=0x10000(runtime) Authority=Developer ID Application: Marcus Puchalla (HYZ2FM38JG) Authority=Developer ID Certification Authority Authority=Apple Root CA Timestamp=5. Aug 2026 at 11:49:51 TeamIdentifier=HYZ2FM38JG Runtime Version=14.5.0 codesign --verify --strict --verbose=2 reports "valid on disk" and "satisfies its Designated Requirement". Hardened runtime is on, the signature carries a secure timestamp, and there are no entitlements at all, so no get-task-allow. Authentication: App Store Connect API key at Team level, via --key / --key-id / --issuer. Every submission is accepted immediately and returns an ID, so upload and authentication are clearly working — only the processing behind them never runs. Things I have already ruled out: Submission volume / throttling. The very first submission, made on an empty queue, stalled identically. Throttling also rejects at submit time with an error rather than issuing an ID. My CI setup. Some of these submissions come from a GitHub Actions macos-14 runner and others (trot-test.zip) were made by hand from my own Mac with notarytool directly. Both stall the same way, so this follows the account rather than any particular build environment. The bundle identifier. It was com.marcuspuchalla.trot, on a domain I do not own. I changed it today to dev.puchalla.trot, which is reverse-DNS off a domain I do control, and resubmitted. No change — the new submissions sit "In Progress" alongside the rest. (I did not expect this to matter for Developer ID distribution; I mention it so you know it has been eliminated.) Signing problems. Verified above. A signing error would come back Invalid with a log, quickly, rather than as indefinite silence. Expired or unaccepted agreements. Membership active, Program License Agreement accepted, nothing outstanding in the portal or App Store Connect. I understand from other threads here that uploads are sometimes held for in-depth analysis, and that new accounts see this more often — I'm entirely willing to wait if that's all this is. But five days with fourteen submissions and zero completions, including from a brand-new account that has never had a single submission succeed, seemed worth reporting in case something is genuinely wedged on my team's side. Could someone check whether these are actually progressing? One further question, in case it's relevant: I'm submitting a bare Mach-O executable rather than an app bundle, DMG or pkg. It's a command-line tool, so there's nothing to staple to. Is that path handled differently by the analysis pipeline? Every similar report I found here involved a bundle.