Notarization stuck "In Progress" for 4+ days — new Developer ID account, first submission

Question

Created 1w

Replies 4

Boosts 0

Participants 2

My notarization submission has been stuck in In Progress for over four days (100+ hours) and I'd appreciate a status check.

Submission ID: e1b209de-c30b-42b7-b431-afaf39e9681b
Team ID: Q77SU7HBNQ
Submitted: July 28, 2026 (late evening, US Eastern) via xcrun notarytool submit
Payload: a zip containing a signed macOS app bundle (arm64, Developer ID Application certificate), about 90 MB compressed

Additional context:

This is a brand-new Developer ID account — these are my first-ever submissions.
An earlier submission (2b1c4738…) appeared to be lost entirely: after several hours, notarytool info and notarytool history no longer returned it, so I resubmitted the identical zip as the submission ID above.
The current submission definitely exists — notarytool info returns it and reports In Progress on every poll, and has for 100+ hours.
I have not resubmitted again, per the guidance in similar threads that first-time submissions can be held for extended analysis.

I understand from other threads (e.g. 821679, 818256, 814827, 821858) that first submissions from new accounts can be held for in-depth analysis. Could someone take a look at this submission and let me know whether it is still progressing normally, or whether something is wedged and I should resubmit?

Thank you!

Answered by Kevin_Pankhurst in 900899022

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.

Answer 1

DTS Engineer OP

Apple

1w

Accepted Answer

I understand from other threads … that first submissions from new accounts can be held for in-depth analysis.

Right. I’ve included my standard blurb about this below.

Could someone take a look at this submission … ?

My advice here is that you simply wait. If the request stays stuck for longer than a week, reply back here and I’ll take another look.

whether … I should resubmit?

As explained in the the Q&A that I reference below, it makes sense to resubmit if you’re making changes for other reasons. But resubmitting the same request doesn’t offer any benefit.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for additional analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays.

For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive.

Answer 2

Kevin_Pankhurst OP

6d

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.

Answer 3

DTS Engineer OP

Apple

2d

So from our perspective that request is stuck waiting for the upload to complete. I have more background on that in this post.

Given that, I have a couple of questions for you:

If you run the history subcommand in notarytool, do you still see e1b209de-c30b-42b7-b431-afaf39e9681b in the list? And if so, is it marked as In Progress? In theory it should’ve been ‘garbage collected’, but we’ve encountered some problems in that space recently.
Since you submitted e1b209de-c30b-42b7-b431-afaf39e9681b, have you tried notarising anything else? If so, did it also get stuck? And if not, please try this and see what happens.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Answer 4

Kevin_Pankhurst OP

2d

Recommended

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.