How to fix: the application is damaged and can’t be opened. You should move it to the Trash”

The error “The application is damaged and can’t be opened. You should move it to the Trash” on macOS typically occurs when an app’s code signature is invalid, its files are corrupted, or Gatekeeper flags it as untrusted (e.g., due to a revoked certificate or incomplete download).

This can happen with apps from outside the Mac App Store or after macOS updates. Below are step-by-step solutions to fix this using built-in macOS tools.

Here are the fixes to such permission problem: –

---

Step-by-Step Solutions

Solution 1: Redownload the Application

• Why: The app might be corrupted from a bad download or transfer.
• How:
  • Move the app to Trash:
  • In Finder, right-click the app (e.g., /Applications/MyApp.app) > Move to Trash.
  • Empty Trash: Right-click Trash > Empty Trash.
  • Redownload from the original source (e.g., developer’s website, GitHub).
  • Move the new copy to /Applications if it’s not already there.
• Test: Double-click the app. If the error persists, proceed to the next solution.

Solution 2: Bypass Gatekeeper via System Settings

• Why: Gatekeeper may block the app even if it’s not truly damaged.
• Try Opening:
  • Double-click the app in Finder. You’ll see the “damaged” warning.
• Open System Settings:
  • Apple menu () > System Settings (or System Preferences on macOS 12 or earlier) > Privacy & Security (or Security & Privacy) > General.
• Allow the App:
  • Look for “‘[App Name].app’ was blocked” and click Open Anyway.
• Retry:
  • Double-click the app again—it may open after this override.
• Note: This option appears only after attempting to launch the app.

Solution 3: Remove Quarantine Attribute via Terminal

• Why: The app might have a quarantine flag causing macOS to mislabel it as damaged.
• Open Terminal:
  • Go to Applications > Utilities > Terminal.
• Remove Quarantine:
  • Run this command, replacing the path with the app’s location (drag the app into Terminal to auto-fill):
    sudo xattr -r -d com.apple.quarantine /path/to/MyApp.app
  • Example:
    sudo xattr -r -d com.apple.quarantine /Applications/MyApp.app
  • Enter your admin password.
• Launch:
  • Double-click the app—it should open if the issue was quarantine-related.

Solution 4: Check and Fix Code Signature

• Why: A broken or revoked code signature can trigger the “damaged” error.
• Verify Signature:
  • In Terminal:
    codesign -vv /path/to/MyApp.app
  • Look for output like “invalid” or “revoked.”
• Fix (if Possible):
  • If “revoked” or “invalid,” redownload the app (Solution 1)—the developer may have updated it.
  • If unsigned, force macOS to accept it:
    sudo codesign --force --deep --sign - /path/to/MyApp.app
  • This re-signs the app with a generic signature. Retry opening it.
• Note: This may not work for notarized apps (Catalina and later).

Solution 5: Disable Gatekeeper Temporarily

• Why: Gatekeeper might misidentify the app as damaged due to strict security checks.
• Open Terminal:
  • Run:
    sudo spctl --master-disable
  • Enter your admin password.
• Launch the App:
  • Double-click the app—it should open.
• Re-enable Gatekeeper:
  • After use:
    sudo spctl --master-enable
• Caution: This disables all Gatekeeper checks—use only briefly.

Solution 6: Right-Click Open

• Why: This bypasses the initial Gatekeeper check, sometimes avoiding the “damaged” label.
• How:
  • In Finder, right-click the app > Open.
  • Click Open in the dialog (if available).
• After: Future launches may work normally.

Solution 7: Repair Disk Permissions (Rare Case)

• Why: Corrupted system permissions might interfere.
• Open Disk Utility:
  • Applications > Utilities > Disk Utility.
• Run First Aid:
  • Select your startup disk (e.g., “Macintosh HD”) > First Aid > Run.
• Retry: Open the app after repairs.

---

Troubleshooting

• “Open Anyway” Missing:
• Attempt to open the app first, then recheck Privacy & Security. If still absent, use Terminal (Solution 3 or 5).
• Terminal Errors:
• Verify the app path (drag it into Terminal) and ensure sudo is used correctly.
• Persistent “Damaged” Error:
• Check file integrity:
  ls -l /path/to/MyApp.app
• If incomplete (e.g., smaller than expected), redownload.
• macOS Version: On Catalina and later, notarization is stricter—Solutions 3 or 5 are more likely to work.

---

Notes

• Security: Bypassing Gatekeeper or re-signing apps can expose your Mac to risks—only trust apps from verified sources.
• Common Causes: Revoked certificates (e.g., after Apple updates), interrupted downloads, or unsigned apps.
• App Location: Move it to /Applications—Gatekeeper is stricter with ~/Downloads.