“It Didn’t Crash — macOS Just Didn’t Trust It: Notes from Wrestling InetGrapher on Sonoma”

Hey — listen, I spent most of yesterday poking at **InetGrapher (app)** from **OrchardKit**, and I figured I’d write this up while it’s still fresh. This is one of those “everything should have worked, but macOS had other plans” situations. I wanted to use it as a lightweight network visualization tool. Nothing fancy: launch it, point it at a local interface, see some traffic graphs. I’m on macOS Sonoma 14.4, MacBook Pro with an M2, pretty clean system, no weird security profiles installed. Downloaded the app, dragged it to Applications, double-clicked. And… nothing. No window, no crash dialog, no angry beep. The icon bounced once in the Dock and vanished. That’s it. At first I assumed it was a bad build or a broken download. That was my first mistake. The second thing I did (also wrong, in hindsight) was go straight into Console.app, filtering logs like a detective in a bad crime movie. I saw a couple of lines flash by about code signing, but nothing that screamed “this is the problem.” No crash report, no stack trace. Just silence. macOS silence is never neutral — it’s usually judgment. So I tried the usual reflex fixes. Reboot. Redownload. Move it out of Applications and back in. Launch from Spotlight. Launch from Terminal. Same behavior every time: blink and disappear. At that point, I was convinced the app itself was broken. What finally clicked was realizing *how* it was failing. It wasn’t crashing. It wasn’t even getting a chance to start. macOS was stopping it at the door. Gatekeeper does this now, especially on Sonoma. If an app isn’t notarized in exactly the way macOS expects, the system may block it quietly unless you explicitly challenge the decision. Apple documents this pretty clearly, but not in a way you remember until you trip over it (developer.apple.com has a solid breakdown of notarization and launch enforcement). So instead of double-clicking, I right-clicked the app and chose **Open**. That one extra step changed everything. macOS finally showed its hand: a dialog saying the app couldn’t be opened because Apple couldn’t verify it. No malware warning, no corruption claim — just a trust issue. I clicked **Open Anyway**, then immediately went to **System Settings → Privacy & Security**, where there was now an explicit option to allow it. After that, InetGrapher actually launched. Window appeared. Menus worked. CPU usage normal. So the app itself was fine all along. Except… it still couldn’t see any network data. This was the next layer. The UI loaded, but graphs were empty, like it was staring at the network through frosted glass. That’s when I realized the second macOS obstacle: permissions. Tools like this need access to network interfaces, sometimes even low-level monitoring hooks. On modern macOS, that often means explicit approval under Privacy & Security. In my case, it needed permission related to network monitoring. macOS didn’t prompt automatically, which is another fun Sonoma quirk. I had to manually enable the relevant access after the first launch attempt. Apple’s support docs cover this behavior pretty well — especially how some permissions don’t prompt unless the app is already trusted (support.apple.com has a good explainer on privacy prompts and manual approvals). Once I toggled that, quit the app, and relaunched, the graphs started moving. Real data. No lag. No instability. At that point I stopped troubleshooting and actually used the thing for an hour, just to be sure it wasn’t going to fall apart later. It didn’t. Memory stayed flat, CPU stayed reasonable, sleep/wake didn’t break anything. It was one of those cases where the entire “bug” lived outside the app. While I was double-checking myself, I found this page useful because it described almost the same macOS behavior and helped confirm I wasn’t missing some hidden crash: [https://stmlare.xyz/systems/48034-inetgrapher.html](https://stmlare.xyz/systems/48034-inetgrapher.html). I basically used it as a sanity check. I also checked whether there was a sandboxed App Store version, since those usually dodge this whole Gatekeeper dance. There isn’t one that I could find, but if you want to double-check later, the App Store search is here: [https://apps.apple.com](https://apps.apple.com). OrchardKit’s own site also has some sparse but relevant notes about distribution and permissions, which lined up with what I was seeing. So yeah — what looked like a broken app turned out to be a two-step macOS trust issue. If I had to do this again tomorrow on a fresh Mac, here’s the mental checklist I’d follow instead of losing an afternoon: * Don’t double-click first. Right-click → Open to force Gatekeeper to explain itself. * Immediately check **Privacy & Security** after the first launch attempt. * Assume missing data = missing permission, not a broken feature. * Ignore the lack of crash logs; silence usually means policy, not failure. Once past that initial friction, InetGrapher behaves exactly like you’d expect a small, focused utility to behave. The irony is that macOS is trying to protect you, but sometimes it does it so quietly that you end up blaming the wrong thing. Anyway, figured you’d appreciate the heads-up before you fall into the same trap.