{"id":29672,"date":"2020-08-04T16:33:49","date_gmt":"2020-08-04T20:33:49","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=29672"},"modified":"2025-04-08T10:08:12","modified_gmt":"2025-04-08T14:08:12","slug":"apple-remote-kills-long-time-developers-apps","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2020\/08\/04\/apple-remote-kills-long-time-developers-apps\/","title":{"rendered":"Apple Remote-Kills Long-time Developer’s Apps"},"content":{"rendered":"

William Gallagher<\/a> (also: Charlie Monroe<\/a>):<\/p>\n

As Apple continues to face controversy<\/a> over its App Store policies and fees, software developer Charlie Monroe<\/a> has told AppleInsider<\/em> that the company has killed all his apps with no warning. Each of his ten macOS apps, and two that are also iOS, remain available to buy in the App Store, but Apple has stopped them launching.<\/p>

[…]<\/p>

“Looking into it, I found that Apple revoked my distribution certificates, which generally kills the apps remotely.”<\/p>

“When I sign in to my developer account, it asks me to enroll to the Apple developer program and I don’t seem to be in the Apple developer program anymore,” he continued, “even though the apps that I have on the App Store are still available.”<\/p><\/blockquote>\n\n

Daniel Jalkut<\/a>:<\/p>\n

\n

Every Apple platform developer’s worst nightmare. It’s bad enough that a seemingly innocuous developer has been effectively banned from development, his apps rendered non-functional, but ... no explanation? That is just cold.<\/p>\n<\/blockquote>\n\n

Charlie Monroe<\/a>:<\/p>\n

In the morning no one got back to me. They did now, but only said on the phone they have no idea what’s wrong and are passing the issue to internal team... 🤔<\/p><\/blockquote>\n\n

Charlie Monroe<\/a>:<\/p>\n

\n

macOS displays a message that the app “will damage your computer” just because the certificate was revoked, which IMHO is bordering with slander. Damages your name and brand. Aside from users unable to use your apps, of course.<\/p>\n<\/blockquote>\n\n

Craig Hockenberry<\/a>:<\/p>\n

The wording for the dialog and intent behind signed code is to protect from malware.<\/p>\n

If this action isn’t based on that, Apple is the one that’s damaging their name and brand.<\/p>\n

And if it is? At least give the developer a chance to rectify the situation.<\/p>\n<\/blockquote>\n\n

Thomas Tempelmann<\/a>:<\/p>\n

Can’t run the long-installed app any more. Can’t open the downloaded installer, not even with right-click + option key, even on High Sierra.<\/p>

This means for us Mac devs that Apple not only has the power to make it near-impossible (at least for the layman) to run your publically available app, but they actually assume the right to do so as they please. They’re judge, jury and executioner. Doesn’t that scare you?<\/p>

Apple’s dev account was originally meant to be necessary only to sign your app, to ensure it can be checked against malicious modification. But now, it’s become the stick by which Apple alone controls which apps can run on a Mac.<\/p><\/blockquote>\n\n

Nick Lockwood<\/a>:<\/p>\n

\n

I wish I could be a fly on the wall when decisions like this get made. Was this a snap judgement made in response to some automated alert, or an executive decision? Did someone suggest contacting the developer but get overruled? Or did nobody even consider it? So many questions.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n