StatusCode 7000 "Team is not yet configured for notarization". It's been over five days, no resolution

Question

Spartan81 OP

Created Apr ’26

Replies 4

Boosts 0

Participants 2

Hi all,

I'm submitting a Developer ID-signed, hardened-runtime app for notarization. Every submission returns:

"statusCode: 7000

statusSummary: Team is not yet configured for notarization. Please contact Developer Programs Support..."

Team ID: V67NRZ84A2. Apple Developer membership is active, Developer ID Application certificate is valid, signing/verification all clean. Already opened a support case last week via the recommended path. The "contact page" on the developer site said Apple usually responds within 2 business days....

Has anyone hit this and gotten it resolved? How long did it take, and was there a more effective channel than the standard support form? I've seen people on Reddit claim they've actually been able to call a Developer phone line, but I haven't seen a valid phone number anywhere.

I appreciate your response!

Answered by DTS Engineer in 885900022

Has anyone hit this and gotten it resolved?

Yes.

I see folks report this error relatively frequently, and then get it resolved via the support path that the error message itself recommends. See this post for more about it.

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

Boost

Answer 1

DTS Engineer OP

Apple

4w

Recommended

Has anyone hit this and gotten it resolved?

Yes.

I see folks report this error relatively frequently, and then get it resolved via the support path that the error message itself recommends. See this post for more about it.

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

0

Answer 2

Spartan81 OP

1w

I

Quinn….There’s never once been a post by anyone that their status code 7000 problem got resolved.

A review of this forum, GitHub communities, and Reddit show nearly a hundred developers get hit with this status block, and all hundred of them never got the block lifted, regardless of length of time.

If you get hit with the status code 7000 bug, your time as an app developer is over. Thanks for the developer fee, no refunds.

0

Answer 3

DTS Engineer OP

Apple

1w

There’s never once been a post by anyone that their status code 7000 problem got resolved.

And yet I’m telling you that I’ve personally seen them get resolved. Weird eh?

I believe there are a number of filters in play here, including:

Some fraction of folks follow the standard DevPrograms path and the issue is resolved quickly.
Some fraction of folks issue are unwilling to discuss the resolution in public. I’m not going to be drawn into speculation as to why that might be.
Some fraction of folks simply forget to come back and close the loop [1].

I’m sorry I can’t help you with this but this isn’t an issue for DTS to resolve and, while I’m usually 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"

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

0

Answer 4

Spartan81 OP

1w

And yet I’m telling you that I’ve personally seen them get resolved. Weird eh?

Hi Quinn,

I posted (and you quoted) "There’s never once been a post by anyone that their status code 7000 problem got resolved."

Do you have a link to any post by anyone claiming that after they followed the official path that their status code problem was resolved? To be fair I didn't write "There's never been second-hand anecdote by a forum mod with zero evidence provided that someone else's status code 7000 problem got resolved."

You referenced Brad's thread and said you know it was fixed. Brad has been VERY vocal in his status code 7000 problem since February and even went so far as to blanket the internet last week (mid-May) with posts saying that he was still encountering the problem. Can you provide a hyperlink to this very vocal poster where he cites that Apple did fix the issue and he's now able to notarize apps?

@bradeac can you chime in and verify what Quinn is saying that Apple resolved your issue this past week? If so, that will be the very first follow-up post in internet history of someone saying they encountered status code 7000, and Apple resolved it for them.

0