Notarization: "Team isn't configured for notarization"

Question

AdamRd OP

Created Jun ’19

Replies 48

Boosts 0

Views 17k

Participants 24

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 message does not indicate a technical issue. As such, it’s not something that DTS (Developer Technical Support) can help you with, either here on DevForums or via a DTS tech support incident.
The correct escalation path for this is Developer Programs Support. You can contact them via this link.

Note If that link drops you at the top-level Contact Us page, try logging in first and then clicking on the link.

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Boost

Answer 1

DenSawasdee OP

2w

Dear Apple Developer Program Support,

I am writing to express my deep frustration and confusion regarding the ongoing issue with notarization, specifically the persistent error:

 - Status Code: 7000;

 - Status Summary: Team isn’t configured for notarization

This issue has been documented under Case ID: 102609548157, among others. Despite creating multiple support cases over the past weeks — including escalation to a Senior Advisor within DPS — the issue remains unresolved. What’s even more concerning is the pattern of interaction I’ve experienced: support agents who are initially courteous and express their willingness to help (“It’s my pleasure to support you”) suddenly stop responding the moment I share concrete evidence, such as screenshots or screen recordings, that clearly demonstrate the problem.

This repeated silence — precisely after confirming the core issue — leaves developers like myself completely in the dark. There is no acknowledgment, no timeline, and no guidance. I find it entirely unacceptable that a paid member of the Apple Developer Program is left without meaningful support for an extended period of time, especially when the issue originates on Apple’s side and prevents notarization — a critical requirement for distributing macOS software.

At this point, it is not only a technical failure but also a serious communication failure. Apple must seriously reconsider how support cases like this are handled internally — and how developers are treated when they encounter well-documented systemic problems. The current experience is eroding trust in the reliability and accountability of Apple’s developer support structure.

I am formally requesting that this issue be escalated again — beyond where it previously stalled — and that I be contacted directly by someone empowered to both acknowledge the situation and work toward a timely resolution.

Thank you for your attention. I look forward to your prompt and professional response.

0

Answer 2

nitinbansal85 OP

2d

Suffering from this.

3+ months have passed. 15+ mail threads exchanged. No resolution, no timelines (not even tentative one), no more information other that the same old useless rhetoric: "Our engineers are working on this", and no refunds of Apple developer fee. This bug is now 1+ year old and many many developers and their businesses are suffering because of this.

This I believe could easily be filed as a class-action lawasuit.

If anyone has any alternative, please let me know. My app, which I just launched: https://zenquery.app (after delaying for 3 months), is suffering because of this. I literally had to put a guide in the app-download-dialog to explain all this. And users are just leaving without even doing that 10-second fix once they see this error which is happening due to app not beiing notarized because of this Apple issue. This is hurting my app sales.

If anyone is running notarization-as-a-service, or just willing to help me out in notarizing my app with their account, please let me know. I'll happily pay more than Apple developer fee for single notarization.

1

Answer 3

DenSawasdee OP

1d

In my case all assistants just disapper after I describe my issue with sreenshot and they start ignoring all further request to provide some information on what is going on. I think it's unacceptable behavoor from support team.

0