ewtheckman

ericthehalfbee said:

ewtheckman said:

Apple implements a system that causes an application to stop working even when nothing has changed, requiring an update from the developer and reinstallation, and which does not take into account real-world cases such as users needing to use an older version of software or applications which are no longer being updated, and some of you have the nerve to blame the developer?!?!? Don't you think you're taking the Fan Boyz thing a bit far?

Fan Boyz? What are you, a 12 year old troll?

Thousands upon thousands of developers don't seem to have this problem. It's absolutely their fault.

They don't? That's very presumptive of you. From the article:

The "crash" turned out to be a feature of macOS in PDFPen's case. According to TidBits, the "taskgated-helper" system app examines a code signing certificate and compares it to the "entitlements" list. Should the the provisioning profile be linked to an expired certificate, macOS blocks the app with the expired certificate from launching.

However, other apps not updated as frequently, or abandoned by developers, may stop working with no recourse by users to get them to start working again.

These particular applications where included as examples, not the only apps having problems. In these cases, the developers were very active in creating a solution to a problem caused by Apple.

Apple implements a system that causes an application to stop working even when nothing has changed, requiring an update from the developer and reinstallation, and which does not take into account real-world cases such as users needing to use an older version of software or applications which are no longer being updated, and some of you have the nerve to blame the developer?!?!? Don't you think you're taking the Fan Boyz thing a bit far?