I am with you on that, Dan. But I love to speculate based on what I see!I have no idea what's happening
I am with you on that, Dan. But I love to speculate based on what I see!I have no idea what's happening
That it seems to be: https://mobile.twitter.com/AppleBeta2019/status/1169314121218703360@JPack submitted this to MacRumors, but MacRumors wouldn't bite. I guess they think it's bogus.
And the iOS 13.1 Public beta 2 is out...
Well to each his own. No one can say you’re wrong, nor can you say for sure you’re right. Time will tell
Actually I didn’t, just saying time will tell, we all have our opinions on what will happenDid you miss the part where I said "My guess"? Sorta implies I don't know.
Actually I didn’t, just saying time will tell, we all have our opinions on what will happen
It's more logical that it's going to be for the new (rumoured) watches & (definitely more than rumoured) Apple TVs, which will come after the phones
Far better state in what sense? Seems like the last 13.0 beta has been quite stable for most.Why is that “more logical”? There isn’t even a 13.1 beta for ATV. I think the new phones are shipping with 13.0 but 13.1 will be released pretty quickly, maybe before the end of September. It’s already very polished and in a far better state that 13.0.
Mail is behaving properly, everything is super snappy and polished. Personally I haven’t encountered a single bug in 13.1 except the share sheet, which is fixed in beta 2.Far better state in what sense? Seems like the last 13.0 beta has been quite stable for most.
That's good to hear. At the same time it seems there are some others who are seeing various things here and there. Which is somewhat similar to 13.0 where many with the latest beta haven't really been running into issues, while some others have been.Mail is behaving properly, everything is super snappy and polished. Personally I haven’t encountered a single bug in 13.1 except the share sheet, which is fixed in beta 2.
Mail is behaving properly, everything is super snappy and polished. Personally I haven’t encountered a single bug in 13.1 except the share sheet, which is fixed in beta 2.
There’s about 5 issues on the dev notes, more being reported in the bugs thread.
The ability to share iCloud folders is still broken. Also the bug with AirPods taking over the sound even though they’re connected to the iPhone is back too. Such a pain.
So it’s not as smooth as 13.0 db8.
On my iPhone XS, 13.1 Beta 2 is infinitely better than 13.0 Beta 8.
Like, night and day different. Beta 8 was terrible for me. Truly a wreck.
That and the fact that PB was released on a "1st" beta.Not a typical x.1 beta since still weekly, leads to more proof that 13.1 might be the GM.
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.
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.
I think you may be missing the point that this is not a rushed release but more of an equivalent of 10 betas now. Note the build numbers of 13.0 and 13.1. They are the same series 17Axxx not your always B or C or whatever that comes with each new x.X release. I believe that is where the big disagreement is. If 13.1 were a 17Bxxx build, then yeah it would be more like a real beta 1 or 2. But since its the same series as 13.0 (17Axxx) then more like beta 10. Also having a public beta release on a dev beta 1 and same day public beta release on a beta 2 would be pretty uncommon on a x.X release if it were in fact an entirely new version. As you guys keep saying...... its all speculation and we will just have to wait and see what Apple has in store for us but at this point its looking more like 13.1 will be the release.......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.
That and the fact that PB was released on a "1st" beta.
I think you may be missing the point that this is not a rushed release but more of an equivalent of 10 betas now. Note the build numbers of 13.0 and 13.1. They are the same series 17Axxx not your always B or C or whatever that comes with each new x.X release. I believe that is where the big disagreement is. If 13.1 were a 17Bxxx build, then yeah it would be more like a real beta 1 or 2. But since its the same series as 13.0 (17Axxx) then more like beta 10. Also having a public beta release on a dev beta 1 and same day public beta release on a beta 2 would be pretty uncommon on a x.X release if it were in fact an entirely new version. As you guys keep saying...... its all speculation and we will just have to wait and see what Apple has in store for us but at this point its looking more like 13.1 will be the release.
Trying to recall exactly, but isn’t that not that unusual for non x.0 releases?That and the fact that PB was released on a "1st" beta.
That and the fact that PB was released on a "1st" beta.
I think you may be missing the point that this is not a rushed release but more of an equivalent of 10 betas now. Note the build numbers of 13.0 and 13.1. They are the same series 17Axxx not your always B or C or whatever that comes with each new x.X release. I believe that is where the big disagreement is. If 13.1 were a 17Bxxx build, then yeah it would be more like a real beta 1 or 2. But since its the same series as 13.0 (17Axxx) then more like beta 10. Also having a public beta release on a dev beta 1 and same day public beta release on a beta 2 would be pretty uncommon on a x.X release if it were in fact an entirely new version. As you guys keep saying...... its all speculation and we will just have to wait and see what Apple has in store for us but at this point its looking more like 13.1 will be the release.
Makes a lot of sense, especially if you buy into Apple sending the phones early to avoid what they thought would be 1 Sept tariffs. That’s only about 3 weeks early so I think it is possible. Would have been a smart move IMO.
And they could easily have added a check for latest version step in whatever they shipped and upload 13.1 as part of the setup.
I guess when we start the annual track your cell phone event, if we find they are already out of China, we will know if we don’t find out on the 10th
Trying to recall exactly, but isn’t that not that unusual for non x.0 releases?
No idea. Don‘t bank on it or quote me on it cause setting up as new is incredibly annoying.Well bollocks. Setting up as new is the way out of this then?
They have a patent for that though (don‘t think it‘s more than a patent though). Some kind of ultra low power mode with a fuse that gets blown after the device got activated to download a new build. Can‘t find that article anymore though, would love to read it again cause I think it‘s something worth to push R&D money into if possible.
Fairly sure it’s already part of the process. Apple would certainly like the update to already be on the device so that the user experience of waiting for an update to install right when you are opening the device wouldn’t be much of an issue.I guess I don’t understand why they would have to update in the box. Couldn’t they have just added a check for updates step as part of the setup progress. Then when phone is first powered on and set up it checks and updates itself to latest version.
Yes I can see that but if they haven’t perfected the in box upgrade it would be the best choice.Fairly sure it’s already part of the process. Apple would certainly like the update to already be on the device so that the user experience of waiting for an update to install right when you are opening the device wouldn’t be much of an issue.