Oh Hosannah! After 52 days, dozens of calls & emails, and badgering an Apple Engineer at the WWDC forum event, my team ID has been switched to being allowed to do notarizations. No more Status Code 7000! Happily eating crow and I'm grateful this ordeal is over. I hope other people don't have to go to the lengths that I did in order to get the 7000 bug lifted.

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!

[quote='888263022, DTS Engineer, /thread/824359?answerId=888263022#888263022'] And yet I’m telling you that I’ve personally seen them get resolved. Weird eh?[/quote] 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.

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

[quote='885900022, DTS Engineer, /thread/824359?answerId=885900022#885900022'] I [/quote] 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.

Today is Day 24. Still nothing. All work at my company has now stopped due to this bottleneck. Every day is filled with anxiety and worry over this specific issue. I can't believe Apple does this to their developers after charging them a developer fee. Apple Developer Support - please help. After 24 days, my request to remove the status code 7000 block has ended up in a black hole from which no updates or resolution seems to be provided. I formed an LLC to make & distribute mac apps, only to run right into a brick wall from which no resolution is being provided. This is dream-crushing.