13.1 beta 3 today. 13.1 GM next Monday. New iPhone's ship with iOS 13 beta 8, but 13.1 available for download right away on 9/20. That's my guess.
Last edited:
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
All Devices iOS 13 Speculation Thread [Merged]
- Thread starter Ebok
- Start date
- Sort by reaction score
Something final is coming tomorrow (13 or 13.1). Or there are going to be a lot of upset developers. And by “final” I mean a Golden Master. Those have been known to not be the final, public release but that’s not common.
Last edited:
iOS 13.1 is no where near final, another few betas, it will be out October time
My guess:
2019-09-10: iOS 13.0 GM release (at least for developers)
2019-09-12: iOS 13.1 beta 3 release
2019-09-16: iOS 13.0 official release
2019-10-xx: iOS 13.1 official release
2019-09-10: iOS 13.0 GM release (at least for developers)
2019-09-12: iOS 13.1 beta 3 release
2019-09-16: iOS 13.0 official release
2019-10-xx: iOS 13.1 official release
I find it funny that people are claiming 13.1 as “not ready” while believing that something close to 13.0 beta 8 (also a buggy release) will be shipped as GM
Bingo. And everyone saying how "unpolished" either of them are also usually don't provide much detail, or the issue is with their device and not those of (many) others (at least as reported here). Betas can be wonky, but a bug, even a debilitating one like extreme battery drain, is not a showstopper unless it affects more than just a few users.
My own experience is such that I could accept, without reservation, 13.1 as my daily driver. Which is good, because I have!
[doublepost=1568040325][/doublepost]I will add: I hope Apple explains during the keynote tomorrow this whole 13.0/13.1 thing. I think they owe it, at the least, to the developer community (and probably should have issued a statement when 13.1 hit initially).
They're both buggy, but it's still much more likely that 13.0 beta 8 will be the GM.
It's not really about the bugginess, but more about the beta cycle timing.
I predict it won't even get a mention, other than to say iOS 13 will come on xyz date.
That's correct, but the GM is a developer thing. I really think Apple owes it to them to explain why they suddenly veered from one beta to another prior to release of the first. How are developers supposed to know what they are targeting? Yes, I get that 13.0 beta 8 is still on the servers, but that is besides the point. They prominently directed everyone to the new beta without any explanation. If you are working from a profile, that's where you ended up unless you elected not to install the new version.
I've indicated why I think this happened elsewhere. I do think its incumbent upon Apple to give some sort of explanation when they can do so.
Zero chance. And why do you think apple owe it? 99% of iPhone users don’t know this and don’t care
Why would you think the target should be anything other than 13.0 beta 8?
They've clearly labeled the subsequent betas as 13.1, not 13.0.
I am going to challenge you to explain the portion of your post I've bolded. Pretend that the release 2 weeks ago was 13.0b9 rather than 13.1b1 (and that 's not an unreasonable position, given the build nomenclature and general posture of 13.1 vs 13.0). If it were b9 and last week's release was b10, it'd line up precisely.
[doublepost=1568043886][/doublepost]
Users are not the target: developers are.
And a lot of scoop from macrumors or 9to5mac recently was based on an internal build of iOS 13. And i think that’s the build to release tomorrow as the GM
Uh, you are bringing up random hypothetical situations that are irrelevant here. The bottom line is that Apple stopped releasing 13.0 betas and started releasing 13.1 betas. They did not release 13.0b9 so it's pointless to bring that up.
The main aim of the September iPhone events has never been developers.
And I'm not saying they have to use stage time to do this. But they should use the occasion to issue a statement. I would imagine that this sudden veering to a "new" version before releasing the other one has caused some consternation in the developer community. Or not, if the SDK really didn't change, in which event 13.1 will be the release version.
Yeah I’dont know where this come from (13.1 should be seen as b9 , b2 as b10....)
13.1 b1 is 13.1 b1
I am not bringing up hypothetical situations. I am noting that for all practical purposes, Apple continued the iOS 13 development process seamlessly, simply changing the name of the software to 13.1. That has NEVER happened before and is hardly irrelevant.
You missed my point re the target: the target of a communication about 13.1 would be developers. I'm sure 99% of the public could care less.
[doublepost=1568045038][/doublepost]
Except when viewed in light of its unprecedented nature and its space in the continuum of the iOS 13 development process.
No they didn't. 13.1 has an updated feature set.
BTW, in previous years, if you installed the beta profile to get the x.0 betas, if you didn't delete it, you'd seamlessly get the x.1 betas too, etc. The only difference this year is when the first x.1 beta arrived.
Last edited:
And the fact that .0 version has not been released.
I think they went to .1 is because of features they took out early for whatever reason but now are adding back before release
These aren't updated features, they're features that were removed for more work. And, again, releasing a x.1 while the x.0 is still unreleased is unprecedented.