MacOS Golden Gate 27.0.1

[Shlomo_Drechsler]

Hi, after updating to 27.0.1 today, the bypass from last week stopped working.

This is extremely frustrating. Over the past week, I have spent hours trying to resolve the issue.

There must be a way to fix that issue.

[achilleas_konstantin (achilleas konstantinidis)]

today i updated to 27.0.1 and i can see again my devices on roon macbook

[Jake_Watson]

I run Roon Server on ROCK, not MacOS, and my BOwers & Wilkens Formation products have all disappeared (but show up as they are in the B&W app). B&W had a software update, also, so I was/am confused, but the rest of our devices are all Mac, so I’m guessing this issue is also affecting clients?

[Suedkiez (Just a fellow user like you)]

@Jake_Watson

B&W had a software update

And that’s where this different issue is. Roon is aware and working with B&W:

B&W Products not detected in Roon App B&W firmware update (ref#I8KQW3) [Investigating]

Hi everyone, Roon is in contact with B&W and we will share updates here promptly as more information becomes available. Thank you for the thorough reports and for your patience.

[Suedkiez (Just a fellow user like you)]

@Shlomo_Drechsler

Hi, after update 27.1 today, the bypass from last week stopped working. This is extremely frustrating. Over the past week, I have spent hours trying to resolve the issue. There must be a way to fix that issue .

Every macOS update since Sequoia required the workaround of toggling the local network permissions for Roon off and back on. Did you do that?

[Stephen (Stephen Shaw)]

It’d be very interesting if the 27.0.1 update fixed the issue I worked around… My improvement better isolates us from breakages like this.

[Suedkiez (Just a fellow user like you)]

I edited the title of this topic from 27.1 to 27.0.1 for clarity as 27.1 doesn’t exist, so surely the OP doesn’t have it.

[Jake_Watson]

There is another issue here that doesn’t have anything to do with B&W, IMHO – Namely, using a Roon client on Golden Gate doesn’t work consistently. I can get it to work on from one machine, but only after a fresh restart. My other machine – same network – can’t connect. Using the iOS client works just fine (but my B&W speakers/zones don’t appear, which is what we have been talking about here).

---

Environment:

• Roon Server (ROCK) on dedicated NUC, RoonOS 2.1 (build 271), wired Ethernet, static IP 192.168.1.221

• Roon Remote on two Macs, both freshly upgraded to macOS 27 Golden Gate (now on 27.0.1)

• Network: UniFi Dream Machine SE gateway, multiple managed switches, flat network (no VLANs)

• Symptom: Remote shows ROCK correctly (right name, IP, version) but hangs at “Initializing…” / “Connecting…” and never completes. Works briefly immediately after a full system restart, then degrades.

Steps taken, in order:

1. Flushed local DNS/mDNS cache (dscacheutil -flushcache; killall -HUP mDNSResponder) — temporarily restored connection, confirming it wasn’t a DNS/discovery resolution issue, but didn’t hold.

2. Verified UniFi network settings were not the cause:

   • IGMP Snooping: confirmed off

   • Gateway mDNS Proxy: confirmed set to Auto

   • Ruled out VLAN segmentation (none configured — flat network)

3. Applied the documented Terminal workaround for Golden Gate’s Local Network Privacy enforcement:

   sudo defaults write com.apple.network.local-network AllowedEthernetLocalNetworkAddresses -array "192.168.1.0/24" "224.0.0.0/4"
   
   

   Full restart after each change. Tried both subnet-wide and host-specific (192.168.1.221/32) scoping. Verified the setting persisted correctly via sudo defaults read com.apple.network.local-network. No improvement — same stall behavior.

4. Checked System Settings → Privacy & Security → Local Network: only Roon.app is listed. RoonAppliance.app and RAATServer never appear in this list at all, despite the main app being present and allowed.

5. Checked Firewall settings: Roon.app, RoonAppliance.app, and RAATServer are all correctly present and set to “Allow incoming connections” — ruled out the firewall as the blocker.

6. Performed a full clean uninstall and reinstall of Roon Remote, including removing /Applications/Roon.app, ~/Library/Application Support/Roon, ~/Library/Caches/com.roon.*, ~/Library/Logs/Roon, preference plists, and any LaunchAgents — to force a fresh permission registration attempt. No Local Network permission prompt appeared for RoonAppliance/RAATServer on first launch after reinstall — same stall behavior persisted.

7. Updated to macOS 27.0.1 — issue persists unchanged.

Conclusion: This appears to match the broader Golden Gate bug reported by other third-party developers (Moonlight-Qt, LightBurn, Codex Desktop, Ghostty, TrguiNG) where certain helper/child processes never trigger macOS’s Local Network permission prompt at all, regardless of the parent app’s permission state, Terminal-level network exemptions, or a clean reinstall. RoonAppliance and RAATServer specifically never register in Local Network privacy on this setup, which appears to be the root blocker.

Current workaround: Using Roon’s iOS app as the primary remote, which connects reliably.

[Suedkiez (Just a fellow user like you)]

@Jake_Watson

There is another issue here that doesn’t have anything to do with B&W, IMHO – Namely, using a Roon client on Golden Gate doesn’t work consistently. I can get it to work on from one machine, but only after a fresh restart. My other machine – same network – can’t connect.

Open a new support request if you haven’t. Posting here in the user discussions in Roon Software Discussion won’t do anything. (Copy your detailed analysis from here to the new support case)

How to get help with Roon

Do you need help with one of our products? Well, you’re in the right place! Just click on the “Get Help” button at the top of the Support category, or click the image below… [IMG_9100] From there you simply need to answer a few questions and will then be able to enter a description of your issue. If required, a community post will be created on your behalf and a member of our team will be with you shortly in order to provide assistance. In the mean time a member of our user community may be…

You could also try clicking the Select a different Roon server button, if you have it, in the remote that can’t connect. If this helps, then this happens sometimes and is not new to 27.x.

[Jer]

Just to say I updated to MacOS27.0.1 and Roon 2.73.1 today and everything seems fine. I run Roon on a Macmini but it can ‘see’ my other Macs and my Sonos Roam as endpoints, and my iPad andiPhone work fine as control points.

[MarcMarc (Marc)]

I just updated to 27.2 (beta) and Roon (2.73) (2.73.1 EA Hotfix build 1697).

No workarounds required at all. It simply just works.

[Suedkiez (Just a fellow user like you)]

2.73 or 2.73.1 (with the hotfix)?

[MarcMarc (Marc)]

I dunno. I just updated everything a few hours ago

[Carl]

Build 1697 EA is 2.73.1 … see …

Early Access: Roon 2.73.1 build #1697 Hotfix is Live!

Hey Everyone, This release addresses the most urgent issues introduced by Apple’s OS 27 updates: Missing audio devices on macOS 27 Silent playback on HomePods running software version 27. It also includes a fix for a cross-platform regression from our previous release, which is why this build is being shipped across all platforms. The tvOS 27 issue affecting playback on Apple TV is not fixed in this release and remains a top priority. Thank you for your feedback and continued support! The…

---

I’ve updated your post.

[Matthew_Bowden1 (Matthew Bowden)]

So have all the issues been fixed with latest update? Safe to update my MacBook and iPhone?

[Suedkiez (Just a fellow user like you)]

The traditional necessity of having to toggle the network permissions haven’t been fixed, but they seem no worse than before.

Other than that, macOS and iOS have enough issues of their own, independently of Roon. Mission Control on macOS is more or less completely broken. WiFi reception on iOS is worse at least for some people. As always, the safe approach is waiting for 27.2 in November/December or googling for “macOS 27 issues” etc and deciding for yourself.

[Baker]

I have an M4 Mini, M1Pro Macbook and iPhone 17 all updated with none of those problems so it is not like that for every user. Roon and ARC are both running great for me at the moment.

[Suedkiez (Just a fellow user like you)]

@Baker

I have an M4 Mini, M1Pro Macbook and iPhone 17 all updated with none of those problems so it is not like that for every user.

Well the broken Mission Control at least is on all Mac sites and was already widely reported during Beta. The WiFi problem seems less frequent but it exists (I have it).

But that’s why I said nothing beats looking for oneself and making one’s own judgement. (The question was if all issues are fixed and they aren’t).

As for the Roon issues, yes they are largely fixed but not the old one with the permissions, at least occasionally, and there are enough reports on the forum. Anyway, this probably never affected everyone on every update, but often enough.

[Stephen (Stephen Shaw)]

There is another 2.73(.2) release coming out today or tomorrow that’ll fix the tvOS issues and a couple other issues around airplay. Hopefully we are getting closer to Roon running smoothly regardless of what Apple does

[MarcMarc (Marc)]

Apple „Challenge accepted".