My guess is that 12.4 will get released in the end of may
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Seeds Fourth Beta of macOS Monterey 12.4 to Developers [Update: Public Beta Available]
- Thread starter MacRumors
- Start date
- Sort by reaction score
The macOS 12 has not been good. A year after release and it’s not bug free yet. I’m hoping they will stick with this version for one more year and fix everything
Forget about that thought. You are having a progression of capabilities where Big Sur was major changes such as AS support, Monterey was more of refining the AS support, and Mammoth will be another example like Big Sur.
If were discussing external devices and what type of connection works and what doesn't, that more along the lines of Monterey. You can't blame Apple about this works and this doesn't work. We seen too many devices that are designed to be both windows and Mac compatible but they aren't really. Displays, storage, other external connected devices. Mammoth has to be about improving AS performance with better graphics support so development of native apps using other graphics standards are also supported such as directX11, 12.
We are introducing the next Mac Pro this year, this OS progression for AS Macs hasn't even approached what it is capable of. Too much reliance of Rosetta 2, can't run iOS/IPadOS apps much in MacOS.
What I want to see in macOS 13
After the mostly subdued macOS Monterey, macOS 13 should prove much more substantial, starting with its name.
www.imore.com
Last edited:
Has this been pulled? My Mac isn't seeing this beta at all. I'm still on 21F5063e. I've even checked via the command line
If it doesn't show try removing profile (restore defaults), restart, then reinstall dev or public beta profile and go to software update and click on advanced button -> ok -> then watch if it finds it. Should find it fairly quickly.
No it hasn't been pulled.
The full installer has also been released.
I updated with the OTA update but like to download the full installer as well in order to make the bootable usb. Unfortunately I think there wasn't one for beta 1, but there were for betas 2, 3 and 4.
If you can't update via OTA, you can just get the full installer instead.
Last edited:
Happy surprise here. I've been using the almost-vintage Bookmark Sorter app for years now, and its ability to automatically sort bookmarks in the background began to fail about a year ago; I've been using it manually. Just at random, I tried toggling that setting on again several times in the past year, to no avail. Somehow with the new 12.4, it's working!
Hold on. Safari 15 sucks big time and it is only the fault of Apple! Big Sur with Safari 14 was working fine. This new version of Safari 15 is a performance hog.Forget about that thought. You are having a progression of capabilities where Big Sur was major changes such as AS support, Monterey was more of refining the AS support, and Mammoth will be another example like Big Sur.
If were discussing external devices and what type of connection works and what doesn't, that more along the lines of Monterey. You can't blame Apple about this works and this doesn't work. We seen too many devices that are designed to be both windows and Mac compatible but they aren't really. Displays, storage, other external connected devices. Mammoth has to be about improving AS performance with better graphics support so development of native apps using other graphics standards are also supported such as directX11, 12.
We are introducing the next Mac Pro this year, this OS progression for AS Macs hasn't even approached what it is capable of. Too much reliance of Rosetta 2, can't run iOS/IPadOS apps much in MacOS.
What I want to see in macOS 13
After the mostly subdued macOS Monterey, macOS 13 should prove much more substantial, starting with its name.
On my M1 24" IMac and 16" M1 Max MBP, its very fast now. Are you using the 2019 16" Intel MBP still? How does speedometer 2 test fare comparably? Activity Monitor shows nothing amiss.
And new bugs have been appearing over time as well, like the FireWire video capture bug discussed here...
DV capture bug on 12.3 (.1)?
I recently did some experimentation with my Canon Optura 60 and HV40 DV camcorders. Somehow, with one of the recent versions of Mac OS 12 Monterey, I believe version 12.3, some kind of bug was developed that prevents video capture software from detecting IEEE-1394/FireWire video cameras! I would...
forums.macrumors.com
Any improvements in utterly slow external SSD drives (in my case LaCie Mobile SSD) on the latest beta? Tried to re-format the drive on BigSur (APFS), tried multiple cables (even Apple Thunderbolt Cable), but the drive still reads/writes like 8MB/s on Monterey (M1 Pro 16") while it works flawlessly (550MB/s read/write) on Macbook Air M1 running BigSur. ?
I'm using the latest 16" M1 Pro MBP and also late 2015 iMac. I have lots of tabs open and the memory management in Safari 15 sucks. With these many tabs on Safari 14, I had no issues. Of course the Safari web content goes on taking lots of memory. Sometimes even Firefox is faster on my Mac than Safari 15 and I have never witnessed this trend in my usage of Macs since 2007.
For comparisons I use no safari extensions, always use private mode and make sure looking at preferences there is no 3rd party trackers, cache, data. Exception is with running in normal mode for only Netflix session which can’t run in private mode because it uses 4 things. Firefox is also setup to do the same, not save anything. I found when running in normal mode to involve a incredible amount of third party activity that is totally unnecessary for web browsing. You can go to one site and end up with dozens of methods that external parties are monitoring you with.
That should only show when you encounter an app on your Mac that is not responding. You had activity monitor opened so it would show what is consuming your memory if that was a issue. The dialog doesn't show anything wrong, maybe you did this by keystrokes. (escape -option - command)
FWIW I'm not experiencing these issues. I'm having none of the Apple Music issues you're referencing, and I have a VERY large library on an external drive. Just today for the first time, Safari crashed when trying to move one tab to another Tab Group. Again, a first for me and I tend to have between 10-20 tabs open. I've seen some random graphics glitching, or where a Finder window doesn't update after adding or removing a file. And as for iCloud, at least for me, it's generally become more reliable on the 12.4 betas, especially build 21F5071b.
This is a late 2020 M1 MBP usually kept in clamshell mode, and as of now I'm actually on about 5 days of uptime, and to me that's great news considering all of the other issues so far on Monterey. But again, in my case, 12.3.1 and now the 12.4 betas have resolved most for me. The fact that I don't have kernel panics every other day seems like a win to me. Maybe I've set the bar too low.
...and I know you indicated not to reply with the old "works for me", but I believe it's important for others to know that you're making specific claims regarding specific issues, and the next person reading it will most likely not have these problems. It can look scary to someone perusing these forums to see someone posting all sorts of issues, and it's important to see that others aren't.
I also have a 2015 MBP and a 2018 Mac mini- none of these issues there, either.
Last edited:
The trouble with that mindset is two-fold:
#1 Bugs usually aren't pervasive, 100% reproducible. So the idea that some people might have been bitten and others haven't really isn't a useful metric. If one person is bitten, a bug exists. Period. If you're NOT experiencing it, keep on truckin', you likely can't provide any empirical information to help expose or resolve the conditions that cause the bug. And, who knows, someday you might trigger the bug, then, certainly, circle back around!
But #2, given #1, the chances are quite high, thanks to the moderate amount of QA that Apple apparently DOES do, that the bug only will effect a small amount of people. In that (overwhelming) case, all the "works for me" responses serve to a) drown out the actual troubleshooting/bug remediation discussion and b), worse, serve to intimidate others from testing and speaking up about weird behavior... NOBODY likes to be the black sheep who is the 1 out of 50 "admitting" they have a problem.
The avalanche of "works for me" comments really a form of social bullying, and it needs to stop. Or, go start another forum for "I experience a completely stable Apple OS so I'm special and you aren't".
We're in this thread to test beta builds. We COME HERE to find bugs, so they can be investigated, reproduced, reported, and, hopefully, resolved. "Works for me" is poison. Think of it this way, the code is SUPPOSED to work… so why are you bothering announcing that it does work over top of somebody who is trying to investigate it NOT working??
Now… it is an entirely different discussion if we're trying to work out whether a behavior is INTENDED. If you feel somebody is reporting an issue, and you think that it works a certain way different from how they're attempting to use it, by all means pipe up! That might be important! But "works for me" isn't that.
And I'm not trying to be antagonizing, I'm trying to be educational. I've been doing OS QA for 30+ years. Trust me, "works for me" is simply not helpful or necessary to the process.
I totally agree that a simple 'works for me' isn't helpful... and, to be fair here, my reply wasn't a simple 'works for me', as I briefly explained my setups to show that I'm on both an M1 Machine and a 2018 Intel Mac mini, both accessing a very large Library (7.5TB including both my Music and TV media), on an external drive. I would think that info might be helpful in eliminating some of the issues you reported. Being on the same build with the same app version, and one person has an issue and the other does not.. If it was me having the issues I'd be grateful someone provided me with a way to eliminate potential variables.
And I agree with what you're saying. That's actually the reason I included my experience, as I've also been doing the same in my line of work for roughly 20 years. I'm used to replying to people that report problems as "My computer isn't working", but don't include one iota of information beyond that. 😉 I hope you get everything sorted...
There is nothing wrong with a comment concerning I don't see that issue on my device as long as you identity your configuration instead of just saying I don't see the same issues.
When someone comments they have an issue we all try to be suggesting what to investigate. You can never assume that what you are experiencing is a general bug/error that effects all testers, because of the many Mac setups with various software installed we all utilize. I would go as far as completely rebuilding from scratch (DFU) with not importing all MacOS preferences/data/setting to test/rule something out. I use multiple Macs to test these betas with as well as many others Apple devices.