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.
Topic:
Code Signing
SubTopic:
Notarization
Tags: