When Kenophobia Met Gatekeeper
Yesterday I took a swing at getting Kenophobia (Kenophobia - Spot Light Hub) running on my MacBook Air M2 (macOS Ventura 13.6). Looked simple enough—it’s a small productivity utility that hooks into Spotlight indexing and custom shortcuts. But of course, nothing involving Spotlight and unsigned bundles ever goes smoothly on macOS.
The trouble started right after installation. Double‑click, bounce in the Dock, and then poof—nothing. No crash report, no dialog box, just a ghost entry briefly showing up in Activity Monitor and dying instantly. Terminal launch gave me the dreaded message:
“Kenophobia.app” is damaged and can’t be opened. You should move it to the Trash.
Here we go again, I thought. Classic Gatekeeper behavior when an app isn't properly notarized or when the quarantine flag is mis‑set.
The First Wrong Turns
My first move was the oldest Mac trick in the book: unchecked “Open Anyway” in System Settings → Privacy & Security. Then tried xattr -cr /Applications/Kenophobia.app to clear extended attributes. No luck.
I even re‑downloaded it from what looked like the official listing on the Mac App Store just to make sure the bundle wasn’t corrupted. Same silent crash. I checked the Console logs—error EXC_BAD_ACCESS (SIGSEGV) right at launch. That pointed to either sandbox restrictions or some dependency failing early.
Then I stumbled on this page, which had a short note about the app misbehaving on the latest macOS builds due to how Gatekeeper applies quarantine flags on system‑extracted archives. Sounded about right.
What Actually Fixed It
Turns out the fix was almost embarrassingly simple once I understood what macOS was doing. When you download an app via Safari or Chrome, it attaches a quarantine attribute so the system can verify its notarization. Kenophobia wasn’t signed correctly, so it was blocked mid‑launch even after clearing attributes from the outer bundle.
The trick was to remove that flag recursively before moving it to /Applications:
cd ~/Downloads
xattr -r -d com.apple.quarantine Kenophobia.app
Once I did that, the app opened instantly—no warning, no crash. I also granted it extra permissions in System Settings → Privacy & Security → Files and Folders so it could index user data for its custom search menu. After that, it remembered everything smoothly.
Worth noting: if you’re ever unsure whether an app is safe after doing this, you can verify its digital signature manually with:
codesign --verify --deep --strict --verbose=2 /Applications/Kenophobia.app
If that command returns “valid on disk” and “satisfies its designated requirement,” you’re good. Apple explains the whole signature process nicely on developer.apple.com, and they even show what happens when a notarization ticket doesn’t match. It’s nerdy but worth a glance if you deal with lots of indie utilities.
The Aftermath and Minor Tweaks
Once I got Kenophobia running, I noticed it still refused to index files outside the user’s home directory. Spotlight integration tends to be picky these days, and Ventura’s tightened sandbox rules didn’t help. Granting Full Disk Access under Privacy & Security → Full Disk Access solved that instantly.
One optimization tip: when Kenophobia was trying to read the Spotlight database, CPU usage spiked to 98% on a single core. I fixed that by manually rebuilding the Spotlight index using:
sudo mdutil -E /
After that, the app ran cooler and didn’t stutter every few seconds when querying file paths.
For future installs or testing, I keep a short checklist handy:
-
Never run unsigned apps directly from Downloads. Move them, clear quarantine flags.
-
Always check
codesignoutput before bypassing security dialogs. -
Grant File and Folder access explicitly—Spotlight utilities need it.
-
Rebuild metadata indexes occasionally if file searches start lagging.
Apple’s own support article about opening apps from “unidentified developers” pretty much sums up the cautious route. I like to follow it loosely—verify first, then override if I know the source.