Developer ID notarization submissions stuck In Progress after app transfer

Question

mazzystar OP

Created May ’26

Replies 2

Boosts 0

Participants 2

I’m seeing several Developer ID notarization submissions stuck in “In Progress” after an app transfer.

This is for a macOS app distributed outside the Mac App Store.

The app was recently transferred to a new Apple Developer team. After the transfer, notarization uploads succeed, but the submissions never complete.

The app appears to be Developer ID signed correctly with the new team.

I submitted the app through both Xcode Direct Distribution and command-line notarytool.

The upload succeeds, but the submissions remain in “In Progress”, and no notarization log is available.

Example submission IDs:

5e411dc6-0610-4f9c-8eef-e2a3d0b6a2fb

01bdeeda-3c7e-421a-ae72-6dc081b75e79

986b0c5e-e32f-489f-bc86-3b3c7d7ec91d

193f29b7-b23a-40e7-8324-c076859ca843

notarytool log returns:

Submission log is not yet available or submissionId does not exist

I also see older submissions from the previous day still stuck in “In Progress”, so this does not look like a normal notarization delay.

I’m trying to determine whether this is caused by the recent app transfer / Team ID change, or whether there is anything else I can check locally.

Questions:

Is it expected for Developer ID notarization jobs to remain “In Progress” for more than a day with no log available?
Is there any known issue with Developer ID notarization after an app transfer?
If the upload succeeds but no log is ever generated, is there a recommended escalation path for stuck notarization backend jobs?

Answer 1

DTS Engineer OP

Apple

May ’26

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth 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.

Is it expected for Developer ID notarization jobs to remain “In Progress” for more than a day with no log available?

Yes, if you hit the in-depth analysis path mentioned above.

We don’t document a detailed list of criteria that cause a request to get on that path. However, one thing I’ve noticed here on the forums is that folks with new apps, or new teams, are commonly affected. Given that, I’m not super surprised that you’re seeing it after an app transfer.

My advice here is that you simple wait. This state usually clears in a day or two. If a week passes without any progress, reply back here and I’ll dig deeper.

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

Answer 2

mazzystar OP

18h

Quinn — following up as you suggested ("if a week passes without any progress, reply back"). It's now been over two months, and the situation has moved from "stuck In Progress" to outright rejection.

Every notarization submission since then — via both Xcode Organizer and notarytool — now returns the identical log:

"status": "Rejected",
"statusSummary": "Team is not yet configured for notarization.
 Please contact Developer Programs Support...",
"statusCode": 7000,
"issues": null

Team: H4N8Z7K4S4 (SmashMelon LLC, US organization; I'm the Account Holder). This is the team the app was transferred to. The same team ships iOS updates via App Store Connect with no problems, and the latest Program License Agreement is accepted (June 20, 2026).

Recent submission IDs:

7ec8ec66-ab23-46e3-996f-22ff9f463593 (June 15)
f7546486-255e-484c-a08f-dd6a2df391df (June 17)
56754783-3436-4142-84a4-d8cbfe400fc1 (June 23)
79f3a014-812f-4cca-969c-e41a432c24fe (July 6)

issues:null on every log suggests the binary is never scored at all — the rejection happens at a team-level gate. Notably, Apple's cloud signing service happily issues Developer ID signatures for this team (signing is cloud-managed; the portal lists no local certificate), yet the notary service refuses it. The two systems appear to disagree about whether this team is provisioned.

I also opened a Developer Support case (102898059793) in early June. They requested identity and company verification (passport, formation docs, IRS 147-C), which I uploaded June 15, but the case has been "still under investigation" for four straight weeks with no state change.

Given the transfer origin you flagged back in May, this really looks like the team's Developer ID / notarization provisioning was never completed after the transfer. Is there anything I can check from the Account Holder side, or can this be escalated to whoever owns team provisioning?

Thanks Quinn — really appreciate you keeping an eye on this tag.