Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Actually, it's more like an alpha. Beta releases should already be tested well enough that they don't brick significant numbers of devices. Unless you are 2024 Apple and growing sloppier.

Looks like alpha not beta. Some time ago this also was with android 14 or 13. But sadly apple in last years went downhill in software development.

No. It’s not because there’s a (major) bug in a software version it should be labeled alpha instead of beta. That has nothing to do with it.

Also, there’s no data backing up the claim that Apple has more incidents like this compared to their earlier years.

Apple used to be way more strict about who could run their test versions. Now, everybody can and apparently everybody is. Because 17.3 brings so many amazing new features you have to have now?
 
  • Love
Reactions: KeithBN
Had a bootloop with iOS 17.2.1 too. After the initial update to 17.2.1 everything worked fine until I turned off the phone. After turning it on again it went in a permanent bootloop; had to erase and do a restore from iCloud.
 
Now that we got this out of the way we won't have to worry about something like this happening for the rest of the year.

:)

Shouldn't these graphics really be "17.3b"?
Considering 17.3 is not out and only in beta that’d be redundant and really it’s not necessary.
 
  • Like
Reactions: KeithBN
Wonder if Microsoft's "The Customers are Our QA Department (Since We Laid Them All Off)" development program would have caught it?

Another reason I don't update automatically when given a choice, but read the news often enough not to be caught out.
 
I'm actually glad they found an issue with backboardd and the Back Tap Launcher. Whether they introduced the bug on accident or changed something else that caused an issue, they found it and pulled it within a few hours or so. This is good.
 
Please share your prompt!

I don’t remember exactly but basically “make me a cereal called Apple boot loops in the style of Froot Loops.” I tried to refine it but it got worse every time. I find the first try is usually its best, it just gets weirder after that.

Once I asked it to put Tim Cook’s face on the box. That was…creepy.
 
  • Haha
Reactions: Amazing Iceman
It's a developer beta, not even a public beta (which also is a risk to run anyway). It is not intended for production devices for a reason. Just because some members of the public don't understand what a beta is, doesn't mean Apple is labeling it wrong.

Exactly this. While I was lucky not to have an issue (install went fine), I know the risks of running a beta on my main device. With that said, I have been doing it for the last 6-7 years without any major flaws.
 
Living in the edge. Performed the update and it went ok.

Sorry for those who have problems though.

Watch and AppleTV are also good to go.
 
  • Like
Reactions: JFLECHUGA
Something is off at Apple. Between the Apple Watch being banned (albeit temporarily) to having to pull beta releases, there seems to be something missing in their development and testing programs. Perhaps placing secrecy above all else wasn't such a great idea?
Last I heard they rotate people from project to project like a merry-go-round. There is no consistent strategy, except what will make money this month.
 
  • Like
Reactions: gank41
This kind of testing is literally part of QC. It was not publicly released.
Was just the developer Beta affected or also the public beta?
Making sure participant‘s devices aren’t bricked/the software can’t disable a phone is part of QC and that obviously didn’t happen before it was released, otherwise it wouldn’t have been pulled. Public beta testing is done for the large feedback pool, not to edge out bricking scenarios.
 
I’ve tried to use it, but I find it either triggered too easily or not easily enough. Never seems to be just right.
Couldn't remember if I had it on but did a search under settings and guess what - it doesn't show up. I did find it but I guess somewhat of a bug that it doesn't show up when you search settings....
 
Last edited:
  • Like
Reactions: CarAnalogy
Was just the developer Beta affected or also the public beta?
Making sure participant‘s devices aren’t bricked/the software can’t disable a phone is part of QC and that obviously didn’t happen before it was released, otherwise it wouldn’t have been pulled. Public beta testing is done for the large feedback pool, not to edge out bricking scenarios.
This was only the developer beta.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.