All Devices iOS 13 Speculation Thread [Merged]

[gwhizkids]

13.1 will be the release version. Bank it.
[doublepost=1567616567][/doublepost]@Banglazed This one catch you by surprise? Thank you in advance for the thread you will create!

 

[TheSkywalker77]

Okay about 5 people have said the source is 9to5 we can stop repeating eachother now.

 

[mt247]

Ipad is already updating

 

[Chacocliff]

OTA out now.

 

[TheSkywalker77]

OTA out now.

Still not seeing it on my 7 plus.

 

[mt247]

Iphone could not find anything yet...

 

[chrisdazzo]

It has reached the dev portal.

Build 17A5831c.
Prev. 17A5821e.

 

[Chacocliff]

OTA

 

[d5aqoëp]

It’s live !!!

 

[Ansath]

3.1 is ahead of 3.0 in builds - and progress. Yes, the event was in June but they won’t show new features (which will be in the software) until next week. Otherwise we would all know everything that’s coming. As I said, let’s see next week.

It was on the last release. We don’t know the GM build number yet. 13.0 or 13.1 is not what I mean, build number like: 17A5572a and 17A5821e. For all we know, 13.0 GM could be 17A5822e. Or they pull the 13.1 beta from being available and put up 13.0 GM for the cats on 13.0 dev beta 8/public beta 7. (This being the more likely option)

Do you know that to be true? Otherwise it’s anecdotal.

From my perspective, 13.1b1 is substantially similar to 13.0b8. The only significant issue is the Share Sheet.

This thing is ready for prime time.

Nah 13.1 b1 has more issues then I had in 13.0 db8. Will see how B2 is.

Sure, that’s definitely behind 13.1, but that doesn’t have much to do implying that 13.1 will be what gets released as the first public version of iOS 13.

Exactly. If it’s a day 1 new device update, it has ALWAYS been a x.0.1 release. New features/re-added features have always been a month or more later.

If you follow their logic then we’re getting 2-3 betas for 13.1 for them re-adding features that broke iOS 13.0 enough that they were removed early on and not added back in any of the later 13.0 betas...... it’s worth noting that only 1 out of 12 x.1 betas, only 1 had 2 betas, the rest were 5 or more, and 8.1 was only 2 betas due to Apple Pay not being fully signed off in time due to bank systems.

I think for that we are (or at least I am) relying on the unprecedented step by Apple of releasing a beta version of a point release before the major release has been issued and inferring further from the precarious position Apple finds itself in with its largest revenue source potentially being subject to tariffs that were not a factor in earlier years. I’m sure you’ve read/seen the rest of that theory, so I won’t fully rehearse it here.

13.1 is a software update and not affected by tariffs. iOS 13.0 was stated as barely crossing the line in time for release, meaning that it was always going to be the last beta leading to GM being installed on the new devices before shipping, therefore again the tariffs thing is a misdirect.

That‘d be the case if they didn‘t forcefully „upgrade“ everyone to 13.1 with the beta profile without giving a GM (has never happened before) so people can get off the ride. Like there has never been a single release where a point release was issued before an official GM so testers can get off the beta ride before the new phones hit.

That‘s why I believe in the tariffs theory and that 13.1 is fast tracked for public release instead of 13.0.

They weren’t forced, a lot chose to stay on Beta 8. Also, they never tell us when the last beta is, so you can hop off the beta train any time.

 

[dannyyankou]

This isn't your ordinary .X release. Apple wants to rush this out and have it ready as quickly as possible after 13.0 is released.

 

[TimFL1]

It was on the last release. We don’t know the GM build number yet. 13.0 or 13.1 is not what I mean, build number like: 17A5572a and 17A5821e. For all we know, 13.0 GM could be 17A5822e. Or they pull the 13.1 beta from being available and put up 13.0 GM for the cats on 13.0 dev beta 8/public beta 7. (This being the more likely option)



