“Goodwill Calculator on macOS: The Silent Crash That Wasn’t Gatekeeper”

Hey,

So yesterday I went down a small rabbit hole with Goodwill Calculator (app) from OrchardKit on my MacBook Air M2 (macOS Sonoma 14.3), and I figured I’d write this up before the details blur together.

All I wanted to do was run a quick valuation scenario for a side project. Nothing heavy — just plug in assets, liabilities, projected earnings, export a report, done. I grabbed the build and installed it into Applications like usual. Double-clicked.

And macOS hit me with:
“Goodwill Calculator can’t be opened because Apple cannot check it for malicious software.”

Classic Gatekeeper moment.

Apple explains the logic behind that warning here:
https://support.apple.com/en-us/HT202491

So I did the standard move: right-click → Open → confirm dialog. It launched for half a second, then closed. No error. Just a polite crash.

At first I assumed the download was corrupted. I re-downloaded the installer. Same behavior. Then I checked whether it might be notarization-related or an outdated signature. The bundle looked properly signed, at least superficially.

Next step: I opened Console and filtered logs by the app’s bundle identifier. That’s where it got interesting. I kept seeing sandbox denial messages tied to access in ~/Documents and ~/Library/Application Support. No explicit crash trace — just permission blocks.

So it wasn’t exactly Gatekeeper blocking execution. It was the app failing during initialization because it couldn’t read or write to protected folders.

Apple’s breakdown of privacy permissions and protected directories is here:
https://support.apple.com/en-us/HT209175

And that lined up perfectly with what I was seeing.

The weird part? macOS never showed the usual “Allow access to Documents?” dialog. It just let the tool fail silently.

My first mistake was assuming this was purely a code-signing issue. I even removed the quarantine flag just in case:

xattr -dr com.apple.quarantine /Applications/Goodwill\ Calculator.app

Still crashed.

What finally worked was resetting the TCC (Transparency, Consent, and Control) permissions database for the bundle:

tccutil reset All com.orchardkit.goodwillcalculator

After that, I relaunched it — and finally got the proper system prompt asking for access to Documents. I approved it.

Boom. The interface loaded completely. Input fields populated. No crash.

While I was troubleshooting, I found this page useful as a reference for the macOS-compatible build I was testing:
https://technotafastore.xyz/finance/57427-goodwill-calculator.html

It helped confirm I wasn’t accidentally running some outdated release.

Once it was actually running, performance was totally fine. CPU usage hovered around 5–8% during recalculations. RAM stayed under 250 MB. Exporting a PDF report was instant. So the tool itself wasn’t broken — macOS just wouldn’t let it touch protected directories until explicitly approved.

What I misunderstood at first was thinking Gatekeeper and privacy permissions are the same thing. They aren’t. Gatekeeper controls whether an app is allowed to launch at all. Privacy controls determine what it can access once it’s running. In this case, the app technically launched — it just failed during startup because it couldn’t access its working folders.

If I had to do it again, here’s the short version I’d follow:

• Install normally into Applications.
• Launch once.
• If it crashes immediately, open Console and check for “deny” or “sandbox” entries.
• Reset TCC for the bundle.
• Relaunch and approve folder access prompts.

That’s it. No need to disable Gatekeeper system-wide, no need to mess with SIP, no need for weird workarounds.

If someone prefers App Store builds when available, you can search here:
https://apps.apple.com/us/search?term=Goodwill%20Calculator

In this case I was testing the direct distribution build, which is why the permission flow was slightly messier.

After permissions were clean, everything behaved exactly as expected. I ran multiple valuation scenarios, exported reports, reopened saved sessions — no instability. The crash never came back.

Honestly, this is one of those modern macOS quirks that can waste an hour if you assume the worst. A silent startup failure often isn’t a broken binary. It’s the OS enforcing privacy rules a little too quietly.

Anyway, that was my little adventure. Now the calculator works perfectly, and I have a reminder — again — that when something quits instantly on macOS, check Console before blaming the developer.