What on Earth is happening at Apple QC? LAUGHABLE BUG

[WilliamG]

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👀🤗

This bug is also most certainly present on 26.1 official release, too. Happened to me several times, not to mention friends.

 

[Allen_Wentz]

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

Yes, X.1 releases like 26.1 public release are in reality beta, which means Apple is using the non-beta community for beta testing, which totally sucks. It is not ethical behavior by Apple. IMO X.1 versions like 26.1 should stay in beta until they are very solid, which has not been the case, for years.

 

[soundslikeaudio]

For everyone posting “but it’s a beta!!!” the release candidate is out, and I’m about to DFU mode restore an iPhone 15 Pro Max and set it up as new, without syncing. Let’s see how long it takes before this very visible bug rears its ugly head again.

Granted, a release candidate is NOT always the release, so I will repeat the experiment should a newer build get released before general availability.

But the point here is NOT that a bug is present in a beta; it’s that a bug present since 26.0 beta 1 is STILL present on the latest version of the OS, including the release versions.

 

[Abydos]

I was looking at some notes from 45 years ago: "a bug is an undocumented feature" , apparently apple merely needed to document these "bugs" then they disappear

 

[soundslikeaudio]

I was looking at some notes from 45 years ago: "a bug is an undocumented feature" , apparently apple merely needed to document these "bugs" then they disappear

Hahahaha, I feel like that’s how Avid at times approaches Pro Tools development, “ehhh add it to known issues, then we can ignore it for a few years”.

 

[theheadguy]

The release is still a beta.

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.

1. It’s a beta, expect bugs

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

It's unfortunate that the bar is so low for some. The point of this post is that this problem (which is already reported by many on Reddit) should not have made it past their final internal alpha release. Expect better.

 

[Mr_Brightside_@]

Really? 😧 I thought the 'Beta' under Developer Betas that I downloaded was a joke?! 😂

On a serious note, have a scour through the forums - the stable releases have mountains of bugs. There's forum members who have bugs from iOS17..

From my point of view - Apple doesnt seem to listen to beta feedback - leaves reports sitting there (I'll check my dev account, I am pretty sure some of my reports are from 2018 or even earlier - still unseen😅), and Apple still has the audacity to pre-install the feedback app on all beta software.

Why even pretend anymore? 😅

Given how uninvolved Apple is in attending to actual reports (some of them take a bit to write up/capture) - we might as well treat the Betas as a cute-half finished peek into the next version - with absolutely no intention of providing feedback.

Thats my 2 cents - open to different thoughts✌️🙂

My thoughts: you're running beta software and posted a thread with a ragebait title

 

[soundslikeaudio]

It's unfortunate that the bar is so low for some. The point of this post is that this problem (which is already reported by many on Reddit) should not have made it past their final internal alpha release. Expect better.

Not only that, but many of us have reported it via the official reporting mechanism, as is the point of the beta process. There’s no way that they’re unaware of it.

But your point very much stands; in a major update that is focused on a visual overhaul, something like “the home screen not rendering icons and/or having to re-render them each time you exit an app and/or the color of the app either doesn’t match the settings or changes depending on if you’re viewing the app from an opened folder vs the smaller preview” is some seriously 101 stuff.

 

[paulvee]

I 100% agree, and would encourage Apple to implement both the options simultaneously. We just need a solid, reliable OS after all these years

We have a solid, reliable OS after all these years, and I have used every Apple OS since 1995. I do a lot of work all day and can't afford to beta test.

 

[leifp]

Great news! Happened to me on iPadOS 26.1 even if only briefly

 

[-BigMac-]

My thoughts: you're running beta software and posted a thread with a ragebait title

What's rage bait about the title?

My genuine concern about Apple QC (I think many MR members are at least a little concerned about this judging by the hordes of forums on the topic).. Or is it that the bug is laughable?

If you think the worlds foremost Mobile OS company, having a huge bug where ALL the home screen icons completely disappear (something which has been reported, and is present throughout the subsequent NINETEEN versions):
- 26.0 beta 1, beta 2, beta 3, beta 4, beta 5, beta 6, beta 7, beta 8, beta 9, RC, Stable;
- 26.1 beta 1, beta 2, beta 3, beta 4, RC, Stable;
- 26.2 beta 1, beta 2, beta 3;
is anything but laughable (and disappointing) - then it seems we share different opinions on expectations of quality, and the purpose of bug reports.

I personally think 'laughable' and 'sad' are the only genuine responses to the matter - don't forget we (Apple users) ALL pay for this software. The software is a large part of what Apple brings to the table. Since these bugs are present in stable releases - doesn't that affect our reasonable expectations of quality?

In Australia for example, we have strong Consumer Rights protecting 'reasonable quality' of goods and services which are enforceable. If the software or hardware doesnt operate up to the standard as described, or is unreliable enough - then there is merit for refund or compensation of the whole phone. Some of these releases are really treading a fine line

 

[-BigMac-]

We have a solid, reliable OS after all these years, and I have used every Apple OS since 1995. I do a lot of work all day and can't afford to beta test.

haha are we running the same OS? 😬

This thread is based on a bug which has been reported, and present throughout 19 subsequent iOS versions - including 3 Production releases - 26.0 final, 26.1 final and 26.2 final

 

[MBAir2010]

Seems to me the "QC" a forgotten aspect in manufacturing is gone.

blame "it's teh betas-dude" is old.

there is no way any reputable or even a linux basement design company would release such failures.
unless these mistakes are another  profit ploy?

these examples of Cupertino's lethargic release are just plain embarrassing.

the weather here is great though!