Notarization: "Team isn't configured for notarization"

I keep getting rejected with this error.

The correct path forward here is as I described in my 29 Aug post. There isn’t anything that I, or anyone else here on DevForums, can do to help you resolve this issue.

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

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

Hi AdamRd, I got the same error as yours. Did you solved the problem?

@eskimo We are also still experiencing this issue and it is blocking us from updates to our applications.

Apple Developer Support have pushed us over to Feedback Assistant, however we are not getting any response there. How can we proceed ?

You need to push back on Apple Developer Program Support here; this is very much their bailiwick.

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

Hi @eskimo

Would appreciate your help here. I appreciate the undertain times right now, however:
- TSI are not responding
- Apple Developer Support say that they're only an admin team

- Feedback Assistant are not responding.

What would be an appropriate escalation path from here ?

Please drop me a line via email (my address is in my signature).

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

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

The same problem. DPS tell me contact DTS. DTS tell me contact DPS. ... Cycle five times.

then,

DPS tell me send to Feedback Assistant 100 times.

No responding...

What's wrong with Apple Developer Support Department?

This issue in Developer Program Support’s responsibility. I’ve seen a number of developers stuck in this loop and DPS is taking steps to avoid that in the future (r. 81235504).

In your specific case, I believe that my DTS colleague Matt is already working with you on this, and I’ll let him follow up via a private channel.

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

Facing the same issue for a 3rd party app. Any updates on a method for how to solve this?

For this specific message, Team isn't configured for notarization, the advice in the Apple Recommended answer is still correct.

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

Even though we've been notarizing our macOS app already for quite some time, we've just been suddenly affected by this error. One of the reasons we started distribution via our website (.dmg) instead of App Store was to deploy improvements immediately and avoid certain issues and delays we've had with the review process. Apparently it's not that simple.

{
  "logFormatVersion": 1,
  "jobId": "3fba6b2a-4db9-4897-9b51-5b6f1a361401",
  "status": "Rejected",
  "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.",
  "statusCode": 7000,
  "archiveFilename": "....zip",
  "uploadDate": "2023-07-22T07:57:16Z",
  "sha256": "316674c07aee66d2d0649e99d0d1bbb10c52ecbe241d19fc3e4d649d95ed2c99",
  "ticketContents": null,
  "issues": null
}

We've contacted the Developer Programs Support and are full of hope that this gets resolved in a timely manner.

@tomekit Did you get it resolved?

I sold many pre-order copies of my app with a promised launch date. Tested throughout the week, and the notarization process was working fine. However, on the release date, I encountered the 'team is not yet configured for notarization' error. I have everything checked on App Connect, all contracts, etc.

Talk about bad timing. Really annoying that even after paying $100, distributing outside the store, and Apple still finds a way to block the launch I've worked really hard on. I'll seriously think twice about building for this platform in the future.

Completely uninstalling Command Line Tools for Xcode and installing it again resolved the errorrr.

Hello Adam,

I have helped multiple clients with this kind of issue. This usually means that your code has been detected as "malicious" software.

You say that you are using Electron and this could be problematic; as "older" versions has many security vulnerabilities.

At some point, your account could have been blacklisted; so you could no longer notarize. But during the first rejections, you could still revert it by correcting the issues in your code.

1. try to notarize a simple "hello world" application to verify that your team is OK for notarization. You could notarize from Xcode or using notarytool

2. if 1) is working, update your software to use the latest Electron framework and this should solve your issue.

I think that Apple should give a more comprehensive feedback when software is using a problematic "known" framework.

Regards

David

I have received the same response:

"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."

I have just escalated via the channels recommended, however, I am feeling discouraged that this issue is so widespread and seemingly unaddressed. I am responsible for getting this application deployed for my job and I am reaching a deadline. Anyone else have any luck?

Thanks. -Will

To repeat:

• We are not able to help you with this here on the forums.

• DTS is not able to help you with this in general.

You need to escalate this with Apple Developer Program Support, as explained in this thread’s recommended answer.

I’m sorry but that’s all I can do for you here.

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

Hi @DTS Engineer , do you have advice on what to do when Apple Developer Program Support doesn't reply back at all?

We contacted them as you suggested and it has been two weeks and they haven't responded back yet. The case ID is 102570284981. What should we do? Keep creating a new support ticket until we get a response?

@DTS Engineer

Hello Quinn,

I'm also following this thread while dealing with the "Team is not yet configured for notarisation" issue. I took your advice and contacted the Apple Developer Program Support team.

I stressed several times to multiple team members and senior team members over the phone and via email your explicit instructions/advice:

• It's only within Developer Programs Support's ability to address/fix this.
• Developer technical support cannot address this.

Despite this, they clearly and explicitly reiterated that they cannot do anything except escalate this to engineering and are also unable to contact engineering for updates. They consistently repeat that there's literally nothing further they can do until engineering responds.

Conversely, as an engineer, you have reiterated numerous times across various forum threads here that you cannot do anything to help this issue, and advise contacting Developer Program Support.

This back-and-forth has continued for 39 days for my specific case, with neither providing meaningful updates nor a clear timeline for resolution. Each team insists that the responsibility lies with the other, creating an impossible stalemate. Despite numerous calls and emails, the response has remained unchanged.

As a developer, I'm left without any actionable path forward. Clearly, Apple's internal communication or processes must be addressed to resolve this delegation loop. Clearly, it has gone on for some time given the length of this thread.

Could you please escalate this broader communication issue internally? Individual developers have no power to influence this deadlock.

Thank you for your assistance.

Scott

I’m sorry but I’m not able to argue your case here. I have a reasonable understanding of the background to this issue and, while I can’t go into the details, I’m absolutely sure it’s not something that DTS can resolve.

It’s not uncommon for these requests to get misdirected within Apple Developer Program Support. If you’re talking with DevPrograms and they attempt to direct you to DTS, feel free to send them a link to this thread. If that’s not sufficient, they can contact me internally.

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

@ScottBlack Hello. Have you got any updates on your issue? I faced the same problem but didn't get any help from DPS yet.

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.

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.

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.

I encountered the same issue three weeks ago, but it has not been resolved yet. Every time, they just say it has been submitted to the relevant team. I'm extremely disappointed with Apple's technical support.

I'm on the same boat: same error, three weeks, no ETA, no info - extremely disappointing.