What on Earth is happening at Apple QC? LAUGHABLE BUG

[-BigMac-]

LOL cmon Apple… this has to be a joke.

26.2 beta 2 on 16ProMax

Is Apple Quality Control even in the room with us anymore?

Reminder: this is a 4 Trillion dollar company.. their budget for QC is $WhatEverTheyWant

And yes - it’s a beta (mistakes happen), but these ‘mistakes’ are happening a lot more often than I ever remember.

So for now - while this bug has been reported to Apple - we can all laugh at all its glory, and let it serve as a reminder to us all.. that no matter how inexperienced, inattentive, unqualified, or uncaring we may be - we can always apply for a job at Apple QC 🤣

Screenshot and video attached for the shared lols🙏🏼🤭

 

[I7guy]

The release is still a beta.

 

[-BigMac-]

The release is still a beta.

Yes I acknowledge that in the post, along with an overarching conclusion of increasingly common unreliability and polish throughout the OS.

The current stable version has significant bugs. I made a thread about one recently. This from a company which has endless pockets and a huge beta base - to QC stable builds and prevent these sort of coding errors.

I think the time to excuse Apple every single instance there is an issue is wearing thin, and users are becoming aware

 

[TumbleDryer]

The whole point of the Beta is to find and detect bugs and let Apple know about them. It's not to get the latest stable software then moan about it when there are bugs because its not stable. It's like asking someone to paint a wall and walking in halfway through saying 'you've missed a bit'.

SO many people download the beta with no intention of testing and reporting and then moan it's not polished on forums. Tell Apple.

 

[-BigMac-]

The whole point of the Beta is to find and detect bugs and let Apple know about them. It's not to get the latest stable software then moan about it when there are bugs because its not stable. It's like asking someone to paint a wall and walking in halfway through saying 'you've missed a bit'.

SO many people download the beta with no intention of testing and reporting and then moan it's not polished on forums. Tell Apple.

Thanks for NOT reading any of my original post, and commenting the generic #ItsABeta comment👍🏼

TLDR original post:
1) I acknowledge its a beta
2) I acknowledge Betas have issues, because Beta
3) I state I reported it to Apple
4) I state there is a growing number of bugs in stable releases

Yes “its a beta” - but its the second beta, of the third major release, of the 19th OS cycle - of a 4 trillion dollar company.

You reckon all home screen icons disappearing is of a beta standard given all that? If so, I reckon you need to swallow a tough pill and realise Apple is not always justified and right - they are dropping standard, maybe youre in too deep to notice👀🤗

 

[HouseLannister]

The current stable version has significant bugs. I made a thread about one recently.

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.

Reminder: this is a 4 Trillion dollar company.. their budget for QC is $WhatEverTheyWant

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.

Yes “its a beta” - but its the second beta, of the third major release, of the 19th OS cycle - of a 4 trillion dollar company.

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.

 

[HouseLannister]

And stop saying $4 trillion dollars. That's not a real number. It only means anything to shareholders.

Apple has $54 billion and I am sure they would like to keep as much of it as possible. Those AI acquisitions they are eyeing are not going to come cheap.

Apple (AAPL) - Cash on Hand

List of the top public companies ranked by cash on hand. A company’s cash on hand also refered as cash or cash equivalents (CCE), is the amount of accessible money a business has.

companiesmarketcap.com

 

[Apple_Robert]

Often times, a bug will only show intermittently to only a small group of people. As such, it can make it more difficult to find and fix the bug.

And as a follow-up, often times in beta, fixing one problem can end up breaking something else that wasn't a problem before.

The fact that you encountered this problem does not show sloppiness on the developer team at Apple.

I think your rant is without merit.

 

[JCCL]

The whole point of the Beta is to find and detect bugs and let Apple know about them. It's not to get the latest stable software then moan about it when there are bugs because its not stable. It's like asking someone to paint a wall and walking in halfway through saying 'you've missed a bit'.

SO many people download the beta with no intention of testing and reporting and then moan it's not polished on forums. Tell Apple.

That would be typically true, however the 26.1 release build is even buggier than 26.2 beta. I actually had crashes (more recently in WatchOS) that were fixed by updating from stable to beta.

 

[Lounge vibes 05]

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.

 

[-BigMac-]

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 100% agree, and would encourage Apple to implement both the options simultaneously. We just need a solid, reliable OS after all these years

 

[-BigMac-]

That would be typically true, however the 26.1 release build is even buggier than 26.2 beta. I actually had crashes (more recently in WatchOS) that were fixed by updating from stable to beta.

