Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I did a macOS public beta once or twice before realizing how little appetite I have for my machine running hot, slow and buggy. So I just never did it again.

I have zero patience for people who come onto forums to whinge about bugs in a beta since surfacing the bugs is literally the point of the process.
What about people who are reporting that the issue occurs on GA’d builds as fresh installs, who are still seeing it after multiple beta cycles and releases? Any patience for them?
 
  • Love
Reactions: -BigMac-
And now we know why companies often don’t offer beta releases to the general public.
It's been happening on stable versions for months. Heaps of reports - still there.

i saved a screenshot of this happening in production, not beta.
So (and apologies to Contact_Feanor, as I’m replying to a number of posts at the same time), this issue is one that a large number of testers have had since iOS 26 beta 1, reported throughout the entire beta cycle, and the bug shipped in iOS 26. Then it was present in iOS 26.1 beta 1 throughout its beta cycle, and is present in the release version of iOS 26.1, and has now been present through all the betas of 26.2.

It persists through a restore and setup as new, at least on an iPhone 15 Pro Max. It’s definitely present on both my parents iPhone 17’s, non-pro, both of which only run release software.

This isn’t some obscure bug; I’m sure there are a lot of folks out there who’s use or configuration doesn’t make the issue apparent to them, but if it’s reproducible on a DFU restore as new without logging into iCloud, it’s the software, straight up. I spent seven years troubleshooting Apple hardware at the Genius Bar, and this is absolutely the sort of thing a fresh install used to fix. It simply doesn’t anymore.

That’s straight crazy. Apple makes the hardware, decides what range of hardware an OS can run on, codes the software, and provides both the backup/restore functionality and data sync functionality. It’s nuts that this obvious of an issue can persist through, by my quick count, 10 betas and 2 release versions. I’ve tried each beta as a restore and setup as new without syncing, since it’s my test device, and it’s present on every single install. It’s so much worse if you actually try and use the new visual candy, like having your app icons clear with a colored background to show off “Liquid Glass”.

“It’s a beta” doesn’t work as an explanation here, since it’s also been glaringly obvious on two release versions. “Your configuration/“doesn’t happen on mine so it must be an issue on your end”” also doesn’t work, since it’s easily reproducible on a factory fresh general release if you use the features as advertised; the OS does not work as expected on Apples own hardware with a fresh install. Simple as that.

I’ve been an Apple fanboi for years, but ignoring the obvious slide in their QC over the years is just a bridge too far. It feels like Apple fans are in an abusive relationship now, and can’t acknowledge when Apple’s products make something from MS, which doesn’t have the same vertical integration, look reliable as hell.
That’s the issue here; folks keep saying “but it’s a beta!!!” when those who’ve been using each beta are saying “after something like ten betas and two release versions this insane bug is still somehow present”.

It’s funny too, so many issues like this used to fix themselves once spotlight indexing etc finished after the update; this particular bug seems to go away after each update and then pops back up a few hours later.
What about people who are reporting that the issue occurs on GA’d builds as fresh installs, who are still seeing it after multiple beta cycles and releases? Any patience for them?

Yep - thank you! Finally some actual Beta testers🙂.. unlike the keyboard warriors commenting "bUt iTs A BEta".
Btw I think some of them straight up copy and paste their comments in beta threads trying to portray Apple as some perfect, untouchable company - must be QC staff 😅

Homie still on 4G? Is your cell service in Chernobyl?
Haha yea - Melbourne, Australia. We have 5G in most places, then black spots in others haha
Apparently we are like 10+ years behind some countries in infrastructure 😂

I just pray 4G hangs on for dear life sometimes😅
 
Letting non-developers use beta versions was a mistake.
When Apple let anyone run a beta. It was better when it was locked down because the vast majority of the public has no idea what a beta means. They gloss over and skip all the warnings and terms.
I do hope that was directed as me (I often have no idea about things).

Tim Jobs the 2nd - "Macrumors Newbie". Welcome to the forums my dude:)

You know, I was a "Macrumors Newbie" in 2011 - registered Apple Developer, running my Mac Pro on Snow Leopard - how time flies hey? some good memories🙂

Be sure to let us "no idea" members know if you need help setting up your signature, or navigating the Forum categories😘
 
  • Like
  • Love
Reactions: Parowdy and UliBaer
I have four active bugs related to apples accessibility features in thefeedback app.
Two of those four bugs are fixed in the latest 26.2 beta and reflected in the feedback app as resolved, the third is known by Apple. Only the fourth is still not responded to but *appears* to be resolved in the latest round of 26.2 betas.
So I very much believe that Apple responds to feedback submissions. Not sure why there’s a conspiracy theory about that.

Mind sharing what those four active bugs related to accessibility features are? I have issues with improved contrast resulting in keystroks beeing HDR, and sometimes even breaking completely. Disabled it for now.
 
Last edited:
If you want to see a really ridiculous bug, use the camera from the lock screen horizontally.
The swipe gestures are all messed up and when you share a picture, it looks like this:
IMG_4249.png

