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

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"

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"

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"

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