Apple Seeds Fourth Beta of macOS Monterey 12.4 to Developers [Update: Public Beta Available]

[MacRumors]

Apple today seeded the fourth beta of an upcoming macOS Monterey 12.4 update to developers for testing purposes, with the new update coming a week after the release of the third macOS Monterey 12.4 beta.

Registered developers can download the beta through the Apple Developer Center and after the appropriate profile is installed, betas will be available through the Software Update mechanism in System Preferences.

According to Apple's release notes, Universal Control in the new iPadOS 15.5 and macOS Monterey 12.4 updates is not compatible with machines running macOS 12.3 or iPadOS 15.4, so Apple suggests that as a workaround, users should update their Universal Control devices to the new betas.

When paired with a Studio Display, macOS Monterey 12.4 supports new 15.5 Studio Display firmware, which improves the quality of the webcam on the machine.

There are also new betas for macOS Big Sur 11.6.6 and the macOS Catalina 2022-005 security update.

Article Link: Apple Seeds Fourth Beta of macOS Monterey 12.4 to Developers [Update: Public Beta Available]

 

[Realityck]

I be curious to see if Safari remains the same version with beta 4? (beta 3 used a slightly older version then beta 2)

 

[Realityck]

OTA is now active, 2.55 GB download for M1 family Macs

 

[5425642]

Let's hope it's out from beta soon.

 

[tywebb13]

Build number is 21F5071b

 

[Realityck]

MacOS 12.4 beta 4

Safari Version 15.5 (17613.2.7.1.6)

System Firmware Version: 7459.121.2 (M1 based Macs)

Darwin Kernel Version 21.5.0: Tue Apr 26 23:21:38 PDT 2022; root:xnu-8020.121.3~5/RELEASE_ARM64_T8101 arm64

MacOS 12.4 beta 3

Safari Version 15.5 (17613.2.6)

System Firmware Version: 7459.120.56.0.2 (M1 based Macs)

Darwin Kernel Version 21.5.0: Thu Apr 21 19:53:52 PDT 2022; root:xnu-8020.120.68.131.2~2/RELEASE_ARM64_T6000 arm64

 

[rpmurray]

What's fixed with this release?

 

[Realityck]

The release notes are still the old beta 3.

Browser tests for this Safari Version 15.5 (17613.2.7.1.6)
Speedometer 2.0
M1 24" IMac = 342
M1 Max MBP = 350

HTML5test
M1 24" IMac = 514
M1 Max MBP = 514

 

[CMMChris]

What's fixed with this release?

Nothing as usual.

 

[Morod]

Hope they fix the "external drive not ejected" problem when you sleep the iMac.

 

[Realityck]

Nothing as usual.

Obviously you missed now much Safari caching has improved.

Back in March I posted these results
M1 24" iMac latest beta Safari 15.4 - 285, Firefox 97.0.2 - 229
M1 Max MBP latest beta Safari 15.4 - 295, Firefox 97.0.2 - 229
Both on ethernet, 12.3 beta 5.

With Beta 3 and now Beta 4 of MacOS 12.4 betas I'm seeing substantially faster scores with speedometer 2.0

Browser tests for this Safari Version 15.5 (17613.2.7.1.6)
Speedometer 2.0
M1 24" IMac = 342
M1 Max MBP = 350

Firefox 100 = 242/240 on both examples, still a bit faster.

Quite a speed improvement!

 

[Jeo_cz]

What's fixed with this release?

An eye in smiling emoji

 

[mxrider88]

What's fixed with this release?

My question is more like what did they screw up with this release.

It’s just getting worst.

Does iCloud Drive sync?

 

[Realityck]

Still get a occasional disk utility crash after erasing a unmounted external HDD volume group for making a CCC legacy bootable snapshot with M1 iMac. You of course can again launch it and it runs. Been this way thru the 12.4 betas.

 

[iAssimilated]

Can someone tell me the AMD driver version in this beta?

-> About This Mac -> System Report... -> Software -> Extensions -> AMDRadeonXxxxx

Preferably for the 6000.

 

[adh1003]

So here's my own "does it fix" list:

