Not sure where to report. I am sure you have someone looking at this, Beta 27.2 came out overnight and I now have it installed on one of my Mac’s. That one will no longer see any ROON server. (I have a Nucleus and Synology both running production).
Working fine with my other. Just wanted to let anyone know.
Roon doesn’t look at betas until late in the RC stage as nothing is guaranteed to stick with Apple, which is a waste of effort for devs.
Don’t use a beta unless you are comfortable that things may break.
I was just putting it out there for fyi. I use Beta on one of my systems for testing other software testing and figured I would let people know before they tried. Sorry I won’t mention items like this again then.
I’ve been in the software business for about 40 years now and I don’t think this is a fair statement. I use Apple betas to prep for upcoming releases and have never found it to be a burden to prepare and engage with Apple so that everything is good on both sides for a public OS release. Roon’s unwillingness to engage and ready for release using developer betas is puzzling.
At any rate, @Rollerbones , I am using 27.2 beta just fine - have you toggled Roon’s local network access on and off in Privacy settings yet?
Thanks, I just did that it they appeared again. 
I like simple fixes!
Just repeating what Roon has previously said on the matter.
We use betas to prepare but usually don’t create workarounds for things that are broken in the beta because it is not clear what they will or won’t fix. Who expected them to not fix Mission Control during 27 Beta and release, and instead ship with an entirely broken one? 
Yeah, part of what folks on our side do is: report what’s broken. It’s a two-way street. But not an excuse at all to step to the sidelines. When we all work together, things get fixed faster on both sides. Software Engineering is a team sport.
I don’t know about Roon, but we do report things and spend lots of dev and QA time to help Apple and Microsoft debug. Though there are not just our reports but others as well, and in either case it’s by far not always clear what will be fixed by x.0. We have spent too much time building workarounds for things that get fixed after all and been hit by others where it seemed obvious that they can’t release with this but they did. Resources are limited.
Understood.
Although this seems to be about MacOS rather than iOS, it does apply.
Arc on CarPlay with iOS 27 beta and now public release still doesn’t display the shuffle and repeat buttons at the correct size. Oddly, all other apps during all iOS 27 betas displayed correctly. 
I appreciate Roon’s response about not looking until at RC stasis, but knowing Roon’s release cycles as I feel I do, it’s likely any testing on iOS 27 RC is likely to hit until November/December time. As mop up from .net 10 and other issues surrounding Roon Bridge continues I do wonder if it’ll be longer.
Roon Remote on iOS 26 when scrolling had an awful stuttering affect that I know Roon Dev’s were looking into. But as iOS 27 betas were around, testing might have helped there as well before release so a flood of iOS 27 scrolling complaints didn’t hit the forums.
I guess it’s a fine balance of dev time on current OS’s and beta OS’s even if their releases are known and a few months away.
My personal opinion is that a software dev team should really be looking at a beta OS on devices their product will run a good 4 months before it is released. Just my view. This is why Apple offer public and developer beta release cycles after all.
If true, a big Oops
The claim is obviously incorrect because it works for others (enough reports on the forum where it was fine after the usual network permissions dance)
Never made sense anyway. As a general statement about software it is obvious nonsense, and what would a random Apple support person know about Roon specifically. Who knows what they said and what the poster understood.
Looking, sure. The problem is deciding which issues to spend how much time on.
This is not new (neither was it new in Tahoe) and there is no quick fix for it, apparently. (Issue is in the fundamental toolkit level)
Perhaps, but running extensions as a PWA with 120hz screen refresh rate scrolls buttery smooth. I mentioned this to Stephen a while ago.
Interesting opinion.
Wait…you were juust repeating something? It sounded like an opinion.
I’d guess that more than 50% of Roon users are Apple users on one or more platforms. Apple has a well established pattern of yearly releases with clear patterns for developer and user betas.
The industry at large accepts this. I run many apps and I watched the app developers fix their iOS 27, macOS 27, iPad OS 27 issues during the beta. Nobody expects developers to have zero issues but I think it’s reasonable to expect that major commercial software products take this cycle seriously and have their issues identified and addressed before the release.
I can’t imagine a process that’s much better than what Apple does. I’m not saying that they’re a fantastic, responsive partner to developers during beta cycles, but I am saying that doing it once a year, across all platforms at once, and making pre-releases widely available to both developers and users is a great approach. Most companies whose products I use are happy to take advantage of this by allowing their users to report the issues they run into. Roon, on the other hand, disclaims the process by saying it’s a waste of their time and they don’t even want to hear user reports. I don’t think that’s a good thing.
So they’re in reactive mode now. We’ve seen some wonderful, quality-focused changes from Roon this past year. I hope that by the time the version 28 beta cycles start, they’ve given this a bit of thought and approach it differently. Even just welcoming user reports of issues during the cycle would be a big step forward.
I was at an airport and my reply was rushed as air was boarding. Anyway, it was paraphrasing this.