This would explain the buggy software this year lmao.
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.
- Status
That will likely be a very good thing. Quality of reports is going to shoot up.
I picture a bunch of Apple workers following this thread…just laughing hysterically. 😂🤣
Brought my watch charger with me to work for the same reason
I guess they’re also laughing when ignoring bugs for months.
Still a couple hours today for something to come.
Or just tomorrow.
Point releases have come out mid week, especially after a holiday.
Apple still saying UC for iPadOS & MacOS is later this autumn (or Fall for you Americans). So, I do wonder if they are just going to make it available in the RC/Public release as a beta feature, based on what we have seen in MacOS (as per the screenshot @gwhizkids posted, that I reposted).
Or just tomorrow.
Point releases have come out mid week, especially after a holiday.
Apple still saying UC for iPadOS & MacOS is later this autumn (or Fall for you Americans). So, I do wonder if they are just going to make it available in the RC/Public release as a beta feature, based on what we have seen in MacOS (as per the screenshot @gwhizkids posted, that I reposted).
Prior to iOS 14, it was about 50/50 between a GM (the old name for RC) or beta straight to public. Only iOS 14 has had almost every release have an RC first. 14.8 & 14.8.1 had no betas and no RC, from memory
These are betas — they're expected to have bugs, and they even warn us right up front (emphasis mine):
Keep in mind that Apple releases betas on their schedule, not ours, and they prioritize the bugs that get fixed in each beta. They're not going to bump usability issues up the fix list on beta builds because their expectation is that the people using betas are doing so on devices being used for app development to ensure compatibility with upcoming iOS/iPadOS/macOS releases, not the devices they actually carry around and use every day. (And as public betas are frequently the same builds as developer betas, the same caveats apply — it's still unfinished software and it should be expected that things will be broken.)
Those of us who ignore that warning and install betas on our everyday devices anyway already know (or should know) what we're signing up for, and it should not come as a surprise when a beta build breaks features we use on a regular basis. That's life on the beta train, and I'd suggest that anyone not comfortable with dealing with broken features for weeks at a time should probably just stay on the platform with public releases and let the rest of us at the bleeding edge deal with the pain instead.
Last edited:
Completely agree. I am a pacifist, but let me tell you, dont bring beta software near my house or we will have more than words. I´ve seen people suffer from high cholesterol and heart attacks because of the stress produced by beta software.
Its very dangerous, I´m telling you.
If you think that there are no bugs in the official releases, you’re very mistaken.
I'm actually happy in guessing it would NOT be this week as I'm expecting a major Maps update within the next week to coincide with 15.2 going public. Hoping for USA mass LookAround release as well as road details across the country as they stated at WWDC. They will need to coincide.
Beats Fit Pro firmware received an update as well.
They dropped another grape...
They dropped another grape...
Oh, I didn't say there weren't, to be sure — but that's a far cry from installing something that is expected to be broken. ?If you think that there are no bugs in the official releases, you’re very mistaken.
Addendum: It's also worth noting that many app developers can't or won't provide support for apps that don't work right if they're running on a device with a beta OS installed — only for devices running a publicly released OS. So there's another negative incentive for installing betas on a primary device — you may be stuck not only with broken iOS/iPadOS features, but also broken apps until either a future beta, public release, or app update when the dev has the opportunity to update for the latest release (which they may not be able to do before the release because it's not unheard of for a compatibility fix for a future iOS update to break compatibility with the current version of iOS).
Last edited:
I was talking about poor software quality in general, have never mentioned anything beta-related. As a software engineer myself, I think I know enough about beta software and how development works, but thanks for enlightening me.
I used your posts as a starting point, but it wasn't targeted at you in particular — apologies if it came across that way. I based it more on a general discussion in the thread around beta software quality as there seems to be quite a few folks in the forum/thread who aren't familiar with software development processes and lifecycles.
Never understood why they gave a huge bump in Maps in Lisbon, Portugal instead of all of USA first.
