Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Who knows what else will get broken/hobbled in this release, even if a new RC version is released as official to public. Will wait until the official public version is fully vetted. If it goes away because Apple wants to force 16, then let 15.7 be my final version.
 
  • Like
Reactions: Glideslope
"Release Candidates" ain't what they used to be.
actually, this is exactly what they are.

They are a candidate for release, not THE release. If show stopper bugs are found, like this, then it is no longer a candidate for release and will be superceded. This happened with the new Mac OS candidate, and a new build was released yesterday.
 
actually, this is exactly what they are.

They are a candidate for release, not THE release. If show stopper bugs are found, like this, then it is no longer a candidate for release and will be superceded. This happened with the new Mac OS candidate, and a new build was released yesterday.
Ideally you declare the release candidate from the latest beta that doesn't have high level bug like this.
Does this mean that they inserted a fix between the latest beta and the RC, or did they overlook this bug?
 
Now more than ever.

1666345808909.png
 
Ideally you declare the release candidate from the latest beta that doesn't have high level bug like this.
Does this mean that they inserted a fix between the latest beta and the RC, or did they overlook this bug?
Regressions - sometimes fixing one bug can cause another !
 
Ideally you declare the release candidate from the latest beta that doesn't have high level bug like this.
Does this mean that they inserted a fix between the latest beta and the RC, or did they overlook this bug?

Well, "ideally", bugs wouldn't exist.

It can be either of those. The development cycle of 15.7.1 was presumably short, so maybe they didn't notice the issue all along. Alternatively, they did something to fix an entirely different bug, and that caused a regression.
 
Apple need to be less blatant in telling people to buy new iphones. I mean come on, FaceID is an essential basic security feature. Why does it break in an x.7.1 release when it was fine in the previous versions?
It’s still in beta. Release candidate not available to general public.
It’s obviously a bug and should be fixed before general release.

This isn’t apple blatantly telling people to upgrade.
 


...Some users are not interested in updating to iOS 16...

I really don't understand these people that avoid updates. And it's ironic that someone is really scared of 'bugs' so they avoid upgrading to iOS 16, only to have a bug "potentially" released to iOS 15.

Also, these comments and some of the outrage seems pretty dumb. It's pre-release software. lol. A major bug in pre-release software that will obviously get fixed before it's officially released? Oh my!!!
 
Last edited:
Well 16 broke Siri. I can’t even tell my gps where to take me now

I have had zero issues with iOS 16 with Siri in my car giving her gps destinations. In fact, I have had zero issues with anything related to the update. 🤷‍♂️
 
  • Like
Reactions: inkswamp
It’s still in beta. Release candidate not available to general public.
It’s obviously a bug and should be fixed before general release.

This isn’t apple blatantly telling people to upgrade.
1. It's a joke.
3. RC is really close to GM and most often are the same. One should ask why such fundamental breaking bug even managed to get into RC release.
3. It should be fixed. But will Apple just release a 15.7.2 as the fix? Seems like if it's already RC, it means the release date timing is already close, so Apple might as well just release 15.7.2 as the fix.
 
"Nudging" customers to iOS 16 by "accidentally" breaking FaceID in iOS 15.

You think a company like Apple wants to tarnish their own image just to get a few people to upgrade? Or risk those same people just switching to Android? Doubtful.

We're so privileged nowadays that we take this stuff for granted. I don't think most people appreciate just how complex an endeavor it is to produce large-scale consumer software. Bugs and glitches get by despite everyone's best efforts, especially in betas. I don't understand the cynicism. Does it make you feel clever?
 
"Nudging" customers to iOS 16 by "accidentally" breaking FaceID in iOS 15.
Problem runs much deeper. Once some internal flag is set to signal "Face ID unavailable", there is no simple way to restore the function. Updates or downgrades (as long as still possible) do not solve the issue.
I once had a perfectly working iPhone X and obstructed the Face ID sensor by misaligned screen protector. Experimented a bit with resetting Face ID and re-teaching in. It ended up in deactivated locked Face ID that could not be restored even after removal of the screen protector. No visible damage on Tx/Sensor, no scratches whatsoever remained. Apple support remote-tested and diagnosed the iPhone and came to conclude "nothing wrong, sensor should work". Which it never did again, not even after wiping iPhone and fresh iOS install.

Could it be that Apple has minimal motivation in fixing this deadlock? Will be interesting to see what will happen to those 15.7.1 beta victims iPhones...
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.