Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MacRumors

macrumors bot
Original poster
Apr 12, 2001
67,646
38,074


Apple today released the fourth beta of macOS Ventura 13.4 to developers, and it appears that there are some issues with content filtering apps like Little Snitch, Radio Silence, and others.

macos-ventura-roundup-header.jpg

After installing the beta, some users on the MacRumors forums and on Twitter had problems with network connectivity, and managed to narrow it down to interference with firewall apps. MacRumors reader Grant, for example, saw his network cycling on and off repeatedly until he uninstalled Little Snitch.

Twitter user @Aaronp613 had an issue with his Mac disconnecting after updating and he was able to fix it by turning off Radio Silence.


Mac users who are having problems with network connectivity after installing macOS Ventura 13.4 beta 4 should disable their network filtering apps. Those who are concerned about not being able to use the apps for the time being should avoid installing the latest beta for now.

Article Link: PSA: Latest macOS Ventura 13.4 Beta Doesn't Play Nice With Content Filter Apps
 
  • Wow
Reactions: sorgo †
Yeah, Little Snitch has been complaining lately. I don't have network issues. But, it complains about not running correctly. I assume it was because my I just moved to a new MacBook Pro M2 Pro. Figure something got messed on migration.
 
I miss "just works" Apple.

Who's for a Snow Leopard year or two focused up to entirely on bug fixes and optimizations to get us back to "just works" Apple again?

Personally, I don't need gimmicky new features. I'd rather have reliable old features... and then start adding on new software bling if they must.
 
Last edited:
Anyone know if this impacts machines with a Pi-hole doing network-wide DNS filtering?
 
I've had issues on and off over the years with these, but 13.3 actually seems to be very stable for them. Reckon I'll hold off updating for a while, especially now that we have Rapid Security Response (TM).
 
My concern in that Apple is breaking things like this in a x.4 update! It used to be that major breaks and bugs would be in new OS versions, with adequate beta time to fix and address the breaks, and then subsequent point revisions would actually clear up bugs rather than introducing major new ones. MacOS is so buggy now, and seems to be getting worse by the release.
 
Apple keeps updating their software to add more bugs, instead of fixing the old ones. Software quality control is decreasing constantly. Sheesh !

Dude, you've opted into a BETA update. You're going to get regression bugs. If you don't like it, stick with Production builds.

I'm a former QA Manager for a high tech software company. This is why we do betas.
 
Apple keeps updating their software to add more bugs, instead of fixing the old ones. Software quality control is decreasing constantly. Sheesh !

Software development happens in "branches" (like a tree) where individual bugs are investigated and fixed in their own branch, and then merged into the master ... er "main"... release branch once confirmed. Meanwhile, other "feature" branches may be getting merged in, too. Development is not linear like many think. Several things are happening at once and it's extremely complex.
 
I think with all the OS security issues and constant updates to fix them, we are all going to have to switch to external hardware/ software for filtering and securing our connections to the outside world, just too much hassle working around OS changes…
 
Software development happens in "branches" (like a tree) where individual bugs are investigated and fixed in their own branch, and then merged into the master ... er "main"... release branch once confirmed. Meanwhile, other "feature" branches may be getting merged in, too. Development is not linear like many think. Several things are happening at once and it's extremely complex.
Please, someone tell Apple to revive the branch from 3 years ago that allowed us to save the on screen location of apps like the Stock app!!! So tired of the regressions! Every time I open the damn Stocks app, it is tiny and smack dab in the middle of my 49" monitor. Resize, drag to the left...about 1000 times now...gets old.
 
Dude, you've opted into a BETA update. You're going to get regression bugs. If you don't like it, stick with Production builds.

I'm a former QA Manager for a high tech software company. This is why we do betas.
This. Also remember that this might not be a bug, at least not for Apple. They may have changed some facet of the operating system intentionally and third parties, like Little Snitch, need to test against it, prior to release. That’s also why we do betas.
 
Dude, you've opted into a BETA update. You're going to get regression bugs. If you don't like it, stick with Production builds.

I'm a former QA Manager for a high tech software company. This is why we do betas.

True, but I also think that Apple has conceded the way it takes feedback from developer/public betas is really atrocious.

It doesn’t explain the fact that clearly broken things that get reported during the beta testing period just sit there sometimes for 2-3 builds and they get shipped. I mean, the animated image bug in 13.3 showed up in something like beta 3, and wasn’t fixed until 13.3.1. The ticket that was generated to track it still says that it will be fixed in a future update.
 
This. Also remember that this might not be a bug, at least not for Apple. They may have changed some facet of the operating system intentionally and third parties, like Little Snitch, need to test against it, prior to release. That’s also why we do betas.

I believe they changed something with firewall that might have depreciated some old API, so I think developers will need to adapt to this one, not Apple.

I know the "Apple can do no wrong" is strong on MacRumors, but let's be real.

IF Apple was making breaking changes to network filters automatically, they woudl have to publicly document and announce these changes so vendors can make their required updates. Right now, vendors are scrambling and knocking on Apple's door asking what broke.

And, while this is a beta, this is also an issue that should have NEVER passed the QA tests before release. This bug has broke the beta cycle for Enterprises. Any Enterprise that cares about security has network security software installed. We have devices that run beta's specifically to make sure we are aware of any changes. However, after applying the latest beta, I could not do anything. I had to do and EACAS and re-enroll. I literally watched my enrollment process and saw the exact application that was installed before the network broke.
 
Dude, you've opted into a BETA update. You're going to get regression bugs. If you don't like it, stick with Production builds.

I'm a former QA Manager for a high tech software company. This is why we do betas.
Actually, chances are this person didn’t opt into the beta at all. Good chance also their complaint was pasted from a clipboard.
 
True, but I also think that Apple has conceded the way it takes feedback from developer/public betas is really atrocious.

It doesn’t explain the fact that clearly broken things that get reported during the beta testing period just sit there sometimes for 2-3 builds and they get shipped. I mean, the animated image bug in 13.3 showed up in something like beta 3, and wasn’t fixed until 13.3.1. The ticket that was generated to track it still says that it will be fixed in a future update.
I assume a lot of what Apple look for and act on are not individual, manually submitted reports, rather automatic reports. They push a Beta out, harvest data, a see that some kit is crashing in the background for a few thousand people, and look into that using their own internal ticket.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.