Nah 13.1 b1 has more issues then I had in 13.0 db8. Will see how B2 is.



Exactly. If it’s a day 1 new device update, it has ALWAYS been a x.0.1 release. New features/re-added features have always been a month or more later.

If you follow their logic then we’re getting 2-3 betas for 13.1 for them re-adding features that broke iOS 13.0 enough that they were removed early on and not added back in any of the later 13.0 betas...... it’s worth noting that only 1 out of 12 x.1 betas, only 1 had 2 betas, the rest were 5 or more, and 8.1 was only 2 betas due to Apple Pay not being fully signed off in time due to bank systems.



13.1 is a software update and not affected by tariffs. iOS 13.0 was stated as barely crossing the line in time for release, meaning that it was always going to be the last beta leading to GM being installed on the new devices before shipping, therefore again the tariffs thing is a misdirect.



They weren’t forced, a lot chose to stay on Beta 8. Also, they never tell us when the last beta is, so you can hop off the beta train any time.

I am still on B8, you are right about that. The thing is this has never happened before so it‘s highly sketchy. 13.0 is a goner and 13.1 is bae now.

 

[gwhizkids]

It was on the last release. We don’t know the GM build number yet. 13.0 or 13.1 is not what I mean, build number like: 17A5572a and 17A5821e. For all we know, 13.0 GM could be 17A5822e. Or they pull the 13.1 beta from being available and put up 13.0 GM for the cats on 13.0 dev beta 8/public beta 7. (This being the more likely option)



Nah 13.1 b1 has more issues then I had in 13.0 db8. Will see how B2 is.



Exactly. If it’s a day 1 new device update, it has ALWAYS been a x.0.1 release. New features/re-added features have always been a month or more later.

If you follow their logic then we’re getting 2-3 betas for 13.1 for them re-adding features that broke iOS 13.0 enough that they were removed early on and not added back in any of the later 13.0 betas...... it’s worth noting that only 1 out of 12 x.1 betas, only 1 had 2 betas, the rest were 5 or more, and 8.1 was only 2 betas due to Apple Pay not being fully signed off in time due to bank systems.



13.1 is a software update and not affected by tariffs. iOS 13.0 was stated as barely crossing the line in time for release, meaning that it was always going to be the last beta leading to GM being installed on the new devices before shipping, therefore again the tariffs thing is a misdirect.



They weren’t forced, a lot chose to stay on Beta 8. Also, they never tell us when the last beta is, so you can hop off the beta train any time.

You miss the point on the tariffs: its not the software but the phones its installed on and when they needed to be manufactured. Sure, we know now that the phones are not subject to the September 1 tariff increases, but Apple could not be sure of that in mid-July when the decision was likely made.

You continue to look at the past and think it will always predict the future: it will not. We are in uncharted waters here and the appearance of Beta 2 today is further evidence that 13.1 will be the release version, not 13.0.

 

[MrGimper]

No, other one says today

Cat wins!

 

[mt247]

IpadOS Update already completed, waiting for the iPhone Update to arrivie ota

 

[Ansath]

This isn't your ordinary .X release. Apple wants to rush this out and have it ready as quickly as possible after 13.0 is released.

Which is why I think it’s going to be end of September/Early October. There’s no real reason to rush 13.1 as it’s not like it’s bringing any features like Apple Pay in 8.1.

You miss the point on the tariffs: its not the software but the phones its installed on and when they needed to be manufactured. Sure, we know now that the phones are not subject to the September 1 tariff increases, but Apple could not be sure of that in mid-July when the decision was likely made.

You continue to look at the past and think it will always predict the future: it will not. We are in uncharted waters here and the appearance of Beta 2 today is further evidence that 13.1 will be the release version, not 13.0.

If you’re right about the tariffs being the reason, we would have seen 13.1 earlier, as previous said, iOS 13.0 barely crossed the line for release, and that’s based on all the previous years. Crossing the line means being signed off internally at Apple for installation on those new phones being shipped.

