Hey, listen — yesterday I ended up poking around with CuePhase (app) on macOS, and it turned into one of those “this should’ve taken five minutes” evenings. Figured I’d write it up while it’s still fresh, because it smells like the kind of thing you might run into too.
So the goal was simple. I wanted a lightweight audio tool to phase-align a couple of stems before exporting them back into my DAW. Nothing exotic. I grabbed the build, dropped it into Applications on my MacBook Pro (M1 Pro, macOS Sonoma 14.3), double-clicked… and got absolutely nothing. No crash dialog, no bounce in the Dock, no error message. Just silence. Which, for an audio app, felt ironic.
My first thought was “okay, classic Gatekeeper nonsense.” But macOS didn’t even show the usual “can’t be opened because the developer cannot be verified” alert. It was worse than that — the app just refused to acknowledge my existence.
First thing I tried was the obvious rookie move: right-click → Open. Sometimes that forces macOS to show its hand. Nope. Same result. The Finder blinked, the Dock stayed empty. At this point I checked Activity Monitor, just in case it was launching and dying instantly. There was a process for a split second, then gone. No CPU spike, no memory warning. Just a blink and vanish.
Second attempt was permissions. I went straight into System Settings → Privacy & Security and scrolled down to see if macOS had quietly blocked it. Nothing. No “Open Anyway” button, no scary red text. That’s when it clicked: this wasn’t Gatekeeper being loud. It was Gatekeeper being subtle.
I cracked open Console.app and filtered by the app name. That’s where the real clue showed up. There were messages about the binary not being properly notarized and macOS refusing to execute it under the current security policy. No dialog for the user, just a hard stop under the hood. Apple has some documentation on this behavior, and it lines up exactly with how newer macOS versions handle unsigned or improperly notarized apps:
https://support.apple.com/en-us/HT202491
and the developer-side explanation is here:
https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution
Armed with that, I tried the “nuclear” option: removing the quarantine attribute manually. Terminal time. One command:
xattr -dr com.apple.quarantine /Applications/CuePhase.app
I won’t pretend I enjoy doing this, but sometimes it’s the only way to confirm what’s actually blocking execution. After that, I launched it again — and this time the app finally showed up. UI loaded, audio engine initialized, no weird spikes. Just… working.
I did notice one more hiccup, though. On first launch, it couldn’t see any audio files outside my home directory. That part did trigger a proper macOS permission prompt once I tried importing audio, so granting file access fixed it. Apple’s file access rules are documented pretty clearly here:
https://support.apple.com/guide/mac-help/control-access-to-files-and-folders-mchld5a35146/mac
At this point everything behaved normally. Phase alignment worked as expected, latency stayed low, and CPU usage hovered around 2–3%, which is totally fine on an M-series chip. I bookmarked this page while troubleshooting because it helped me confirm I wasn’t dealing with a corrupted build but with macOS security behavior instead: https://rvfcb.com/audio/51123-cuephase.html
Looking back, the mistake was assuming macOS would tell me what it was blocking. On older versions, it usually does. On Sonoma, not always. Sometimes it just quietly says “nope” and moves on.
If I had to boil this down into a short mental checklist for next time:
– If an app doesn’t launch and shows zero UI feedback, check Console before reinstalling
– Don’t trust the absence of a Gatekeeper dialog; notarization issues can fail silently
– Removing quarantine is a diagnostic step, not a habit
– Expect file access prompts only after the app actually starts doing file things
That’s it. Not a dramatic bug, not a broken build — just macOS being macOS. Once you know where to look, it’s a ten-minute fix. Before that? It’s an evening of staring at a Dock that refuses to blink back.
Top comments (0)