Fix “App is Damaged Can’t Be Opened” Error Messages in Mac OS X
Some Mac users have discovered they are unable to open some applications downloaded from the Mac App Store. When attempting to open an impacted app in OS X, a message stating “Name.app is damaged and can’t be opened. Delete Name.app and download it again from the App Store.” Another variation is a pop-up window appearing asking a user to “Sign in to use this application on this computer” requesting an Apple ID and password.
The reason these app can’t be opened error messages are appearing is because of a code signing security certificate expired, this is not user error or anything to do with user involvement, it’s basically something with DRM that was messed up on the Mac App Store side but is now impacting some applications that were downloaded from there. Yes, this is a strange and frustrating error message, but it’s easily resolvable.
Resolving the “App is damaged and can’t be opened” Error in OS X
This error message tends to appear in new versions of OS X:
- Reboot the Mac, this alone may be sufficient to fix the problematic apps and remove the error message
- If a reboot does not fix the app, delete the application (just drag it to the Trash and empty), then re-launch the Mac App Store and download the app again via the Purchases tab or by searching for the app manually
- Open the once impacted apps again, they should now work fine
Resolving the “Sign in to use this application on this computer” Error in OS X
This error message may appear in older versions of OS X:
- Close the “sign in to use this application” error dialog box when you see it, and reboot the Mac instead
- Upon reboot, open the Mac App Store and log in to your Apple ID to re-authenticate the Mac and all related apps
- Open the apps as usual
That should be all that is required to get your apps working again in OS X.
The Quick App Error Fix for Advanced Mac Users: Killing a Process
You can target the storeaccountd processes via Activity Monitor if you want, or use the command line if you are comfortable with the Terminal:
sudo killall -v storeaccountd
There are typically two “storeaccountd” processes running, one as user, and one as root, and thus using killall on both is sufficient to resolve the issue.
Those interested in learning a bit more about the technical details behind these error messages can refer to this Twitter thread, which reveals the certificate that expired and speculates on various contributing factors.
Well that would explain the MAS problem. pic.twitter.com/Nuqj9Uxxiz
— Paul Haddad (@tapbot_paul) November 12, 2015
Obviously if you haven’t seen these error messages on your Mac, you have nothing to worry about, and can go about your merry way. But, should you see them, at least know it’s a simple fix, the apps aren’t actually damaged, it was just an error on the Apple side of things with a quick remedy.
- Mac Apps Not Opening? Apps Crashing on Launch? Fix Error 173 with OS X App Store Apps
- Fix Repeated “Your message could not be sent” Messages Error on Mac
- Fixing OS X Install Errors “can’t be verified” and “error occurred while preparing the installation”
- “Internal Error” or “Unknown Error” Occurred During iOS Install? Easy Fix!