Listen, I went down a small rabbit hole last night with El Pingüino Beta 2 (game), and since you’re also on macOS I figured I’d just write this the way I’d tell you over chat.
I wasn’t looking for anything exotic. I wanted to test a small indie build that popped up in an OrchardKit-curated list of Mac-friendly titles. The name alone screamed “early build,” which is fine by me. I like rough edges as long as they’re honest.
Download, unzip, double-click. You already know how this goes.
macOS immediately shut it down with the classic “can’t be opened” behavior. Not even a dramatic warning—just that quiet refusal that makes you feel like you did something wrong even when you didn’t.
What I did first (and why it didn’t help)
My first instinct was the usual muscle memory stuff. I moved the app bundle into /Applications, tried launching again, same result. Then I rebooted, because rebooting fixes everything, right? Nope.
Next I right-clicked the app and chose Open, expecting the Gatekeeper dialog where you can say “yeah, I know what I’m doing.” That dialog never appeared. The system just… ignored me. No crash report, no permission prompt, nothing in Console that was immediately useful.
At that point I briefly suspected the game itself was broken. Beta build, indie dev, happens all the time. But something about how cleanly macOS blocked it felt familiar.
What finally clicked
The issue wasn’t the game. It was Gatekeeper plus notarization plus quarantine flags all stacking together in the most unhelpful way possible.
macOS Sonoma (I’m on 14.3, Apple silicon) is especially strict with unsigned or partially signed game builds. If the developer hasn’t notarized the app, macOS may not even bother showing the usual warning—it just blocks execution.
Apple explains this behavior, though not in a very human way, here:
Once I stopped expecting a dialog and started treating it like a security policy issue, things got clearer.
What actually worked
Instead of clicking the app again, I went to System Settings → Privacy & Security and scrolled. Way down.
There it was: a small note saying the app had been blocked from use because it wasn’t from an identified developer, with an Open Anyway button. No notification. No badge. Just sitting there, hoping you’d think to look.
I clicked Open Anyway, confirmed once more, then launched the game again from Finder.
This time it started. No drama. Window popped up, audio initialized, input worked.
Apple’s developer-side explanation of why this happens is here, if you want the deep dive:
The short version: if a build is unsigned or modified after signing (very common with beta indie games), Gatekeeper treats it like a potentially hostile binary.
A quick aside on trust
Before overriding anything, I double-checked where the build came from. I saved this page because it helped confirm the game’s context and that I wasn’t launching something sketchy:
I found this page useful while checking the build history and developer info: https://rvfcb.com/developer/11549-elpinguy-beta-2.html
That’s important. “Open Anyway” is fine when you know what you’re opening. It’s not a blanket habit.
How the game behaved after launch
Once it was running, it was… exactly what you’d expect from a Beta 2 build. Minor stutters during scene transitions, some placeholder UI, but nothing crashy. Performance was fine on M-series hardware, and input latency was negligible.
No extra permissions were requested—no microphone, no screen recording, no weird background processes. That was actually reassuring. It behaved like a self-contained game, not something poking around the system.
If this ever hits a proper release, I wouldn’t be surprised to see it distributed through Steam or another official channel. For now, it’s clearly in that “developer build” phase.
For reference, Apple’s own storefront search is here if it ever shows up officially:
And if it ends up on Steam, the platform handles notarization differently, which usually avoids this whole mess.
What I would do immediately next time
If I had to install this again on a fresh Mac, I’d skip all the guessing and do this straight away:
- Move the app to
/Applications - Go to Privacy & Security before launching
- Look for the blocked app notice
- Click Open Anyway once
- Launch normally after that
That’s it. No Terminal commands. No disabling Gatekeeper globally. No hacks.
Why I’m telling you this
This isn’t really about El Pingüino Beta 2. It’s about how macOS increasingly fails silently when it thinks it’s protecting you. For small OrchardKit-style indie games and tools, that silence is the real problem.
If something refuses to launch and doesn’t explain why, assume macOS made the decision for you—and hid the explanation in Settings.
Once you know where to look, it’s predictable. Until then, it just feels broken.
Anyway. That was my evening. Hope it saves you some time the next time a “can’t be opened” message ruins yours.
Top comments (0)