Even so, if they rushed the release for the phones and they needed a Day 1 update, it would be 13.0.1, not 13.1.

The past always informs the future. Also, common sense when it comes to software development trumps that, and you would be nuts limit yourself to 2-3 betas to rush 13.1 out on the 20th, that’s just illogical.

 

[TimFL1]

Which is why I think it’s going to be end of September/Early October. There’s no real reason to rush 13.1 as it’s not like it’s bringing any features like Apple Pay in 8.1.



If you’re right about the tariffs being the reason, we would have seen 13.1 earlier, as previous said, iOS 13.0 barely crossed the line for release, and that’s based on all the previous years. Crossing the line means being signed off internally at Apple for installation on those new phones being shipped.

Even so, if they rushed the release for the phones and they needed a Day 1 update, it would be 13.0.1, not 13.1.

The past always informs the future. Also, common sense when it comes to software development trumps that, and you would be nuts limit yourself to 2-3 betas to rush 13.1 out on the 20th, that’s just illogical.

Can we drop the „but 13.0.1?“ already? When you introduce major features or breaking changes, you do a point release. You don‘t change/bend the rules of semantic versioning, it‘s like gravity... a force itself.

 

[Ansath]

Can we drop the „but 13.0.1?“ already? When you introduce major features or breaking changes, you do a point release. You don‘t change/bend the rules of semantic versioning, it‘s like gravity... a force itself.

To take a page out of your book then.... Can we drop the 'but early betas & tariffs mean 13.1 is gonna be on the new shiny phones and no-one will ever see 13.0 GM or publicly', since you cannot change/bend the rules of developing software, it's like gravity... a force itself.

You're making the assumption that 13.1 is being released on Day 1, but if it's actually coming 2-3 weeks later (which is a 6-8 weeks earlier than normal for a x.1 release with any new features), then this is perfectly logical, if not a break for the norm.

 

[TimFL1]

To take a page out of your book then.... Can we drop the 'but early betas & tariffs mean 13.1 is gonna be on the new shiny phones and no-one will ever see 13.0 GM or publicly', since you cannot change/bend the rules of developing software, it's like gravity... a force itself.

We can if you post a single reason why it‘s unlikely?

 

[C DM]

Can we drop the „but 13.0.1?“ already? When you introduce major features or breaking changes, you do a point release. You don‘t change/bend the rules of semantic versioning, it‘s like gravity... a force itself.

Seems like part of the point there is that they don't need to have those new features in a 13.0 release given that they weren't part of it.

 

[Ansath]

We can if you post a single reason why it‘s unlikely?

I have, but you choose to be ignorant of the reasons I've given.....

 

[gwhizkids]

Which is why I think it’s going to be end of September/Early October. There’s no real reason to rush 13.1 as it’s not like it’s bringing any features like Apple Pay in 8.1.



If you’re right about the tariffs being the reason, we would have seen 13.1 earlier, as previous said, iOS 13.0 barely crossed the line for release, and that’s based on all the previous years. Crossing the line means being signed off internally at Apple for installation on those new phones being shipped.

Even so, if they rushed the release for the phones and they needed a Day 1 update, it would be 13.0.1, not 13.1.

The past always informs the future. Also, common sense when it comes to software development trumps that, and you would be nuts limit yourself to 2-3 betas to rush 13.1 out on the 20th, that’s just illogical.

Regarding seeing 13.1 earlier, I don't think so. Let's assume for the sake of argument that the team at Apple decided about 15 July that they were going to accelerate phone production to avoid any potential tariffs. At that point, we were at beta 4, I believe. But Apple internally was much further along. They gave themselves a cutoff date of, say, August 20 to have a "13.0" ready for the phones being produced but with a feature freeze. If your feature wasn't going to be ready for that cutoff (think Automation), it got the ax from 13.0 but got moved to 13.1. But they also wanted to keep pushing development of the overall 13 tree. so they kept moving forward on that separate path.

