If you've just installed an app on your Mac and see this error message:
"App.app" is damaged and can't be opened. You should move it to the Bin.
Don't worry; your App is likely not damaged at all, and caused by a security feature in macOS can be easily bypassed if you trust the source. Here's what's happening and how to fix it.
Why This Happens
macOS includes a built-in Gatekeeper feature to protect users from potentially malicious apps. If an app:
- Isn't downloaded from the App Store
- Isn't signed or notarized by an Apple-verified developer
- Was downloaded via a browser (like Chrome)
- Has been flagged as "damaged" even when it isn't
The App may be blocked from opening by default, which often affects legitimate apps, especially those from smaller developers or Chrome-based apps installed via chrome://apps.
How to Fix It (Step-by-Step)
Follow these exact steps to open the App safely:
1. Add the App to your Applications folder (or locate it via chrome://apps if it's a Chrome-based app).
2. Double-click the App to open it.
You'll see the error:
"App.app" is damaged and can't be opened. You should move it to the Bin.
3. Click "Cancel" (Do not move it to the Bin)
4. Click "Cancel" again if prompted.
5. Go to System Settings → Privacy & Security.
6. Scroll down to the Security section.
7. You should now see a message like:
"'App.app' was blocked to protect your Mac."
(e.g., "Lovable.app was blocked…", "Grammarly.app was blocked…")
8. Click "Open Anyway"
9. A new dialog will appear:
"App.app" is damaged and can't be opened. You should move it to the Bin.
10. This time, click "Open"
11. macOS may prompt you to confirm your identity using Touch ID or your Mac password.
12. The App will now open normally!
13. Optional: Pin the App to your Dock for easy access in the future.
Chrome Apps Note
This process works the same whether you're opening:
- Chrome Web Apps from chrome://apps
- Standalone apps downloaded from the internet
The key is that once macOS sees your manual approval through Privacy & Security > Open Anyway, it will no longer block the App.
Is It Safe?
If you trust the App's source, bypassing this warning is generally safe. MacOS is simply warning you because it can't verify the App's developer credentials, not because it is a broken app.
In Summary
This '"App.app" is damaged and can't be opened. You should move it to the Bin' error doesn't mean your App is truly damaged; it's just Apple being cautious. By navigating through a few security settings, you can tell macOS, "I trust this," and open the App without issue.
.png){kind=logo}
Join in the Discussion