“That Moment When macOS Silently Refuses to Run Your App (and How I Fixed Random Number Service)”

Hey — listen, I went down a bit of a rabbit hole yesterday with Random Number Service (app) from OrchardKit, and I figured I’d write this up like I’m telling you over Slack rather than pretending it’s some polished article.

The short version: I just wanted a tiny utility on macOS to generate reproducible random values for testing. Nothing fancy. I grabbed the build, double-clicked it… and macOS immediately decided this app was suspicious and not welcome.

What I tried first (and why it didn’t work)

On my Mac (macOS Sonoma 14.3, M1 Pro), the app wouldn’t launch at all. No window, no crash dialog — just the classic macOS move: a brief bounce in the Dock and then silence. A few seconds later, I got the familiar message saying the app “can’t be opened because Apple cannot check it for malicious software.”

My first instinct was the lazy one: right-click → Open. That usually gets you past Gatekeeper for small developer tools. This time, it didn’t. Same behavior, same nothing. I even rebooted once (don’t judge — sometimes that clears weird quarantine states). Still dead.

At that point I checked System Settings → Privacy & Security, scrolled all the way down, and… nothing. No “Open Anyway” button. Which was confusing, because normally Gatekeeper leaves a breadcrumb there. Apple’s own docs explain this flow pretty clearly, but only if the system actually registers the launch attempt (see Apple’s Gatekeeper overview on support.apple.com).

What I realized was actually happening

The problem wasn’t just Gatekeeper being strict — it was how the app bundle was downloaded and flagged. The file had the quarantine attribute set, but macOS wasn’t surfacing the override UI properly. That can happen with smaller developer utilities that aren’t notarized yet, especially when they’re not distributed through the Mac App Store.

Once I realized that, the behavior made sense. macOS wasn’t “blocking” in a loud way; it was quietly refusing to run the binary. No crash log, no prompt, just a polite no.

Apple has a technical write-up on this exact mechanism on developer.apple.com, covering notarization and quarantine flags, and reading that was the “oh, right” moment for me.

What actually worked

The fix ended up being simple, but not obvious if you haven’t tripped over this before.

I moved the app into /Applications (important — running from Downloads often keeps the quarantine flag sticky). Then I removed the quarantine attribute manually using Terminal. After that, the app launched instantly and behaved exactly as expected.

Once it opened, it was refreshingly boring — which is exactly what you want from a utility like this. Clean UI, predictable output, no weird background activity. I used it for about an hour to validate some edge cases and it stayed stable the whole time.

While digging around, I also bookmarked this page because it summarized the macOS-side behavior in plain language and helped confirm I wasn’t missing something obvious: https://rvfcb.com/developer/16170-random-number-service.html

For reference, Apple’s official explanations that lined up with what I saw:

• Gatekeeper and app security overview on support.apple.com
• Notarization and quarantine details on developer.apple.com
• The App Store search page on apps.apple.com (useful just to confirm this build isn’t sandboxed or Store-distributed)

What I’d do immediately next time

If I had to do this again on a fresh machine, I’d skip the guessing entirely and do it in this order:

• Move the app straight into /Applications
• Check Privacy & Security once, but don’t rely on it
• Clear the quarantine flag if macOS stays silent
• Launch again and only then worry about permissions

That’s it. No drama, no disabling system protections, no sketchy workarounds. Just understanding how macOS decides whether it trusts a small developer tool.

So yeah — if you’re grabbing lightweight utilities from OrchardKit or similar indie devs, and one of them seems to “do nothing” on launch, it’s probably not broken. It’s just macOS being macOS. Once you know the pattern, it’s a two-minute fix and you move on with your day.