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
68,537
39,377


The release candidate version of macOS Ventura 13.4 fixes a frustrating content filter bug that was introduced in an earlier version of the macOS Ventura 13.4 beta, so users who install the macOS Ventura 13.4 public release next week will not need to worry about networking issues.

macos-ventura-roundup-header.jpg

Last week's fourth beta caused macOS Ventura 13.4 not to work with content filtering apps like Little Snitch and Radio Silence. After installing the update, some users on the MacRumors forums and on Twitter had problems with network connectivity, and it turned out that firewall apps were the cause.


Disabling content filtering apps fixed the problem, but Apple has addressed the overall issue and now content filter apps work with the macOS Ventura 13.4 update.

macOS Ventura 13.4 and iOS 16.5 will be released to the public next week.

Article Link: macOS Ventura 13.4 RC Fixes Bug With Content Filter Apps
 
Is this version up for the Public Beta testers - I couldn’t tell on the software update box and do not want to install last weeks buggy version.
 
After having read about the problems with Little Snitch, I think that I will wait a few weeks before installing and see how real world users are finding compatibility with the program.
Similar things have happened such as effecting VPN client on a late beta where they just correct the issue on a RC.
 
Last edited:
Hi everyone,

Here you are what I found when trying unenrolling from beta programs using console:

Last login: Tue May 9 21:22:59 on console

ilde@MacBook-Pro-de-Ilde ~ % - sudo /System/Library/PrivateFrameworks/Seeding.framework/Versions/A/Resources/seedutil unenroll DeveloperSeed

Password:

Unenrolling...

Unenrolling from beta programs is no longer supported through seedutil.

ilde@MacBook-Pro-de-Ilde ~ %

Regards.
 
This is why I only install the RC for macOS releases after dot two. Prior to dot three I install the beta builds too for stability.
 
Just waiting for someone on here to insist this bug should never have happened in the first place - showing a drastic misunderstanding of how software development works, and specifically why betas are a thing.
 
Just waiting for someone on here to insist this bug should never have happened in the first place - showing a drastic misunderstanding of how software development works, and specifically why betas are a thing.
Let get this straight. It is NOT that the software has bugs, we all get that is part of the beta cycle.

The issue was that this bug was so severe that it effectively made it nearly impossible to test B4 for many customers.

The issue is that this severe of a bug should have been caught by Apple before the beta was released. It is not like Network Content filters are some edge case. They are heavily used in the Enterprise.
 
The issue is that this severe of a bug should have been caught by Apple before the beta was released. It is not like Network Content filters are some edge case. They are heavily used in the Enterprise.
Most consumers wouldn't be using content filter apps utilities, they simply are not your usual hardened enterprise example. Ventura is set up for blocking incoming connections, but we are talking about the use of outgoing connections involving apps. Perhaps the next MacOS will support the firewall involving outgoing connections?
 
Last edited:
  • Like
Reactions: KeithBN
Let get this straight. It is NOT that the software has bugs, we all get that is part of the beta cycle.

The issue was that this bug was so severe that it effectively made it nearly impossible to test B4 for many customers.

The issue is that this severe of a bug should have been caught by Apple before the beta was released. It is not like Network Content filters are some edge case. They are heavily used in the Enterprise.
You should NOT be running beta software on a production machine, full stop. If you're using a dedicated beta machine (or VM), then a bug like this, while annoying, shouldn't affect your ability to test other items.

Furthermore, while yes this bug should've been caught before the beta was released, bugs do fall through the cracks all the time, and there is a reason we have betas!
 
Excusing major bugs, is why developers like Apple don't seem to care and limit the budget and time for testing.
I don't know anyone here that can prove that.

If five people out of a thousand use a 3rd party utility that breaks against a beta release does that mean the OS hasn't been tested adequately? Its was certainly identified quick enough and rectified. ;)
 
  • Like
Reactions: tshane and KeithBN
Excusing major bugs, is why developers like Apple don't seem to care and limit the budget and time for testing.
It would only be a major bug if it was released in the final non-beta build. Otherwise, it's a f*cking beta - bugs happen in betas, that's why we have them. This isn't complicated 🤯
 
  • Like
Reactions: wanha and KeithBN
You should NOT be running beta software on a production machine, full stop.
Please point where I said I was testing on a production machine. I didn't. I have dedicated equipment strictly for beta testing.
If you're using a dedicated beta machine (or VM), then a bug like this, while annoying, shouldn't affect your ability to test other items.
How can I test on a computer that can't reach the internet? For Enterprise customers of Apple, we have to test Beta against our software stack. I don't just install a vanilla O/S load and play around. I run every beta through multiple cycles, including upgrades and new enrollments. That has to include installing our security stack. However, with this beta, I could not even finish a simple enrollment. So, yes, it did affect my ability to test.
Furthermore, while yes this bug should've been caught before the beta was released, bugs do fall through the cracks all the time, and there is a reason we have betas!
 
The filter issue wasn't a bug that crept through: it was listed as a known issue (108814599) that was mentioned in the release notes for 13.4 b4.

They knew about it, but regardless chose to release it as a public beta.
 
Websites like facebook and seeking alpha have pages that are jumping, both in safari and firefox.
Hope Apple is fixing this although their support is beyond worthless
 
Websites like facebook and seeking alpha have pages that are jumping, both in safari and firefox.
Hope Apple is fixing this although their support is beyond worthless
Why would accessing a web site cause the HTML content to jump? Looking at Seeking Alpha with Firefox 113.0 and Safari Version 16.5 (18615.2.9.11.4) looks fine on a AS Mac. Is this some graphic issue with an old intel Mac ?
 
Last edited:
  • Like
Reactions: KeithBN
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.