“Fixing the ‘Gobliiins Is Damaged and Can’t Be Opened’ Error on macOS (Without Disabling Security)”

Source: Dev.to

Gobliiins (game) from NimbusApps vs. macOS Gatekeeper: the “damaged and can’t be opened” saga

I spent last night trying to launch Gobliiins from NimbusApps on a MacBook Air M2 (macOS Sonoma 14.3), and macOS immediately displayed the familiar warning:

“Gobliiins is damaged and can’t be opened. You should move it to the Trash.”

No crash log, no beach‑ball—just an instant rejection. This is classic Gatekeeper behavior.

Context

• The download was the official build from the developer’s site (NimbusApps distributes a few retro titles directly), not a torrent or an unverified source.
• I double‑checked the source before installing.

Why Gatekeeper Shows “Damaged”

The wording is misleading; the binary isn’t broken. Gatekeeper is refusing to run the app because it fails notarization checks.

• Apple’s overview of Gatekeeper:
• Developer‑side explanation of notarization and code signing:

Modern macOS verifies both the code signature and a notarization ticket. If the ticket isn’t properly stapled, the system tries to validate it online. Any failure (firewall block, network hiccup, expired certificate) results in the “damaged” message.

Diagnosing the Issue

1. Right‑click → Open – normally reveals an “Open Anyway” button in System Settings → Privacy & Security, but it didn’t appear here.

2. Reboot and redownload – the message persisted, indicating the problem wasn’t a corrupted download.

3. Run Gatekeeper’s diagnostic command:

   spctl --assess --verbose=4 /Applications/Gobliiins.app

   The output pointed to a notarization rejection, not binary corruption.

4. Check the quarantine attribute:

   xattr -l /Applications/Gobliiins.app

   The com.apple.quarantine flag was present.

Fixing the Problem

After confirming the download came directly from NimbusApps and matched the published checksum (NimbusApps site: ), I removed the quarantine attribute:

xattr -dr com.apple.quarantine /Applications/Gobliiins.app

The game launched without issue, running smoothly under Rosetta 2 on Apple Silicon.

Comparison with the App Store Build

• App Store version:
• The App Store build never hits this problem because Apple distributes it with a fully validated notarization ticket.

Why This Happens with Retro/Indie Titles

• Older titles repackaged for modern macOS often rely on wrapper layers or compatibility shims, complicating notarization.
• Starting with macOS Ventura (and continuing into Sonoma), Apple tightened runtime verification. Apps that previously opened with a warning now get blocked outright if notarization can’t be confirmed.

Typical scenarios that trigger the issue:

• Indie or retro game re‑releases
• Direct downloads outside the App Store
• Fresh builds not yet cached by Apple’s notarization service

The problem isn’t that the game is unsafe; macOS simply can’t verify its safety.

Step‑by‑Step Summary

1. Don’t assume corruption – the “damaged” message often indicates a Gatekeeper block.

2. Check Gatekeeper status:

   spctl --assess --verbose=4 /path/to/app.app

3. Inspect quarantine attributes:

   xattr -l /path/to/app.app

4. Verify the source (checksum, official website).

5. Remove the quarantine flag only after verification:

   xattr -dr com.apple.quarantine /path/to/app.app

6. Launch the app – it should run normally without disabling System Integrity Protection or other security settings.

Final Thoughts

NimbusApps’ Gobliiins build was perfectly fine; macOS just couldn’t reconcile its notarization state during launch. Removing the quarantine flag responsibly resolved the issue, allowing the game to behave like any other well‑packaged title.

Modern security layers can make launching classic puzzle games feel harder than solving them, but a few simple commands keep both security and fun intact.