Early on the morning of November 12, many Mac users experienced an issue that saw some of their Mac apps “damaged” due to an authentication issue.
The issue was reported by many Mac owners over the course of the morning, with many of them seeing a “damaged” error when trying to open a variety of different apps downloaded directly from the Mac App Store. According to reports, opening apps like 1Password, Call of Duty 2, Tweetbot, Acorn, Byword, and many others prompted the error to appear instead of opening the app as would normally happen.
In many cases, as the warning prompt suggests, deleting the app from the computer and reinstalling it from the Mac App Store fixed the situation. In others, Mac owners were forced to sign out of the Mac App Store altogether and then log back in, which would apparently fix the issue as well. For others, though, the apps are still not opening even after these steps have been followed.
Apple, for its part, has issued a new security certificate that should alleviate the problem for the majority of users. This certificate isn’t set to expire until early 2035.
The developer behind Tweetbot, Paul Haddad, tweeted earlier in the morning that the issue seems to be related to expired receipts, which are tied to authentication certification. He would add that receipts now using SHA256 encryption could be causing issues with older versions of OS X:
Well that would explain the MAS problem. pic.twitter.com/Nuqj9Uxxiz
— Paul Haddad (@tapbot_paul) November 12, 2015
Wonder if the receipt now being SHA256 is causing problems with old OS versions? pic.twitter.com/ozOssXWlBR
— Paul Haddad (@tapbot_paul) November 12, 2015
However, many OS X El Capitan users are experiencing the same issues, so Haddad also speculates that the issue could be related to apps contacting the Mac App Store servers simultaneously could be causing a “self inflicted DDOS on Apple’s receipt generation service.”
Update: If you would prefer not to restart, or don’t want to reinstall any apps, there is another option. Craig Hockenberry on Twitter has posted another avenue to take, but this would call for a shell command to be run. You’d need to run the command “$ killall -KILL storeaccountd” to fix the problem:
Just verified that you don’t need to reboot to work around the Mac App Store certificate problem. Instead:
$ killall -KILL storeaccountd
— Craig Hockenberry (@chockenberry) November 12, 2015
Are you, or were you, experiencing these issues?
[via MacRumors; @tapbot_paul]
No comments:
Post a Comment