'<App> Can't Be Opened' on Mac? Here's How to Fix It

You double-click an app you’ve used for years and macOS pops a dialog: ” can’t be opened.” No additional explanation in some versions, a vague hint in others. Sometimes it’s followed by “because the developer cannot be verified.” Sometimes “because it is from an unidentified developer.” Sometimes nothing at all.

The wording matters because each variant points at a different cause and a different fix.

Pin down which variant you’re seeing

The exact dialog text tells you which subsystem blocked the launch.

• ” can’t be opened. You should move it to the Trash.” — Gatekeeper considers it actively malicious. Don’t override this casually.
• ” can’t be opened because the developer cannot be verified.” — Gatekeeper, but a softer block. The app was signed by a developer Apple no longer recognizes.
• ” can’t be opened because Apple cannot check it for malicious software.” — Notarization missing or expired.
• ” can’t be opened because it is from an unidentified developer.” — Older Gatekeeper text for unsigned apps.
• ” can’t be opened because the file is damaged.” — Code signature verification failed; quarantine flag may be wrong.
• ” can’t be opened on this Mac.” — Architecture mismatch (PowerPC, 32-bit Intel, or Intel-only on Apple Silicon without Rosetta).

Read the dialog carefully. The right fix depends on which one you got.

Quick fixes by variant

Gatekeeper: “developer cannot be verified” or “Apple cannot check”

For apps you trust:

1. Right-click (or Control-click) the app icon → choose Open from the context menu.
2. The dialog now offers an Open button. Click it.
3. macOS remembers and lets you launch normally going forward.

If the right-click trick doesn’t show Open: System Settings → Privacy & Security → scroll to “Security” → there’s an “Open Anyway” button next to the blocked app’s name. Click it, authenticate, and try again.

”File is damaged” — clear the quarantine attribute

This message often lies. The file isn’t damaged; macOS thinks it might be tampered with because of a quarantine flag.

In Terminal:

xattr -d com.apple.quarantine /Applications/AppName.app

Replace AppName.app with the actual name. The app launches normally afterward. If you get “No such xattr,” the flag wasn’t there — the app really is damaged or its signature is broken. Re-download from the source.

”Can’t be opened on this Mac” — architecture mismatch

If you’re on Apple Silicon and the app is Intel-only, install Rosetta:

softwareupdate --install-rosetta --agree-to-license

Then launch the app. macOS prompts to confirm running under Rosetta the first time.

If you’re on Intel and the app is Apple Silicon-only, you can’t run it. Look for an Intel build or an alternative.

If the app is 32-bit (older than 2019), macOS Catalina and later won’t run it at all. There’s no override — find an updated version.

Skip the manual huntSweep clears the cruft that triggers most of these errors — caches, logs, leftover daemons. Download Sweep free →

When the app worked yesterday and won’t open today

Different problem class. The app already cleared Gatekeeper but something changed.

1. Restart the Mac. Releases stuck file handles and clears Launch Services cache.
2. Check disk space. A nearly full startup disk causes weird launch failures. Apple menu → About This Mac → More Info → Storage Settings.
3. Check the app for updates. A macOS point release sometimes breaks older app builds; the developer’s update fixes it.
4. Reset Launch Services:

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user

That command rebuilds the app database. Takes a couple minutes; Dock and Finder refresh during it.

5. Clear the app’s caches. Quit the app, then in Finder go to (Cmd+Shift+G) ~/Library/Caches/<bundle-id> and ~/Library/Saved Application State/<bundle-id>.savedState. Move them to Desktop, try launching, trash if it works.

Permission and Full Disk Access blocks

Some apps refuse to launch (or launch silently and quit) without specific permissions:

• Full Disk Access — System Settings → Privacy & Security → Full Disk Access. Add the app, restart it.
• Accessibility — same panel, Accessibility section. Required by automation tools.
• Screen Recording — required by screen capture, video conferencing.
• Files and Folders — granular per-folder permission.

If an app launches and immediately quits, check Console.app → search for the app name → look for “TCC” entries. TCC is macOS’s privacy framework, and TCC denials are a common silent cause of launch failures.

When Gatekeeper says “Move to Trash”

This is the strongest warning. macOS’s malware database has flagged the bundle hash as known-bad.

1. Don’t override. This block is rarely a false positive.
2. Re-download from the official site. Make sure you’re on the developer’s actual domain — not a typosquatted clone.
3. Check the developer’s official site for security advisories. Some popular apps have been impersonated or had supply-chain compromises.

If you’re certain the app is legitimate (and you got it from the developer directly), contact the developer. They may have an updated build whose hash isn’t flagged.

Don’t reinstall macOS yetSweep clears the buildup that’s actually causing the issue. Free for macOS →

Reinstall when nothing else works

Some launch failures persist through every diagnostic step. Reinstalling clears them:

1. Quit the app and any helpers (Activity Monitor → search the name).
2. Drag the app from Applications to Trash.
3. Empty Trash, then restart.
4. Re-download from the developer’s site or Mac App Store.
5. Launch.

Cleaning up leftover files also helps if a previous install was corrupt — check ~/Library/Application Support/<app>, ~/Library/Caches/<bundle-id>, ~/Library/Preferences/<bundle-id>.plist.

Read crash logs if the app launches and immediately dies

Sometimes the launch error dialog doesn’t appear, but the app bounces in the Dock and disappears. Open Console.app → Crash Reports. Find the entry for the app. The Termination Reason at the top often spells out the cause:

• “Library Validation Failed” — corrupt code signature, re-download.
• “DYLD, missing library” — the app needs a framework that’s not on your system. Install the prerequisites listed by the developer.
• “EXC_BAD_INSTRUCTION” — corrupt binary; re-download.

Specific cases worth noting

• Apps from email attachments. Quarantine flag is set automatically. Use the right-click Open workaround once.
• Apps from Time Machine restore. Sometimes the quarantine flag survives the restore. xattr -d com.apple.quarantine /Applications/AppName.app clears it.
• Apps installed before a macOS upgrade. Older apps relying on deprecated frameworks may stop working. Check the developer’s compatibility note for your macOS version.
• Open-source apps not notarized. Many GitHub-distributed apps are signed but not notarized. Right-click → Open works the first time.

When it’s the App Store

If a Mac App Store app fails to launch:

1. App Store → click your account name → check for pending updates.
2. If the app shows “Open” instead of “Update” but won’t open: hold Option and click the app’s icon → “Always Reopen” can be toggled.
3. Last resort: drag the app to Trash, then re-download from the App Store.

Mac App Store receipts are stored separately from the app bundle, so reinstalling rarely loses your purchase entitlement.

When the answer is contact the developer

Some launch failures are bugs in the app you can’t work around: a license server that’s down, a required cloud service that changed APIs, a macOS feature the app depends on that Apple deprecated. If you’ve tried the steps above and the app still won’t open, the developer’s support is the right next step. Send them the crash report from Console.app and the exact wording of the error dialog.

The “can’t be opened” wall feels final, but ninety percent of the time it’s a Gatekeeper override, a quarantine flag, or a missing permission. The dialog text is the map — read it carefully and the fix is right there.