• Apple Music: Internal "failed to prepare to play" error (API level) -> track silently skipped, next one plays
• Apple Music: Track slight stutter at start of any and all lossless playbacks, most noticeable with rhythmic track intros
• Apple Music: After a while of working, gets into a state where it completely fails to sync playlist changes at all and never works again until you sign out of every single device everywhere then sign back in one by one, after which it works for a while until it subsequently, once again, breaks (iOS works fine, Cider works fine and astonishingly even iTunes works fine when loaded via Retroactive on the very same x86 machine where Music is sitting there, failing to sync anything)
• Apple Music: Very slow playback startup with lossless, sometimes just goes with lossy for no reason
• Apple Music: Super janky and inconsistent "back" button behaviour, when it's even visible
• Apple Music: Catalyst apps can't play any Apple Music content whatsoever; it's simply broken, acknowledged by Apple engineering several months ago but apparently making basic music playback work is a super hard challenge for today's l33t super-well-paid engineering staff or something?!
• Safari: Tab group changes completely fail to sync, see playlists above
• Safari: Attempting to e.g. rename a tab group involves fighting it constantly dropping input focus until eventually it settles long enough for you to type something (which may or may not get sync'd)
• Safari: Adding/deleting tabs within a tab group can cause a "dead" tab that can't be closed and doesn't change no matter what you try to visit
• Safari: Make enough changes in tab groups and the browser will outright crash
• Safari: Things in a tab group are trapped forever and you have to manually pull them out if you want to remove the tab group but keep the tabs (deleting a tab group will replace every window on every device that has that tab group with a tabs from an apparently-arbitrarily-chosen other tab group, but in a kinda-broken state where they don't quite sync properly and, of course, what you wanted it to do was just delete the group, but leave your Safari windows and their tabs open - just not in a named group anymore)
• Safari: M1 only AFAICS, gets into a state where external link opens don't work - the browser gains focus but no new page or tab opens; requires actual reboot, not just a Safari quit/restart to resolve; fortunately, very rare
• iCloud drive: Can fail to sync, as above, anyone at Apple notice a pattern here?!
• macOS: Since round about Monterey, a rewritten trackpad driver appears to have a very large number of race conditions which can introduce super-annoying misbehaviour such as: You're dragging something. You used to be able to reliably use a two-finger scroll gesture at the same time as the drag. Now that sometimes works or sometimes, bizarrely, your scroll gesture makes the mouse pointer move instead...

...you get the idea. These are faults I've experienced consistently personally on a wide variety of machines, of a wide age span and across Intel and x86, both brand new purchased with Monterey from the start back to machines upgraded over several years of macOS releases. There are Reddit threads for just about all of them, so please don't add "works for me" comments - good for you; it doesn't work for a lot of other people.

As another poster herein observes, nothing ever seems to get fixed; we just see the bugs get worse and more numerous. When a new bug gets into your workflow, your heart sinks and your stress levels peak, because you know that this is it forever; it's never going to get sorted. So I can answer my own question: No. The new beta and its subsequent general release will fix none of those.

 

[Realityck]

....you get the idea. These are faults I've experienced consistently personally on a wide variety of machines, of a wide age span and across Intel and x86, both brand new purchased with Monterey from the start back to machines upgraded over several years of macOS releases. There are Reddit threads for just about all of them, so please don't add "works for me" comments - good for you; it doesn't work for a lot of other people.

As another poster herein observes, nothing ever seems to get fixed; we just see the bugs get worse and more numerous. When a new bug gets into your workflow, your heart sinks and your stress levels peak, because you know that this is it forever; it's never going to get sorted. So I can answer my own question: No. The new beta and its subsequent general release will fix none of those.

If your not testing this beta 4 against your list, whats the point?

 

[adh1003]

If your not testing this beta 4 against your list, whats the point?

Bug reports are submitted, but there's no response to any of them and no request to retry on a beta. As a beta tester, you will of course be familiar with the developer feedback mechanisms and that Apple engineering do specifically ask if something should be retried on a specific Developer Preview, beta or general public release. I'm not being paid by Apple and my time is valuable, so unless they explicitly ask me to re-test, why on earth would I? They've got the bug, they can act upon that if they wish.

The Developer Preview and (to a lesser extent) beta processes are meant to be about trying new things out (if you really want to) mostly to see if it breaks your own applications. That said, "trying new things out" is increasingly difficult as Apple's documentation is so sparse; did it really take hundreds of macOS engineers a full week to fix one single bug in StoreKit, which is the one and only change described in the Beta 4 release notes? What else changed? If nothing, what on earth did everyone spend all week doing?

Anyway, it's not free testing for Apple and, even if it were, it'd be about finding and letting them know about new bugs. You surely aren't suggesting that end-users should regression test existing bugs in Apple's own software for them...?

 

[Realityck]

Bug reports are submitted, but there's no response to any of them and no request to retry on a beta. As a beta tester, you will of course be familiar with the developer feedback mechanisms and that Apple engineering do specifically ask if something should be retried on a specific Developer Preview, beta or general public release. I'm not being paid by Apple and my time is valuable, so unless they explicitly ask me to re-test, why on earth would I? They've got the bug, they can act upon that if they wish.

The Developer Preview and (to a lesser extent) beta processes are meant to be about trying new things out (if you really want to) mostly to see if it breaks your own applications. That said, "trying new things out" is increasingly difficult as Apple's documentation is so sparse; did it really take hundreds of macOS engineers a full week to fix one single bug in StoreKit, which is the one and only change described in the Beta 4 release notes? What else changed? If nothing, what on earth did everyone spend all week doing?

Anyway, it's not free testing for Apple and, even if it were, it'd be about finding and letting them know about new bugs. You surely aren't suggesting that end-users should regression test existing bugs in Apple's own software for them...?

It's very rare to get some return query to submitted feedback in the inbox. Like the only time they do that is when someone has a particular instance where they are trying to understand the issue from several "like" bug reports.

When asked if they even read your submitted feedback that you make attempt to author accurately w/attachments and never receive responses, I was told they do look at everything submitted by staff. That answer was via phone call to Apple staff concerning a Apple developer seeding issue with web page FTP accessibility that effected many participants.

I know in this modern day, you would think they would have a message read by staff indication, but they don't. Yeah I asked that question also, likely not enough time in the day to get back to all submissions.

 

[moodler]

Obviously you missed now much Safari caching has improved.

Back in March I posted these results
M1 24" iMac latest beta Safari 15.4 - 285, Firefox 97.0.2 - 229
M1 Max MBP latest beta Safari 15.4 - 295, Firefox 97.0.2 - 229
Both on ethernet, 12.3 beta 5.

With Beta 3 and now Beta 4 of MacOS 12.4 betas I'm seeing substantially faster scores with speedometer 2.0

Browser tests for this Safari Version 15.5 (17613.2.7.1.6)
Speedometer 2.0
M1 24" IMac = 342
M1 Max MBP = 350

Firefox 100 = 242/240 on both examples, still a bit faster.

Quite a speed improvement!

OK, but this is an app update, not an OS update.

 

[blesio]

Anyone knows if the fixed the non working Apple Multi AV USBC Hub? The previous beta borked the Video output, it just stopped recognizing the HDMI, USB-A worked fine, charging worked fine, HDMI was a no-go....

 

[Bazil_Fawlty]

Can someone tell me the AMD driver version in this beta?

-> About This Mac -> System Report... -> Software -> Extensions -> AMDRadeonXxxxx

Preferably for the 6000.

Version 4.8.54 on my Intel MacBook Pro 2019 running 12.4b4

 

[Ilde]

Hi everyone,

A slight change I found is the keyboard language country flag disclosed on the top bar is no longer available. This country flag was disclosed when you have more than one keyboard selected as input source.

Regards.

 

[5425642]

Is the beta for 12.4 any better then 12.3?

 

[Realityck]

Is the beta for 12.4 any better then 12.3?

IMHO yes. Safari is faster, not seeing any memory oddities. Only thing I encountered is the occasional disk utility quitting. Still see another couple of betas coming because Safari/system FW/Darwin kernel versions are changing before WWDC happens next month.