Every major macOS release breaks a few apps. Golden Gate broke whole categories at once. Menu bar managers stopped hiding icons. Mouse utilities stopped switching Spaces. Audio tools, VPN clients, and Intel-only plug-ins went quiet.

Look closely and most of these failures share a single cause. The apps depended on something Apple never promised to keep, and in macOS 27 Apple changed it. Understanding that pattern is the most useful thing you can take into this upgrade and the next one.

Case 1: Menu bar managers

Bartender, Ice, Hidden Bar, Barbee, Thaw, and similar tools all stopped working on the first Golden Gate beta, on the same day.

What they relied on. Until macOS 27, the system drew every menu bar icon as its own small window. Menu bar managers found those windows, measured them, and moved them out of sight. That's how "hidden" sections, secondary bars, and collapse buttons worked.

What changed. Golden Gate renders the entire menu bar as a single window. There are no per-icon windows left to find. Because this was never a documented interface, there was nothing for Apple to deprecate or warn about. It simply stopped existing.

Where things stand. Bartender released a separate Golden Gate build that works, with some features still missing, including groups. Ice's bug report for macOS 27 has been open since June without a maintainer response, and active development has moved to a community fork, Thaw. BetterTouchTool shipped a partial workaround. All of the working approaches still rely on undocumented behavior.

What Apple added. Golden Gate includes a native overflow button that reveals icons that don't fit, which is most often a problem on MacBooks with a notch. It doesn't let you choose what's hidden, but it covers the most common reason people installed a menu bar manager.

Case 2: Mouse utilities and Mission Control

If a side button on your mouse used to switch Spaces or open Mission Control, it probably stopped after upgrading, while clicks and scrolling kept working.

What they relied on. Utilities like Mac Mouse Fix don't call Mission Control directly. They synthesize fake trackpad gestures, and to do that they wrote undocumented data fields into the system's input events.

What changed. macOS 27 no longer reads those fields. Every gesture-based action broke at once. The Mac Mouse Fix developers traced the problem and fixed it by generating gestures through a different, lower-level event type, but at the time of writing that fix hadn't reached an official release. The project published a temporary build for affected users.

Note that Golden Gate also has system-level Mission Control problems that affect people without any utilities installed. If Mission Control misbehaves with the built-in trackpad and keyboard shortcuts, that's macOS, not your mouse app.

Case 3: Kernel and system extensions

What they relied on. Some VPN clients, antivirus and endpoint security agents, USB and audio interface drivers, filesystem tools, and virtualization software load code into the system itself, and some of that code still depended on components that existed for Intel Macs.

What changed. Golden Gate removed support for extensions tied to those old Intel-era components. Unlike the first two cases, this was signaled for years: Apple has been pushing developers from kernel extensions to system extensions and user-space frameworks since 2019. Vendors who kept delaying the move are the ones scrambling now.

Users of at least one popular per-app audio routing utility have been warning others on forums not to upgrade until it's updated.

Case 4: Intel code inside other apps

What it relied on. Rosetta 2 being present.

What changed. Rosetta isn't installed by default on Golden Gate. macOS offers to install it when you open an Intel app. But plug-ins load inside a host app, so there may be no prompt at all. Audio producers reported Intel-only plug-ins simply disappearing from Logic Pro after upgrading, until they installed Rosetta manually. And in macOS 28, Apple has confirmed Intel apps won't open at all, apart from some older games.

The pattern

Three of these four cases break down the same way:

  1. A useful feature Apple didn't provide.
  2. A developer found an undocumented way to build it anyway.
  3. It worked for years, so everyone forgot it was fragile.
  4. Apple rebuilt the underlying system for its own reasons.
  5. The workaround vanished, with no warning, because there was never a contract.

Apple isn't targeting these apps. Golden Gate's menu bar and input changes almost certainly serve Apple's own goals, like the new overflow button and Siri AI's deeper system integration. Third-party tools were collateral damage.

Check your own Mac before upgrading

List what loads into the system:

kmutil showloaded 2>/dev/null | grep -v com.apple
systemextensionsctl list

Anything in either list needs a confirmed macOS 27 version from its vendor.

List apps with Accessibility access. Most utilities that change system behavior need it, so this is a good map of what could break:

System Settings > Privacy & Security > Accessibility

Go through each entry and ask: does this app hide icons, remap input, manage windows, or change how the interface behaves? If yes, check its release notes or issue tracker for Golden Gate support.

Install Rosetta if you use Intel plug-ins:

softwareupdate --install-rosetta --agree-to-license

Screenshot your menu bar and export utility settings. If you have to rebuild a layout or switch tools, you'll want a reference.

How to pick tools that survive the next release

You can't audit an app's source code, but a few signals predict a lot.

Does it replace a system feature or add to it? Apps that add something on top of documented frameworks, like a clipboard manager using the pasteboard or a menu bar app built with standard status items, rarely break across releases. Apps that rearrange or intercept what the system itself draws are structurally fragile, however well made.

How fast did the developer respond to the beta? Golden Gate's first beta came out in June. A developer who acknowledged the breakage within days and shipped a test build during the summer is showing you how they'll handle the next one. An issue tracker with a months-old bug report and no reply tells you the opposite.

Is it actively maintained? For open-source tools, check the date of the last commit and release. A popular free app with no activity for a year is one API change away from abandonment.

Is the business sustainable? Paid apps aren't automatically better, but a developer who earns a living from an app has a reason to fix it in week one. Free tools often depend on one person's spare time.

Does it use native frameworks? Apps built natively for macOS tend to track Apple's changes more closely than cross-platform tools, because their developers live inside Apple's documentation and beta cycle. That doesn't make them immune, as the menu bar managers show, but it helps.

What to do right now

  • Menu bar manager broken: try Golden Gate's overflow button first. If you need real hiding, use a manager that explicitly supports macOS 27, and keep an exported layout.
  • Mouse buttons no longer switch Spaces: check your utility's GitHub issues or website for a Golden Gate build. Keyboard shortcuts for Mission Control and Spaces still work as a fallback.
  • VPN, security agent, or driver: don't upgrade a work Mac until the vendor confirms support.
  • Intel plug-ins missing: install Rosetta, then start planning replacements before macOS 28.

The broader lesson is simple. Every tool that makes your Mac feel like yours sits somewhere between "built on what Apple supports" and "built on what Apple happens to do today." Knowing where each of yours sits is the difference between an upgrade that surprises you and one that doesn't.