Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
According to Zollotech, he believes the Monday after the Event. I thought there was a year where they released the official IOS on the day of the event. I wish they would do that and just make it a celebration all day long.
Historically, that is how it's been for the past several years... we get the RC after the iPhone event keynote... and the GA version drops the following Monday.

• iPhone Keynote followed by RC drop
• iPhone pre-order the Friday following the iPhone event
• GA release of iOS Monday after iPhone event
• New iPhone released for sale/pickup/delivery the second Friday after the iPhone event.
 
According to Zollotech, he believes the Monday after the Event. I thought there was a year where they released the official IOS on the day of the event. I wish they would do that and just make it a celebration all day long.

That is massively unfair to developers who need to test their updates against the final version. That takes time. As noted above, devs were very unhappy with the best simultaneous release date. Apple won’t make that mistake again.
 
  • Like
Reactions: Jay Bly
Yeah, but beta 8 and the RC might have the same build number, so saying is beta 8 the RC, it could be.
But surely beta 8 contains all the logging code that everyone says screws up performance and battery life.
 
Yeah, but beta 8 and the RC might have the same build number, so saying is beta 8 the RC, it could be.
Could be. But I doubt it considering that in previous years we’ve never seen the last beta of the summer have the same build number as the RC. I’m positive the RC has something in it with evidence of whatever iOS 17 feature the iPhone 15/15 Pro will have.
 
It does. And that’s why the RC will be “different”, even if it has the same build number. All that stuff will be stripped out of the RC.
No professional in the software industry would abandon version control and assign the same build number to two different pieces of software.

Additionally iOS would not detect that an update was available.
 
  • Like
Reactions: kostthem
No professional in the software industry would abandon version control and assign the same build number to two different pieces of software.

Additionally iOS would not detect that an update was available.
When it moves from beta to RC, the build number changes format, though. Goes from 2 digits, a letter then 4 digits & letter, to 2 digits, a letter and then 3 digits - so can be same build, but not same build number as such & how iOS will see it as a new build.
 
I am hoping for an RC sooner than later, ha. Beta 8 has been the worse for me so far for performance and battery life, and the first time my battery health has dropped (100% previously on beta 7, down to 95% now in under a week)
 
I am hoping for an RC sooner than later, ha. Beta 8 has been the worse for me so far for performance and battery life, and the first time my battery health has dropped (100% previously on beta 7, down to 95% now in under a week)

If beta 8 has been the worst for you, I really wouldn’t hold your breath for the RC totally changing everything.

I’d maybe look at doing a restore once the official build is out to help clear up anything over hanging from the beta cycle.
 
It will be curious if any seeding takes place tomorrow, even though we think it is a bit too soon for a RC rather the possibility of a beta 9. The event being a week later along with the 18th as the public release still affords Apple some leeway with iOS 17.0 testing. :cool:
 
  • Like
Reactions: gank41
I am hoping for an RC sooner than later, ha. Beta 8 has been the worse for me so far for performance and battery life, and the first time my battery health has dropped (100% previously on beta 7, down to 95% now in under a week)

Yeah the vast majority of reporting I see has praised beta 8 and my personal experience has been great. I agree that a reset or restore may be in order.

How long have you been OTA updates with backups?

Edit: Quote didn’t work for some reason.
 
Last edited:
Yeah the vast majority of reporting I see has praised beta 8 and my personal experience has been great. I agree that a reset or restore may be in order.

How long have you been OTA updates with backups?

I always restore my device at the end of a beta cycle onto the official build or the RC, same difference.

Has, and always will be, a great spring clean for your device before the next betas come a knocking.
 
I'm still thinking of no more beta and RC next week after the Apple Event.

1693895003231.png
 
But surely beta 8 contains all the logging code that everyone says screws up performance and battery life.

It does. And that’s why the RC will be “different”, even if it has the same build number. All that stuff will be stripped out of the RC.

When it moves from beta to RC, the build number changes format, though. Goes from 2 digits, a letter then 4 digits & letter, to 2 digits, a letter and then 3 digits - so can be same build, but not same build number as such & how iOS will see it as a new build.
If it‘s the same build, you wont get any RC build pushed out. When B8 turns out to be the stable release, update servers push a config down to devices that turns off any beta logging and flags the build as stable removing beta build number parts.

It‘s what happened with 13b8 being RC.

Beta logging is not deleted as a functionality when you go stable, it‘s merely disabled and always exists on your device.
 
If it‘s the same build, you wont get any RC build pushed out. When B8 turns out to be the stable release, update servers push a config down to devices that turns off any beta logging and flags the build as stable removing beta build number parts.

It‘s what happened with 13b8 being RC.

Beta logging is not deleted as a functionality when you go stable, it‘s merely disabled and always exists on your device.
Ahh I forgot about 13b8 being RC. Going senile in my old age. Thanks for reminding us. 😊😊
 
When it moves from beta to RC, the build number changes format, though. Goes from 2 digits, a letter then 4 digits & letter, to 2 digits, a letter and then 3 digits - so can be same build, but not same build number as such & how iOS will see it as a new build.

Yes. I assumed that was common knowledge so I didn’t bother stating that obvious point.
 
It will be curious if any seeding takes place tomorrow, even though we think it is a bit too soon for a RC rather the possibility of a beta 9. The event being a week later along with the 18th as the public release still affords Apple some leeway with iOS 17.0 testing. :cool:

Not going to happen
 
  • Like
Reactions: 17fox and Ansath
If it‘s the same build, you wont get any RC build pushed out. When B8 turns out to be the stable release, update servers push a config down to devices that turns off any beta logging and flags the build as stable removing beta build number parts.

It‘s what happened with 13b8 being RC.

Beta logging is not deleted as a functionality when you go stable, it‘s merely disabled and always exists on your device.

I remember that now. But I don’t expect that here as the iOS 13 issue was likely caused by the need for Apple to complete software development quickly to get on phones ahead of a threatened September 1st tariff increase. So they had to start production early if I recall correctly. I still expect probably a build or 2 bump.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.