“JLinkSys Logger on macOS: The Silent Launch That Turned Out to Be a Permissions Block”

Listen, I was messing around last night with JLinkSys Logger (app) from OrchardKit on my M2 MacBook Air (Sonoma 14.3), and I figured out why it kept refusing to start. It’s one of those cases where macOS looks innocent, the app looks innocent, and you end up staring at a Dock icon bouncing once like it’s mocking you.

The plan was simple. I needed a lightweight log collector to monitor some router traffic on my home lab setup. Nothing exotic — just launch the tool, point it to the device, capture logs overnight. I downloaded the latest build, dragged it into Applications, double-clicked it… and macOS hit me with the classic:

“JLinkSys Logger can’t be opened because Apple cannot check it for malicious software.”

Fine. That’s just Gatekeeper doing its job. Apple explains the behavior pretty clearly here:
https://support.apple.com/guide/security/gatekeeper-and-runtime-protection-sec5599b66df/web

So I did the usual: right-click → Open → confirm. It launched. I thought we were done.

Except we weren’t.

The window flashed for half a second, then the app just quit. No crash report dialog. No “damaged” message. Just gone.

My first reaction was honestly lazy troubleshooting. I assumed the build was unstable. I deleted it, re-downloaded, rebooted. Same behavior.

Then I thought maybe there’s a sandboxed Mac App Store version that behaves better. Checked here:
https://apps.apple.com/us/search?term=JLinkSys%20Logger

Nothing official. So this was clearly meant to run as a direct download.

At that point I stopped guessing and opened Console. Filtered by the app’s process name and tried launching again. That’s when I saw repeated lines about “deny file-read-data” and “deny file-write-data” in ~/Documents/Logs/.

No permission prompt had appeared. Sonoma sometimes doesn’t show one if the request fails early in startup.

That’s when it clicked: this wasn’t a Gatekeeper issue anymore. It was TCC — macOS privacy controls blocking file access. Apple’s documentation on app sandboxing and protected directories explains this behavior pretty well:
https://developer.apple.com/documentation/security/app_sandbox

The logger tries to create its own working directory inside Documents on first launch. macOS didn’t like that. Instead of prompting, it silently denied it. And because the tool depends on that folder existing, it just terminated.

So my initial assumption — “bad build” — was wrong.

What actually helped was boring but effective.

First, I removed the quarantine flag, just in case it was interfering with signature validation:

xattr -dr com.apple.quarantine /Applications/JLinkSys\ Logger.app

Then I launched it again. It still quit, but now I went straight to System Settings → Privacy & Security → Files and Folders. The app was listed there, but Documents access was disabled.

Enabled it.

Launched again.

This time it stayed open. Created its folder. Started capturing traffic logs. No drama.

For sanity, I also verified the code signature:

codesign --verify --deep --strict /Applications/JLinkSys\ Logger.app

No errors. So the binary itself was fine the whole time.

I found this page useful while double-checking I had the correct macOS-compatible release of the tool:
https://rvfcb.com/systems/11730-jlinksys-logger.html

Once permissions were aligned, the app behaved perfectly. CPU usage hovered around 3–5% while idle, spiked to maybe 12% during heavy logging bursts. Memory stable under 200 MB. Exactly what you’d expect from a small network utility.

What’s funny is that if macOS had just shown the permission prompt properly, this would’ve taken two minutes. Instead I wasted half an hour reinstalling and blaming the developer.

So here’s what I’d do immediately next time when an OrchardKit app “launches and disappears”:

• Check Console for TCC or file access denials before reinstalling.
• Remove quarantine flags after downloading a direct build.
• Manually review Files & Folders permissions in Privacy settings.
• Only assume corruption after those are ruled out.

The takeaway is simple. On modern macOS, silent exits are usually the system protecting something — not necessarily the app failing internally. Especially with tools that need file system access.

Anyway, if you run into the same thing with JLinkSys Logger or similar utilities, don’t overthink it like I did. It’s almost always permissions hiding behind a polite Dock bounce.

Now it’s running overnight without issues, quietly collecting logs like it was supposed to from the start.