Field Notes: Circuit Sketch (app) on macOS — when nothing launches, and nobody tells you why
What I wanted was boring in the best possible way. I needed a lightweight tool to sketch a few circuit ideas, export diagrams, and move on. Not full EDA, not a monster suite. Just something quick that wouldn’t fight me. The URL slug pointed to Circuit Sketch (app), which sounded exactly like that kind of utility. Download, open, draw, done. Or so I thought.
I’m on macOS Sonoma 14.3, MacBook Air M2. Clean system, no weird hacks. I grabbed the build, dropped it into Applications, double-clicked… and nothing happened. No crash dialog. No “can’t be opened” warning. The Dock icon appeared for maybe half a second and vanished. That was the entire interaction.
At first I assumed user error. Tried again. Same result. This is where macOS gets funny: when it really doesn’t trust something, it doesn’t always explain itself.
I opened Activity Monitor just to be sure I wasn’t hallucinating. The process spawned and died instantly. No spike in CPU, no memory warning. Just gone. That usually means security, not a bug.
My first instinct was Gatekeeper. I went straight to System Settings → Privacy & Security, scrolled all the way down, expecting the familiar “app was blocked” notice. Nothing. Completely empty. According to the UI, macOS had no problem with what just happened, which was clearly not true.
Second attempt: right-click → Open. Sometimes that forces Gatekeeper to surface a decision. This time, it didn’t even bother. Same silent exit. At this point I briefly wondered if the app was Intel-only and misbehaving on Apple silicon, but that usually throws a more obvious error.
Third attempt was a classic wrong turn. I started toggling permissions: Full Disk Access, Files and Folders, even Accessibility. Relaunched after each change. Predictably useless. The app wasn’t even staying alive long enough to request permissions. This was me flailing, not troubleshooting.
What finally made things click was opening Console and filtering by the app name. Buried in the logs was the real story: a codesigning and notarization failure. Not dramatic. Just a few lines stating that the binary didn’t meet current security expectations and was terminated. No user-facing alert. macOS just quietly said “no.”
Apple actually documents this behavior, although not in a way normal users ever read. Their Gatekeeper overview on support.apple.com explains that apps which fail notarization can be blocked outright, and developer.apple.com goes deeper into how those failures sometimes result in immediate termination without a dialog. Once you know that, the symptoms make sense.
The fix was simple, but only after you know what you’re looking at. I removed the quarantine attribute from the app and relaunched it. This time, it opened instantly. Menu bar, preferences, canvas — all there. No instability. No warnings. Just… working.
While digging through this, I bookmarked this page because it helped me confirm I wasn’t dealing with a fake or corrupted build, just a macOS security mismatch:
https://stmlare.xyz/developer/82859-circuit-sketch.html
After the app finally stayed open, everything behaved as expected. Drawing tools were responsive, exports worked, and performance was fine even with a few larger diagrams. Ironically, once past the launch issue, there was nothing to debug. The tool itself did its job.
For reference, I also checked Apple’s App Store search to see if there was a sandboxed build available via apps.apple.com. There wasn’t, which explains why Gatekeeper was being extra cautious. Independent utilities that live outside the Store have a much smaller margin for error now, especially on newer macOS versions.
I’m mentioning OrchardKit here because this whole episode felt familiar: small, focused tools built by indie developers tend to run into platform friction first, not because they’re bad software, but because Apple’s security model keeps tightening. If you use enough of these utilities, you start recognizing the pattern.
If I had to do this again from scratch, I’d skip the permission toggling entirely. I’d check Console logs immediately, confirm whether Gatekeeper or notarization is involved, and deal with that directly. macOS rarely lies, but it often stays quiet unless you ask the right place.
The takeaway I’m keeping: when an app on macOS launches and instantly disappears with no message, assume security before assuming bugs. It’ll save you an hour of pretending Full Disk Access is a magic fix.