Post

Replies

Boosts

Views

Activity

Reply to Notarization stuck "In Progress" for 4+ days — new Developer ID account, first submission
Thanks Quinn — answers to both questions, and good news. Is e1b209de-… still in history? No. xcrun notarytool history now returns "No submission history." — nothing listed at all. So it does appear to have been garbage-collected at some point; notarytool info was still reporting it In Progress as recently as a few days ago. Have I tried notarizing anything else? As of today, yes. I submitted a new build of the same app (a newer version, so a different payload — signed arm64 app bundle, ~80 MB zip): App submission b53bd371-7132-4278-8d31-c30809ead947 — Accepted within minutes DMG submission aacee6da-973c-49f9-b61c-de0238880ef3 — Accepted in about a minute Both stapled successfully, and spctl --assess on the result gives accepted, source=Notarized Developer ID. So the account and pipeline are clearly healthy, and e1b209de specifically was wedged — consistent with your read that it was stuck waiting on an upload that never completed. From my side this is resolved; I don't need anything further unless the stuck submission is useful to your team as a data point. Thanks again for the help.
Aug ’26
Reply to Notarization stuck "In Progress" for 4+ days — new Developer ID account, first submission
Thanks Quinn — following up as you suggested. The submission is still In Progress. It has now been 9 days (~215 hours) since it was submitted. Submission ID: e1b209de-c30b-42b7-b431-afaf39e9681b Team ID: Q77SU7HBNQ Submitted: July 28, 2026 (late evening, US Eastern) Per your advice I have not resubmitted. xcrun notarytool info continues to return In Progress on every poll, including today. You mentioned: If the request stays stuck for longer than a week, reply back here and I'll take another look. That week has now passed, so I'd be grateful if you could check whether this submission is still progressing normally or has become wedged. If it has, I'm happy to resubmit — I've just held off so far because you noted that resubmitting the same request offers no benefit. For reference, the payload is unchanged from my original post: a zip containing a signed arm64 macOS app bundle (Developer ID Application certificate), ~80 MB compressed. Authentication is an app-specific password via a stored keychain profile rather than an App Store Connect API key. The submitting machine is macOS 26.5.2 (25F84), arm64, with notarytool 1.1.2 (41). Thanks again for the help.
Aug ’26
Reply to Notarization stuck "In Progress" for 4+ days — new Developer ID account, first submission
Thanks Quinn — answers to both questions, and good news. Is e1b209de-… still in history? No. xcrun notarytool history now returns "No submission history." — nothing listed at all. So it does appear to have been garbage-collected at some point; notarytool info was still reporting it In Progress as recently as a few days ago. Have I tried notarizing anything else? As of today, yes. I submitted a new build of the same app (a newer version, so a different payload — signed arm64 app bundle, ~80 MB zip): App submission b53bd371-7132-4278-8d31-c30809ead947 — Accepted within minutes DMG submission aacee6da-973c-49f9-b61c-de0238880ef3 — Accepted in about a minute Both stapled successfully, and spctl --assess on the result gives accepted, source=Notarized Developer ID. So the account and pipeline are clearly healthy, and e1b209de specifically was wedged — consistent with your read that it was stuck waiting on an upload that never completed. From my side this is resolved; I don't need anything further unless the stuck submission is useful to your team as a data point. Thanks again for the help.
Replies
Boosts
Views
Activity
Aug ’26
Reply to Notarization stuck "In Progress" for 4+ days — new Developer ID account, first submission
Thanks Quinn — following up as you suggested. The submission is still In Progress. It has now been 9 days (~215 hours) since it was submitted. Submission ID: e1b209de-c30b-42b7-b431-afaf39e9681b Team ID: Q77SU7HBNQ Submitted: July 28, 2026 (late evening, US Eastern) Per your advice I have not resubmitted. xcrun notarytool info continues to return In Progress on every poll, including today. You mentioned: If the request stays stuck for longer than a week, reply back here and I'll take another look. That week has now passed, so I'd be grateful if you could check whether this submission is still progressing normally or has become wedged. If it has, I'm happy to resubmit — I've just held off so far because you noted that resubmitting the same request offers no benefit. For reference, the payload is unchanged from my original post: a zip containing a signed arm64 macOS app bundle (Developer ID Application certificate), ~80 MB compressed. Authentication is an app-specific password via a stored keychain profile rather than an App Store Connect API key. The submitting machine is macOS 26.5.2 (25F84), arm64, with notarytool 1.1.2 (41). Thanks again for the help.
Replies
Boosts
Views
Activity
Aug ’26