Same here. Not to mention stable was overheating my Pro Max at idle - like it was constantly in direct sunlight.

At least beta is no longer doing that

 

[hovscorpion12]

Unless your post is a typo, best recommendation i can make is to upgrade to beta 3.

This bug does not exist on my testing unit nor others.

 

[DCohen726]

LOL cmon Apple… this has to be a joke.

26.2 beta 2 on 16ProMax

Is Apple Quality Control even in the room with us anymore?

Reminder: this is a 4 Trillion dollar company.. their budget for QC is $WhatEverTheyWant

And yes - it’s a beta (mistakes happen), but these ‘mistakes’ are happening a lot more often than I ever remember.

So for now - while this bug has been reported to Apple - we can all laugh at all its glory, and let it serve as a reminder to us all.. that no matter how inexperienced, inattentive, unqualified, or uncaring we may be - we can always apply for a job at Apple QC 🤣

Screenshot and video attached for the shared lols🙏🏼🤭

Yo

LOL cmon Apple… this has to be a joke.

26.2 beta 2 on 16ProMax

Is Apple Quality Control even in the room with us anymore?

Reminder: this is a 4 Trillion dollar company.. their budget for QC is $WhatEverTheyWant

And yes - it’s a beta (mistakes happen), but these ‘mistakes’ are happening a lot more often than I ever remember.

So for now - while this bug has been reported to Apple - we can all laugh at all its glory, and let it serve as a reminder to us all.. that no matter how inexperienced, inattentive, unqualified, or uncaring we may be - we can always apply for a job at Apple QC 🤣

Screenshot and video attached for the shared lols🙏🏼🤭

View attachment 2584266
View attachment 2584267

You think this is buggy?!? You wouldn’t have survived the Steve Jobs era

 

[ignatius345]

Yes I acknowledge that in the post

But it's still a beta, which is part of the "QC" process you're complaining about. Report the bug via Feedback Assistant and move on. If it's still in the final 26.2 release, maybe save your all caps screaming subject line for that.

 

[d123]

LOL cmon Apple… this has to be a joke.

26.2 beta 2 on 16ProMax

Yes “its a beta” - but its the second beta

1. It’s a beta, expect bugs

2. Update to the newest beta, it may fix the bug

 

[Mr_Brightside_@]

You’re running beta software

 

[bk125]

"My stove company has no QC, I burned myself on the burner."

 

[mxrider88]

I had the same issue on Tahoe the other day, folders gone. Had to force quit Finder.

Not on the beta. On the “stable” release.

 

[Wando64]

...Yes “its a beta” - but its the second beta, of the third major release, of the 19th OS cycle - of a 4 trillion dollar company.

You reckon all home screen icons disappearing is of a beta standard given all that? If so, I reckon you need to swallow a tough pill and realise Apple is not always justified and right - they are dropping standard, maybe youre in too deep to notice👀🤗

I don't know what is your field of expertise, but I can tell it is not software development.
You are correct in saying that "Apple is not always justified and right", but neither are you.

 

[martint235]

I think I’m the luckiest person alive. I’ve been running betas on all my devices for years and haven’t come across a single problem that has been significant enough for me to report.

 

[yanksfan114]

LOL cmon Apple… this has to be a joke.

26.2 beta 2 on 16ProMax

Is Apple Quality Control even in the room with us anymore?

Reminder: this is a 4 Trillion dollar company.. their budget for QC is $WhatEverTheyWant

And yes - it’s a beta (mistakes happen), but these ‘mistakes’ are happening a lot more often than I ever remember.

So for now - while this bug has been reported to Apple - we can all laugh at all its glory, and let it serve as a reminder to us all.. that no matter how inexperienced, inattentive, unqualified, or uncaring we may be - we can always apply for a job at Apple QC 🤣

Screenshot and video attached for the shared lols🙏🏼🤭

View attachment 2584266
View attachment 2584267

You must be new to iPhone if you’ve never experienced a bug before. Stuff like this has happened since the OG iPhone OS

 

[Abydos]

as someone who worked in rdt&e for entire career, face it qc is a cost therefore minimize qc (the cfo view), when sales drop due to product quality invest in qc until sales improve -- repeat endlessly

 

[Happy_John]

It's a beta.

 

[Tim Jobs the 2nd]

Letting non-developers use beta versions was a mistake.

Yes, you acknowledged it is a beta but you did so with the wrong conclusion. You called it a mistake. No, it is just a bug. Something common in betas which is pre-release software.

It isn't a QC issue when a beta version of software has a bug.