Notarization: "Team isn't configured for notarization"

Code Signing Notarization
This thread has been locked by a moderator; it no longer accepts new replies.
AdamRd OP
Created Jun ’19
Replies 56
Boosts 1
Views 23k
Participants 32

I've tried to notarize my app recently and got the error:

{
  "logFormatVersion": 1,
  "jobId": "...",
  "status": "Rejected",
  "statusSummary": "Team is not yet configured for notarization",
  "statusCode": 7000,
  "archiveFilename": "myapp.dmg",
  "uploadDate": "2019-06-20T06:24:53Z",
  "sha256": "...",
  "ticketContents": null,
  "issues": null
}

I've never heard about "team configuration for notarization" previously. What are the steps to resolve that issue?

Thanks in advance.

Answered by DTS Engineer in 379585022

OK, after a lot of misstarts I finally have some concrete info to share:

  • The Team is not yet configured for notarization error does not indicate a technical issue. As such, it’s not something that DTS (Apple Developer Technical Support) can help you with, either here on the Apple Developer Forums or via a DTS code-level support request.
  • The correct escalation path for this is Apple Developer Program Support. You can contact them via Apple > Developer > Contact Us.

Finally, I’ve locked this thread, for the reasons described in the post below.

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

Revision History

  • 2026-06-18 Corrected various bits of terminology. Fixed a broken link. Added a link to my last post on this thread.
  • 2019-08-29 First posted.
Replies  56
Boosts  1
Views  23k
Participants  32
asaddcorp123 OP
Oct ’25

Same Thing with us aswell, ticket raised more than 1 month ago, no timelines, only a script being read by the apple support team, we cannot provide any timelines, this is in review with the engineering team.

1+ month in the dark and more to come potentially is a very poor and disappointing work ethic in use by apple for it's B2B dealings.
eli_ OP
Dec ’25

Hey guys! Has anyone been able to resolve this issue or is this permanent?..
LN1 OP
Jan ’26

We also send the support case regarding "statusCode 7000 / “Team is not yet configured for notarization" like 2 weeks ago and we didint even get any answer.
bradeac OP
May ’26

Adding to the pile. I opened my first ticket on March 1st. It's now the beginning of May. More than 2 months of error 7000, and I still cannot ship my macOS app.

I followed what the Apple DTS engineers recommend on this forum and contacted Developer Program Support. Four cases so far: 102833704616, 102836645198, 102842517951, 102865000390. I keep getting bounced between advisors. I have submitted my ID twice. Every time I ask for a status, I'm told they will get back to me when they have news. They never do.

This bug has been documented on the forum since 2019. Six years. The "correct escalation path" doesn't actually escalate anything. There is no self-serve path, no SLA, and no follow-through. I'm not asking for a refund. I just want to launch my goddamn business on macOS.

If team configuration is something only Apple can flip, then flipping it should take a day, not a quarter. Customers waiting on you have already built the product, paid the $99, and signed every agreement. The only thing standing between us and shipping is somebody on your side clicking a damn button.

I am filing a complaint with consumer protection authorities this week. This is not incompetence anymore, it's daylight robbery.
feedose OP
1w

Hello,

I am paying for the Apple Developer Program and I still cannot ship my macOS app because notarization is blocked by an account/team-level error, not by my binary.

Every submission from this team fails with the same result:

statusCode: 7000 statusSummary: Team is not yet configured for notarization. Please contact Developer Programs Support at developer.apple.com under the topic Development and Technical / Other Development or Technical Questions.

This has happened across multiple archives and dates, including DMGs and ZIPs, so this does not look like a code-signing issue or an archive-specific problem. xcrun notarytool itself runs normally; Apple rejects the submission on the backend.

I have already contacted Developer Program Support through the official support channel, but I have not received any actionable response or timeline. The only replies I get are that the case is being reviewed.

Please confirm:

  1. What exactly needs to be enabled on my Developer Team for notarization?
  2. Is there a backend account flag or configuration that Apple must switch manually?
  3. Can this be escalated to someone who can actually resolve the team configuration?

I have already paid for the program, but the service I need is not working on Apple’s side, and I cannot ship until this is fixed.

Recent submission examples:

  • 8e14b3a1-5721-4e1a-ab43-000852630e29
  • edf241b0-7a0b-4c26-98a8-d3c6f869b0e1
  • 39c9fdf5-0baa-453c-bdd1-7b884fd9e96a
  • 1700b9b2-17b5-47c9-8854-cbdbc342d708
  • 3d4c986d-af30-4c5c-a987-05ed09b16189

If this is a backend configuration issue, please say so directly and provide an actual timeframe for resolution.

DTS Engineer OP
Apple
1w

feedose, I’ve already responded on your specific thread.

For anyone else who stumbles across this thread, please follow the path described in the recommended reply on this thread. This issue must be handled via official channels. It’s not something I can help you with here on the forums.

Given that, I’m going to lock this thread. There’s no advantage to folks piling on here, and DevForums doesn’t deal well with very long threads. If there’s something specific about your case that warrants further public discourse, please start a new thread:

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

Notarization: "Team isn't configured for notarization"
First post date Last post date
 
 
Q