Post

Replies

Boosts

Views

Activity

First notarizations from a newly enrolled account stuck "In Progress" for 50+ hours
I enrolled as an individual Apple Developer on 2026-07-18 (Team ID W6ZKZYL87M) and I'm setting up Developer ID notarization for a macOS app distributed outside the App Store (notarytool + Developer ID Application signing). My first notarization submissions have been stuck at status "In Progress" and have never completed: notarize.zip — submitted 2026-07-18 15:34 UTC — id 9787a18e-e4a7-44cc-abe4-94900f51d336 — still In Progress (~54h) probe.zip — submitted 2026-07-19 13:23 UTC — id 0f7db26d-5abb-468a-9ea5-1bec4f71e1cf — still In Progress (~33h) The second submission (probe.zip) is a trivial ~8 KB Mach-O, locally signed with hardened runtime + secure timestamp, submitted purely to isolate the variable — and it is stuck exactly like the real app. This strongly suggests an account-level hold rather than a problem with any particular package. What I've already verified: Developer ID Notary Service is green on the system status page; submissions enter the queue with no error (no 403 / 7000 / auth failure — I authenticate with an App Store Connect API key); I am NOT re-submitting in a loop; agreements look in order in App Store Connect. This matches the documented "in-depth analysis / notarization profile-building" behavior for newly enrolled accounts, but 50+ hours is past the typical 24-72h window, so I would appreciate a check on whether my account is pending notarization profile provisioning or team configuration. I have an open Developer Support ticket (case 102946182596) but am raising it here in case a DTS engineer can look at the account state. Team ID: W6ZKZYL87M
2
0
34
7h
First notarizations from a newly enrolled account stuck "In Progress" for 50+ hours
I enrolled as an individual Apple Developer on 2026-07-18 (Team ID W6ZKZYL87M) and I'm setting up Developer ID notarization for a macOS app distributed outside the App Store (notarytool + Developer ID Application signing). My first notarization submissions have been stuck at status "In Progress" and have never completed: notarize.zip — submitted 2026-07-18 15:34 UTC — id 9787a18e-e4a7-44cc-abe4-94900f51d336 — still In Progress (~54h) probe.zip — submitted 2026-07-19 13:23 UTC — id 0f7db26d-5abb-468a-9ea5-1bec4f71e1cf — still In Progress (~33h) The second submission (probe.zip) is a trivial ~8 KB Mach-O, locally signed with hardened runtime + secure timestamp, submitted purely to isolate the variable — and it is stuck exactly like the real app. This strongly suggests an account-level hold rather than a problem with any particular package. What I've already verified: Developer ID Notary Service is green on the system status page; submissions enter the queue with no error (no 403 / 7000 / auth failure — I authenticate with an App Store Connect API key); I am NOT re-submitting in a loop; agreements look in order in App Store Connect. This matches the documented "in-depth analysis / notarization profile-building" behavior for newly enrolled accounts, but 50+ hours is past the typical 24-72h window, so I would appreciate a check on whether my account is pending notarization profile provisioning or team configuration. I have an open Developer Support ticket (case 102946182596) but am raising it here in case a DTS engineer can look at the account state. Team ID: W6ZKZYL87M
Replies
2
Boosts
0
Views
34
Activity
7h