QuickFormat!

When QuickFormat! Refused to Behave on macOS

A couple of days ago, I decided to test QuickFormat! (QuickFormat! - Spot Light Hub) — a minimalistic file management utility that claims to batch‑rename and clean metadata of old project files. Perfect, I thought, for taming my cluttered “_output” folder. It took me about five minutes to find myself deep in macOS’s labyrinth of permission errors and Gatekeeper pop‑ups.

The First Launch Disaster

I downloaded the build, dragged it to /Applications, and double‑clicked. Nothing. The icon jumped in the Dock once, then vanished. Trying again produced a comforting but useless message:

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

Right: “damaged.” Of course. On my MacBook Air M1 running macOS Sonoma 14.4, that usually means Gatekeeper doesn’t recognize the app’s developer signature. I followed the ritual — System Settings → Privacy & Security → Allow Anyway, only to get hit with the same error.

So I did what any self‑respecting Mac nerd does: fired up Terminal for xattr therapy. First try:

Still dead on arrival. I even moved it back to the Downloads folder thinking maybe /Applications’s SIP (System Integrity Protection) was blocking it. No luck.

That’s when I remembered reading about macOS’s quarantine attribute — that invisible “tag” that follows apps downloaded from the web, telling Gatekeeper to treat them like radioactive waste until Apple verifies their notarization.

The Fix Appears (After Several Wrong Turns)

Before reaching for drastic measures, I checked the Console for crash traces. Sure enough, I found:

So it wasn’t damaged at all. Gatekeeper was blocking certificate checks internally. I ran the quarantine removal again — but this time from the right directory before moving it:

Then I dragged it back to /Applications, right‑clicked, chose Open, and suddenly — there it was. The icon bounced twice, a prompt appeared, and QuickFormat! actually opened.

I also granted it Full Disk Access in System Settings → Privacy & Security after it complained about missing permissions for the Desktop folder. That fixed the weird freeze when it tried to list files outside the user home directory.

Apple has pretty clean documentation about this topic, like this guide explaining unidentified developer apps, or the more technical developer note on notarization if you enjoy reading about signature tickets and entitlements.

Somewhere in the process I stumbled across this page, which summed up similar Gatekeeper headaches other macOS users had with minimalist utilities like this. It pointed me toward the xattr route first, so credit where it’s due.

Aftermath and Lessons Learned

Once the app was properly launched, it worked fine. QuickFormat! did what it promised — cleaned file metadata, normalized names, stripped weird UTF characters. CPU usage hovered around 2%, and Spotlight indexing didn’t even blink. So the drama had nothing to do with its performance, just the packaging.

For any future me (or anyone else) dealing with small unsigned tools, my mental checklist looks something like this:

• Always remove the quarantine flag before moving the app into /Applications.

• Verify signatures manually with codesign --verify --deep --strict /path/to/app.

• Re‑grant Full Disk Access if the app touches documents or external drives.

• Keep a placeholder copy for rollback — Gatekeeper sometimes re‑flags files after updates.

After all this fiddling, QuickFormat! has earned a cautious place in my utilities folder. It now launches instantly, behaves politely, and hasn’t tripped securityd since.

It’s a funny pattern on macOS lately: tiny indie apps that do one thing right, but stumble because of Apple’s own well‑meaning paranoia. Still, once you understand where Gatekeeper draws the line, it’s almost a rite of passage — like the first time brew doctor scolded you for everything and yet somehow fixed nothing.

In the end, QuickFormat! wasn’t damaged. It was just misunderstood — by the most overprotective operating system on the planet.