Sidebar Sidebar
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

Status
Not open for further replies.
sunny2k1 said:
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.
Click to expand...
Is there any way to predict when it could happen again if it's not fixed?
 
sunny2k1 said:
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.
Click to expand...
I wonder what changed in iOS 11.2 to make that issue disappear (at least for now), but not actually addressed for good (if that is actually the case).
 
C DM said:
What timer?
Click to expand...
That month 13 could be a timer of some sort from when a new build is installed. The public releases are far few and between which is why it ran out. Those on the beta release get updates every week which is why they didn’t face the issue as it resets every time a new build is installed.
 
Radon87000 said:
That month 13 could be a timer of some sort from when a new build is installed. The public releases are far few and between which is why it ran out. Those on the beta release get updates every week which is why they didn’t face the issue as it resets every time a new build is installed.
Click to expand...
Not sure how a timer would relate to month 13. Seems like we need at least somewhat more information and details to even have educated guesses.
 
sunny2k1 said:
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.
Click to expand...
It has been released/activated.
 
  • Like
Reactions: jhall8
sunny2k1 said:
My guess they had to react. I do not know what would have happened if iPhone/iPad users were unable to use their device over the weekend (three full days). Luckily it happened on a Friday and not on a Saturday..

In general it was a pretty bad week for Apple and their software quality...
Click to expand...
It was actually Saturday not Friday.

sunny2k1 said:
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.
Click to expand...
The calculator but wasn't a calculation bug, but an animation type issue. So not sure that would be related to your statement. But yeah not only a bad week in Apple software land but a bad few months it seems.
 
Status
Not open for further replies.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back