Again, you are making the assumption that 13.1 is a true "dot 1" update and not just a naming convention to denote development of 13.0 past the new phone software flash date (which is my operating assumption). The past informs the future, but if anything, Apple has taught us that it doesn't constrain the future. They have changed so many things about how they deliver these betas over the past 2 years that there is no way you can use their past practices to predict what they will do in this regard in the future.

 

[TimFL1]

Regarding seeing 13.1 earlier, I don't think so. Let's assume for the sake of argument that the team at Apple decided about 15 July that they were going to accelerate phone production to avoid any potential tariffs. At that point, we were at beta 4, I believe. But Apple internally was much further along. They gave themselves a cutoff date of, say, August 20 to have a "13.0" ready for the phones being produced but with a feature freeze. If your feature wasn't going to be ready for that cutoff (think Automation), it got the ax from 13.0 but got moved to 13.1. But they also wanted to keep pushing development of the overall 13 tree. so they kept moving forward on that separate path.

Again, you are making the assumption that 13.1 is a true "dot 1" update and not just a naming convention to denote development of 13.0 past the new phone software flash date (which is my operating assumption). The past informs the future, but if anything, Apple has taught us that it doesn't constrain the future. They have changed so many things about how they deliver these betas over the past 2 years that there is no way you can use their past practices to predict what they will do in this regard in the future.

This. Apple can‘t predict the future either, they had to deal with the intel they were given months ago. What happened months ago? Orange man having a new favorite word called „tariffs“. So they could either roll on and ignore that, potentially being hit by surprise tariffs cause why not, or accelerate everything to completely evade nasty surprises and not lose money.

 

[mt247]

has iOS arrived on a non iPad already?

 

[Ansath]

Regarding seeing 13.1 earlier, I don't think so. Let's assume for the sake of argument that the team at Apple decided about 15 July that they were going to accelerate phone production to avoid any potential tariffs. At that point, we were at beta 4, I believe. But Apple internally was much further along. They gave themselves a cutoff date of, say, August 20 to have a "13.0" ready for the phones being produced but with a feature freeze. If your feature wasn't going to be ready for that cutoff (think Automation), it got the ax from 13.0 but got moved to 13.1. But they also wanted to keep pushing development of the overall 13 tree. so they kept moving forward on that separate path.

Again, you are making the assumption that 13.1 is a true "dot 1" update and not just a naming convention to denote development of 13.0 past the new phone software flash date (which is my operating assumption). The past informs the future, but if anything, Apple has taught us that it doesn't constrain the future. They have changed so many things about how they deliver these betas over the past 2 years that there is no way you can use their past practices to predict what they will do in this regard in the future.

So, the new phones are due to be released on September 20th, Apple start bundling the internal GM release onto those devices starting a month beforehand. So your cutoff date is actually the usual cutoff date, which is why Beta 8 was last beta and will be the GM.


If you're right about the tariffs, then they would have done it MUCH earlier.

The 2 features re-introduced, are not significant enough to warrant a rush release of 13.1 for the day of the phone release. So go on, tell my why those features are so significant enough that they've rushed a 13.1 release, rather than leave it til later, and done a 13.0.1 day 1 please if there were any bugs missed due to rushed shipping for tariffs?? A x.1 release tends to be over a month after a x.0 release, but it could be that due to rumoured new Watches, or something they will announce at the event, but not released the same day as the new phones, that they're wanting that x.1 release earlier than normal, possibly the end of September, or early October. This is much more likely than your Tariffs goes.

Also, you keep missing out the point that it makes no real sense that they would rush a x.1 beta to release in a less than 4 week period for Developers to test their apps, as some are massively broken in 13.1 b1 and already seeing them not being resolved in b2. Adobe Creative Cloud & Fitbit still seem broken and that's a big one to have broken still.