iOS 10.1 was actually out earlier than 11.1 was, if we talk about frequency. More importantly, 10.2 wasn't really out around Christmas vs. 11.2 being out quite a few weeks before--the difference between the two is 10 days. Hyperbole isn't really needed.
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.
iOS 11.x.x Release Speculation Thread
- Thread starter LoveToMacRumors
- Start date
-
- Tags
- ios 11.3 iphone x update ios
- Sort by reaction score
- Status
When you say unable to use - can you expand on that? I’ve missed a lot lately.
What was the bug what did it do and when did it pop up? Presumably fixed in 11.2
The so called date bug put your iOS device in a reboot loop caused by notifications.
Entirely plausible. I don’t think I have ever seen a Saturday Apple update in the 20+ years that I have used Apple stuff.
This month bug also seems to be an issue under macOS: https://robservatory.com/month-13-is-out-of-bounds/
I have no idea what are the Apple developers smoking.. Oh boy...
I have no idea what are the Apple developers smoking.. Oh boy...
Haha, even if this was Jony (which of course it’s not) I doubt he has a clue what is going in the software department. They wouldn’t want to disturb his delicate genius with negativity.
Probably not until after the new year. A X.3 beta has never dropped before New Years. Always the second or third week of January.
That could be the case, but 11.3 is our earlier than 10.2 was last year. Last year there was also an odd 10.2.1 update that got 4 updates before the first beta of 10.3 in mid January. Either way, I think we’ll be getting something prior to January.
We will likely get 11.2.1 then. We cannot use 11.2 being released on Saturday to gauge anything. It was released earlier than planned. The entire reason it was released was because Apple did not have a choice because of the bug. 11.2.1 is possible before New Years, 11.3 is highly unlikely.
11.3 will confirm whether the home button delay will be fixed once and for all.
[doublepost=1512389264][/doublepost]
[doublepost=1512389264][/doublepost]
We could easily get a new build in 10 days. That's a big difference. Apple already is a couple of builds ahead internally.
I agree with you. We might see iOS 11.2.1 and maybe iOS 11.2.2 pretty soon, as the date bug is only temporarily fixed. A look in the maOS console shows that even updated systems still have this issue. The data bug seems to be a ticking bomb for all OS X based operating system.
This year's software releases have been quite buggy.
Just a side note. We are missing macOS, watchOS and tvOS. No way we are getting .3 betas while those are still not out.
That is a difference, just not nearly as big as was being unnecessarily implied with alternative facts.
And shouldn't the last release of iOS 11 conform whether or not anything will change about the home button, and only in relation to iOS 11, rather than 11.3 specifically and not "once and for all"?
Eh? The ONLY thing that would come out in 2 hours 13 minute from now is watchOS 4.2, macOS 10.13.2, tvOS 11.2 and Apple Pay Cash.
But remember the original "rumored" date was 12/5. Which means we might not get anything today and it all come out tomorrow.. Or the release of 11.2 early will mean the rest will come out early as well.
I would not be suprised if they do not enable Apple Pay Cash today until the date bug is completly solved. I'm hearing that Apple might even temporarily need to disable temporarily Apple Pay. If your phone is affected by the date issue it is unable to complete the transaction as the internal date can not assign date and time to the transaction...
My employer received several hundreds of rejected transactions over the weekend. Typically we had 10 to 15 over the weekend. And the log clearly showed. that it was unable to assign transaction date/transaction time.
But the date bug is solved in 11.2, No? So how would those with the date bug even have APC?
It is not completly solved. If you ran the console on the mac, the iOS devices still show an warning, that month 13 is out of bounds. As I've written before, it is a ticking bomb to explode again....
I wonder how that month 13 relates to this and why it started playing a role for some on December 2nd.
My guess: As soon as November ended (globally) the out of bounds caused the problem. It could be similar to the Y2K bug back in 1999/2000. Don't forget Apple started transforming the old Objective-C code into SWIFT. Now, we are seeing the consequences (e.g. calculator bug, date bug)
I think, nobody saw that bug. It just worked. The surprise came Friday.
- Status