I’m logging this as a straight troubleshooting note, because this is exactly how it felt while it was happening. I wanted to get a small finance utility running on my Mac, and instead I ended up learning (again) how unforgiving macOS can be when an app crosses one invisible security line.
Based on the URL slug, the tool is MoneyManager (app). That makes sense: lightweight personal finance software, nothing exotic. I’ve been testing a few OrchardKit-adjacent utilities lately, so this one went into the same mental bucket. Download, install, open, done. Or so I thought.
What I wanted to do was pretty mundane. I just needed a local money tracker to open a couple of CSVs and sanity-check some expenses. No cloud sync, no bank APIs. Just launch the app and see if it’s usable.
What broke was the launch itself. Double-click, nothing. No error dialog, no “can’t be opened because Apple cannot check it,” no crash report. The icon flashed in the Dock for less than a second and vanished. That’s it. Silence. Those are the worst ones, because there’s nothing obvious to react to.
First attempt was the usual ritual: delete the app, re-download, move it back into Applications. Same behavior. Second attempt: right-click → Open, expecting Gatekeeper to finally show a warning. Still nothing. At that point I checked Privacy & Security in System Settings, scrolling all the way down to see if macOS had parked an “Open Anyway” button there. It hadn’t. Dead end.
The third attempt was more speculative. I opened Console and watched system logs while launching the tool. That at least confirmed it wasn’t crashing in user space. The process was being killed before it fully initialized. That’s when it clicked: this wasn’t a runtime bug, this was a trust decision.
Apple’s own documentation explains this behavior, but it’s buried between the lines. If an app fails certain notarization or code-signing checks, macOS doesn’t always prompt. Sometimes it just refuses to execute. This page is the official baseline for how Gatekeeper is supposed to behave:
https://support.apple.com/en-us/HT202491
I also skimmed Apple’s developer notes on notarization to remind myself why this happens more often on newer macOS releases, especially on Apple silicon:
https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution
Armed with that, I stopped treating it like a broken app and started treating it like a quarantined one. I checked the extended attributes on the bundle and, sure enough, it was still flagged as downloaded content. Clearing that forced macOS to re-evaluate it. On the very next launch, the system finally showed a security prompt asking for confirmation. I approved it, and the app opened instantly. No drama after that.
Once it was running, it behaved fine. Files opened, UI responded normally, no weird permission requests. That was the confirmation that the binary itself was okay. The problem was never functionality; it was macOS refusing to trust it without being explicitly told to.
I briefly checked the App Store to see if there was an official distribution there, because apps delivered through Apple’s store don’t trigger this class of issue as often:
https://apps.apple.com/us/search
There wasn’t an obvious match, so the direct download route is probably the intended one.
Somewhere near the end of this process, I bookmarked this page because it lined up closely with what I was seeing and helped me sanity-check the macOS side of the problem rather than blaming the tool:
https://proguntalk.com/finance/83653-moneymanager.html
What actually solved the issue wasn’t reinstalling, rebooting, or toggling random privacy settings. It was understanding that silent launch failure on modern macOS is often Gatekeeper doing its job quietly. Once the system was forced to ask the question it had been skipping, everything worked.
If I were doing this again from scratch, I’d skip half the guesswork. When an app won’t open and doesn’t complain, assume it’s a security classification issue first, not a crash. Especially on Sonoma, especially on M-series Macs. That assumption alone would have saved me a good chunk of time.
That’s the full report. One small finance app, one invisible macOS wall, and a reminder that silence is still a signal if you know how to read it.