Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Confirmed on my MBP that b4 is not playing well with network filters. I have Objective-See LuLu installed. After the MacOS Ventura b4 update, no network connections were working (Wifi, Wired). I decided to disable LuLu (and updated it to latest version) and with LuLu disabled, everything is running perfectly.
 
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.
That is a good point. Point releases should refine. However, seems like they are trying to do the agile thing of constant releases. Find if security and bugs. But, feature are definitely being release. I wonder if root cause is features or regression part of other bug fixes. Fix 2, break 1.
 
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.

Yes, there are always tradeoffs and things that you can’t catch in a beta, but it’s strange to me that Apple is actively changing so many things under the hood (e.g. sometimes abruptly enforcing a deprecation in the middle of a major version). I don’t have any proof, I just feel like this is part of the reason that these bugs are showing up.

Apple once completely hosed AppleScript 5 builds into a beta cycle which was just baffling to me: https://mjtsai.com/blog/2022/07/06/applescript-broken-in-macos-12-5-beta-5/
 
Last edited:
After the update, neither my M1 Pro nor my Intel Macbook Pro would connect to the Internet, either wirelessly or hardwired. I disabled all the Cisco AnyConnect stuff in my networking settings and everything (email, Internet) runs fine. Except I can't use AnyConnect to get into my workplace VPN.

The kooky way I get around that? Fire up Windows in Parallels and connect to work through the AnyConnect VPN there. Crazy that Windows via Parallels lets me connect to the VPN, but the new Ventura Beta doesn't.
 
I appreciate people testing non-production code for the rest of us who can't do that because we have a primary machine that's critical for us to do work on.

There's millions of different configurations out there, and Apple can't test them all. I'm glad this kind of thing gets found before release - as long as they fix it, unlike say, the USB bugs that *still* haven't been fixed since Monterey was released.

But...a firewall impacting bug? Yeah, that should have been caught internally. If it was just one app, ok, get a pass. But for the entire class of apps? That's an API defect that regression should have caught.

Still no sympathy for people complaining they can't do work. Don't install betas on production machines.
 
After the update; a strange thing happened on my M1 Pro while connected to an external monitor. The mac display itself is not active at all. Even after unplugging my dock, my MacBook screen is just off.

I had to force reboot to fix it.
 
Apple keeps updating their software to add more bugs, instead of fixing the old ones. Software quality control is decreasing constantly. Sheesh !

Indeed. It's a mess.

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.
As people above have said, it's beta software. I half suspect that they incorporated outside libraries that had been updated for security reasons. The things the filters were doing might have been exploits in the hands of bad people.
Anyone know if this impacts machines with a Pi-hole doing network-wide DNS filtering?
That would be very unlikely.
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.
That feature might have been deleted because, it interacted with something they changed and that interaction would be bad.
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.
I suspect Apple uses third party libraries. I strongly suspect those libraries fixed potential exploits in their code. I suspect the internet filters were using those potential exploits. I have been seeing much of my Linux software stop working because of updates to Ubuntu. I suspect this is true for many distros.
 
As a long time little snitch user, that's good to know!
I don't install betas anyway...
 
Ventura is fine I just dislike the new system settings it's narrow and hard to find stuff, truly not made for large screens.
I guess you haven't experienced the thunderbolt bugs I've experienced, the USB dropouts, my Aquantia lan adapter bugging out when the system resumes from sleep, kernel panics. On Monterey, my Macintosh can stay up for 30+ days without the need for a restart. On Ventura with the same hardware, it crashes every 3-4 days. Clean install. What's the point of moving to Ventura if it is bugged out?
 
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.
Yep. I'm staying put on the production build - macOS Big Sur.
 
I guess you haven't experienced the thunderbolt bugs I've experienced, the USB dropouts, my Aquantia lan adapter bugging out when the system resumes from sleep, kernel panics. On Monterey, my Macintosh can stay up for 30+ days without the need for a restart. On Ventura with the same hardware, it crashes every 3-4 days. Clean install. What's the point of moving to Ventura if it is bugged out?
I'm sorry to hear that I can relate to the thunderbolt bugs one of my TB drives sometimes fails to mount on restart I thought it was a cable malfunction as per the network issue I haven't had any I use a manual static ip and dns.
 
Just another reason not to "upgrade"
Thanks, I will stick with Monterey.
Apple, get back to making things BETTER, not DIFFERENT.
My computer is a tool, not a fashion item, I do not care if it looks the same for 20 years, what I don't want is having to relearn everything I have done for 20 years and have lots of stuff continuously broken.
 
Still no sympathy for people complaining they can't do work. Don't install betas on production machines.
This isn't the first time something like an incoming/outgoing app blocker (3rd party network filter) has caused problems. Little Snitch for example was previous discussed concerning some past MacOS issues. Most people normally would not be using this type of app.
 
Issues like these being found are exactly the reason you do public betas.
Issues like these are exactly the reason I don’t try Apple betas anymore, even as a dev.

I’m not going to play the free worker for a multi billion dollar company.
If they pay me, i might give it a try.

Ramp up the paid internal testers and such things doesn’t happen.
In my opinion public beta tests is to catch smaller glitches, but a show stopper like this is something for internal testers.

Apple’s Software quality is 🤮, this just means that till now not a single soul at Apple tried the content filtering feature, it’s as if they don’t use their own crap.

RSR says it all!
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.