Also, let’s not forget the oldest bug still present in every single iPhone today, literally introduced the day iPhone X was released: the control center accessibility bug

A bug well known by Apple, but so was that the 2016-2019 MBP design was a regression and environmentally very unfriendly.

But here is some fun. You can take a look at an even older oversight on your iPhone right now, no matter the iOS version.
First, open your Photos gallery. Then, flick across the screen to move the thumbnails/previews up and down. Immediately after, swipe up to go into the App Switcher. You will see that the previously smooth scrolling animation in Photos becomes choppy.
Just like the previous bug, I’ve reported this to Apple many years ago. But oh well.

Right now I experience the bug where I can’t get the keyboard to go away since the bar with the X is gone. Fun.
IMG_4410.png
 
And Apple doesn't read those. You can vent here, sure. But don't expect any time on these threads to result in things getting better.


No matter how much money a company has, there is a limited talent pool to hire. And who is going to train and develop them but the same people who are not catching the problems in the first place? Do you trust the current Apple staff to train the next generation to be better than they are? As you build up your staff, you just need more supervisors, have more training classes to schedule, have more HR to hire, more bathrooms, more cafeteria space, more vending machines, etc. Throwing more money at a problem isn't the solution.

If Apple wants to do a major effort to fix bugs, they have two paths:

Option 1) Something like Google once tried with Fuchsia or is apparently trying again with Aluminum. That is, work behind the scenes for years making a new OS without any input from users. Something that replaces all the code, all the features. A complete restart that will need new hardware and most likely not be compatible with anything you currently own. Emerge from the shadows in 5 years with something called Apple Phone 1.0.



See? Tons of tech debt. Starting over is the only "pure" fix. The bug you are showcasing is an issue with Springboard, which has been the most slapdash piece of rickety code since they started bolting on new features to it in iOS 14. It has only gotten worse over the years. You don't fix that with money. You fix it with a do-over.

Option 2) Slow down. No more annual releases. Releases are generational - once every 5 years or so. Instead, new features enter beta every quarter year or half year as needed. Developer betas last months. Take the time to read the feedback. Communicate what testers should actually be testing. Blog about progress. Be open. This would probably need Apple to follow a format like the Google Play Store, where app updates are separate from system updates, because if your OS only updates twice a year then you need to be able to push out fixes for individual apps quicker in case something breaks. Componentized updates for apps would allow them to spend much longer on the big stuff. It would be a lot less flashy. No WWDC. Less press coverage. Apple would need to sell the phone on the hardware alone.
I truly believe Apple needs to stop with annual updates and introduce when ready. This push led to the problems with AI vaporware. And now Apple has let go the executive in charge of AI, when the CFO denied the funds that he required even though Crook approved them. I mean the buck has to stop somewhere and the big problem is the CEO doesn’t understand anything but how to run AAPL as a financial institution instead of a tech company. This is why everyone is destroying Apple on everything except hardware where Apple is furthering their anticompetitive behavior by wanting to control the entire stack of hardware. Blame third parties when they don’t pay their employees and treat them like slaves, and they all get away with it because they’re the top 1% that control the world making all the bank.

Apple needs to be run like a tech company with a tech CEO who understands products and consumers. Crook only understands money.
 
as everyone points out to you, OP, this is a BETA.

You know this.

Why complain here about a BETA in this way - is it even a public Beta or is a developer Beta, ive no idea. If its a developer beta then If you arent a genuine developer you shouldn't even be accessing it.

Direct your energies into helping Apple out in the Beta programme to which you are subscribed and do your job as a Beta Tester to find bugs and report them to Apple as part of the development process.


If this sort of thing was present in public releases then you can whinge - but not before.
 
The whole point of the Beta is to find and detect bugs and let Apple know about them.
I oft wondered why well-reported bugs - like how nightstand mode always ends up displaying two temperature panels losing the important clock part - can be reported complete with not just screenshots and videos of how to make it happen, but detailed writeups (and I've lived in Mantis/Jira/et al. for decades so am no stranger to this)

Or how, Safari's navigation and address buttons, since liquid glass, keep tinting into the colour of pop-up advertising and locking to that colour.

Or how, when you zoom the screen to a mere 120% to account for old eyes, the iPad keyboard covers so much of the screen that you can't see the fields you are typing in, this one started in 18 and got far worse with Liquid A** and the movable searchbar - just why do I need letters that are so tall?

Or how the keyboard can no longer decide which colour it wants to be today.

Or how CSS full-page slide over ads break safari no end. Complete with videos showing it and descriptions.

Or AI changing words to obnoxious replacements when I've disabled the unwanted feature.

Or all the endless bugs I find in basic accessability operation that make my life harder, every day.

All reported, all ignored.


In terms of QA, it's about time Tim stopped with the "the next flashy thing we will announce but never deliver" stuff and really do some work on the meat of it. He needs to do a code red on bug fixing.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.