I was trying to get a small productivity thing running on my Mac, nothing fancy. Just wanted a lightweight way to shuttle snippets between apps while I was cleaning up notes for OrchardKit work. The slug in the link points pretty clearly to Shattle (app), which sounded like exactly that: simple, utility-grade, no drama. Famous last words.
What I wanted to do
Download the build, drop it into Applications, launch it, move on with my day. I was on macOS Sonoma 14.3, M1 MacBook Air. Clean system, no weird hacks, no beta OS. This should’ve been a two-minute task.
What actually broke
Double-click. Bounce once in the Dock. Then nothing. No crash dialog, no “app is damaged” warning, no Gatekeeper popup asking for permission. Just… silence. Activity Monitor showed it spawning and immediately exiting. That’s usually a smell: either a hard crash before UI init or macOS deciding quietly that it doesn’t trust what you just ran.
First attempts (mostly wrong turns)
My first instinct was the classic one: “maybe it’s quarantined.” I checked extended attributes in Terminal and, sure enough, there was a quarantine flag. I removed it manually. Relaunched. Same behavior. Dock bounce, gone.
Second attempt: permissions. I went through Privacy & Security in System Settings looking for anything blocked under “Security” or “App Management.” Nothing. macOS wasn’t even bothering to complain, which made this more annoying than a loud error.
Third attempt was reinstalling from scratch, different folder, even renaming the bundle just in case something dumb was happening with paths. Still dead on arrival. At this point it felt less like user error and more like Gatekeeper doing its newer, quieter thing.
What I realized
Starting with Ventura, macOS doesn’t always show a dialog when an app fails notarization checks. If the binary isn’t properly signed or notarized, launch can be blocked early, before any UI or alert. Apple explains this behavior in their own docs, but you only remember it after you’ve wasted 20 minutes:
https://support.apple.com/en-us/HT202491
and from the developer side:
https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution
So the app wasn’t “crashing.” It was being politely ignored by the OS.
What actually worked
The fix was boring but effective. I explicitly allowed it once macOS finally admitted it didn’t like the binary. I triggered that by trying to open it via right-click → Open. That forces Gatekeeper to surface its decision. After that attempt, a new message appeared in Privacy & Security saying the app was blocked and offering an Open Anyway button. Clicked that. Relaunched. It stayed open.
After that, it behaved exactly as expected. Lightweight, no background drama, just doing its thing. I saved this page because it helped confirm I wasn’t imagining the silent block behavior: https://philropost.com/office-and-productivity/38945-shattle.html
If you’re curious where Apple expects this to live in a more official sense, the safest distribution path is still the Mac App Store search:
https://apps.apple.com/us/search?term=Shattle
How I’d do it from the start next time
If I knew then what I know now, I’d skip half the guessing. My personal checklist now looks like this:
- First launch via right-click → Open, always.
- Immediately check Privacy & Security for blocked app notices.
- Assume notarization issues before assuming crashes.
- Only then touch Terminal or reinstall anything.
This wasn’t a broken tool, just one that macOS didn’t trust yet. Once you understand that Gatekeeper can fail silently, these cases stop feeling mysterious. They’re still annoying, but at least they’re predictable.
Top comments (0)