2+ months blocked on error 7000. Apple's "correct escalation path" is broken.

Question

Created 3w

Replies 6

Boosts 0

Participants 4

I'm posting this so other devs hitting error 7000 know they're not alone, and so this gets some visibility outside the support ticket black hole.

Timeline:

End of February 2026: first notarization attempts. All rejected with status code 7000
March 1st: first support case opened
Today, beginning of May: still blocked. Still error 7000

Four cases: 102833704616, 102836645198, 102842517951, 102865000390. Different advisors each time. I've uploaded my government ID twice. When I ask for a status, the answer is "I'll get back to you when I have news." Then silence.

My setup is fine. Team ID is Y564MF82K8. App is signed with Developer ID Application, hardened runtime, secure timestamp, no get-task-allow, deep verify clean. Apple rejects the submission before inspecting the binary. The block is on Apple's side. Somebody needs to push a button but they cannot agree who needs to push it, so they just pass it from one department to another.

The "correct escalation path" doesn't work. Quinn (Apple DTS engineer) keeps saying on this forum that error 7000 is administrative and the path is Developer Program Support (https://developer.apple.com/forums/thread/118465?answerId=379585022#379585022). I followed that path four times. The cases just sit there.

Threads on this forum about error 7000 go back to 2019. Six years. Devs report cases stuck for weeks, months, with the same scripted responses. Apple knows. Apple does nothing.

I'm a solo dev and I want to do a proper launch of my SaaS on all major desktop platforms. I paid the $99. I built the app. I signed every agreement. I cannot launch on macOS because Apple's departments cannot agree on who needs to push a button.

If anyone here has actually unblocked error 7000, please share what worked. The official path obviously doesn't.

Answered by DTS Engineer in 886728022

If anyone here has actually unblocked error 7000

Yes, many times.

Despite the vague error message, this is not simply someone forgetting to check a box. There is a real issue that warrants careful resolution. I can’t share more details here. This isn’t a DTS concern and, while I’m usually quite happy to wade into other team’s ponds, this specific issue has to be handled through official channels.

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

Boost

Answer 1

DTS Engineer OP

Apple

3w

Recommended

If anyone here has actually unblocked error 7000

Yes, many times.

Despite the vague error message, this is not simply someone forgetting to check a box. There is a real issue that warrants careful resolution. I can’t share more details here. This isn’t a DTS concern and, while I’m usually quite happy to wade into other team’s ponds, this specific issue has to be handled through official channels.

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

0

Answer 2

DTS Engineer OP

Apple

3w

rather that going through the official channels isn’t leading to a resolution

Right. But I can’t speak for other teams here at Apple, which is why I posted that very focused reply.

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

0

Answer 3

Spartan81 OP

1w

Hey Brad,

Since all work at my company has ground to a halt due to the status code 7000 issue, I did some deep-diving on other people's experience with this problem. And to my shock I discovered something:

No one has ever posted online that this problem was resolved for them. There's hundreds of posts about "Team ID not yet configured for notarization" and not a single follow-up success story. Not here, reddit, github communities, etc. We have lots of evidence that many people have encountered this problem, and no evidence that anyone has overcome it.

I wrote a thread about it here: https://developer.apple.com/forums/thread/826413

0

Answer 4

kmansm27 OP

1w

Adding my experience here as well.

I started getting the same 7000 error code randomly two days ago during notarization. It seems to be triggered with larger builds. I tested out notarizing a small 8kb file, and that took 25 minutes, which is much slower than expected but eventually succeeded.

My actual applications are around 500mb, and those either hang forever, or result in the 7000 "Team is not yet configured for notarization" error. I'm blocked on publishing any new app updates.

0

Answer 5

DTS Engineer OP

Apple

1w

To reiterate, there isn’t anything we can do for you here on the forums. As the error message says, you need to contact Apple Developer Program Support.

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

0

Answer 6

Spartan81 OP

1w

Hi Brad,

DTS Engineer posted in my thread that Apple has resolved your problem. He hyperlinked this thread I'm messaging you in and stating that you (as the OP) had this problem resolved. Can you corroborate?

It's in reference to this thread: https://developer.apple.com/forums/thread/824359?page=1#888279022

Quinn wrote: "[1] For example, I happen to know that the original poster on this thread was able to successfully resolve the issue and continue notarising their apps." And the hyperlink for "this thread" in that sentence was to this thread we're in right now.

My fingers are crossed - I really hope this got fixed for you! Maybe there's hope for us!

0