First notarization on new Developer ID account stuck "In Progress" for 40+ hours

Question

Created 19h

Replies 3

Boosts 0

Participants 3

Hi — I'm hoping someone from the Notary team can take a look.

This is the FIRST notarization on a brand-new individual Developer ID account, and every submission has been stuck at "In Progress" for well over 40 hours. Normal submissions for me would be expected in minutes.

Team ID: 4FT9BQJ765

Submissions (all still "In Progress" as of 2026-07-20 21:00 UTC):

08953b37-a6a7-43a3-bf76-0bb7d7450b10 (.dmg) submitted 2026-07-19 01:33 UTC (~43h)
3b1c0d76-11e9-4689-b699-e247b4659c5e (.zip) submitted 2026-07-19 01:09 UTC (~44h)
9025ba6f-0f7e-4137-888c-8ca4c7a2f42b (.zip) submitted 2026-07-18 22:44 UTC (~46h)

What I've verified:

My very first submission (9d595afa-5603-42b4-9ac9-0ea638c7eca0) returned "Invalid" within ~3 minutes with real signature errors (unsigned nested dylibs). I fixed those — signed every nested Mach-O inside-out with --options runtime --timestamp using my Developer ID Application cert — so the pipeline and my account clearly work.
Since fixing the signature, every re-submission just hangs at "In Progress" and never completes (both .zip of the .app and a signed .dmg).
Signature checks pass locally: codesign --verify --deep --strict is clean, hardened runtime is enabled, secure timestamp present, and the Developer ID Application cert is valid.

The pattern matches other "first notarization on a new account stuck for 24-48h" reports here. Could someone please manually push these submissions through (or let me know if something on the account side needs attention)?

Tools: notarytool (Xcode 26), macOS 25, Apple Silicon (arm64).

Thanks very much.

Answer 1

Etresoft OP

16h

The pattern matches other "first notarization on a new account stuck for 24-48h" reports here. Could someone please manually push these submissions through (or let me know if something on the account side needs attention)?

And what was the resolution for those similar reports?

Did anyone get anything manually pushed through or did new developer simply have to wait?

Normal submissions for me would be expected in minutes.

So why not use that account? If you're creating a new org account to replace a personal account, then it would make sense to transition to a new account. But I don't see any reason to transition from one individual account to another individual account.

If anything, that's something that could cause delays. Fraud is a huge, extremely lucrative business. $99 isn't even a business lunch for those folks. New accounts get extra scrutiny.

Answer 2

hersheep OP

12h

I don't really get what's your point. I understand the system can assume new accout/org are fraud. But cannot any indenependt developper notorizy an app anymore? And when it stuck in progress, cannot I ask why and seek an resolution??

Answer 3

DTS Engineer OP

Apple

8h

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.

I don't really get what's your point.

I think Etresoft is encouraging you to look for similar threads here on the forums, because:

They all received the same reply.
Many of them [1] are from folks with recently created developer teams.

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

[1] But certainly not all.