Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
Not open for further replies.
Replaced 8+ with 8 yesterday and this morning got updates for iMovie, Pages, Numbers & Clips.

All Apple so could have just been a delay in new phone pinging for latest versions.

Just sharing.
 
Replaced 8+ with 8 yesterday and this morning got updates for iMovie, Pages, Numbers & Clips.

All Apple so could have just been a delay in new phone pinging for latest versions.

Just sharing.
That’s because those apps were probably out of date on your phone when it was built. Had that happen on my mother’s new iPhone 2 days ago.
 
  • Like
Reactions: PBz
I might happen to some devices. It could hit anybody, if Apple isn‘t able to fix the issue prior new Year‘s day resp. January 2nd.



That could be an issue with the App Store on your device. I received app updates almost a week after it was released. At the moment, developers cannot submit any updates to the App Store.

Can you look from which date the app update of the app was?
What's special about Jan. 2nd?
 
Wasn’t the original issue 12/2? So 1/2 enters month 13 again?
Not sure, which I why I was asking basically. Still not quite sure how month 13 connected to it all, why December 2nd was the date, how exactly iOS 11.2 stopped it, why that stoppage is only temporary, and if it does come back why it would be Jan. 2nd in particular.
 
Not sure, which I why I was asking basically. Still not quite sure how month 13 connected to it all, why December 2nd was the date, how exactly iOS 11.2 stopped it, why that stoppage is only temporary, and if it does come back why it would be Jan. 2nd in particular.
I’ve been thinking about this too. I have no idea why 12/2 was the date. But I think the installation of 11.2/11.2.1 pushes it back a month. I have no idea how any of it works. But it’s like a new update pushes the issue back a month. So maybe the date is one month from the day 11.2.1 came out. Who knows.
 
What's special about Jan. 2nd?

Date wise the year/month end on December 31st 11:59:59pm at the date border. On the left side (Australia, NewZealand) it‘s already January 1st 11:59:59pm.

So, on the left side of that border the problem started to spread the problem around the world.

For example, if you fly from North America to Australia you lose two days as you cross the date border. If you fly back you lose no day.

In general, computers, software and technical instruments in general are pretty „dumb“. Back in the days without the internet, you needed to set up the time manually (time zone and time) while installing an operating system. When you changed the internal battery, the time and date needed to re-set up the time in the BIOS.

Now the time is usually set via NTP or it is sent via GSM (resp. the connection to the cellular network).

Apple is working on a fix currently? They weren’t on vacation?

That‘s not unusual if you may run into a huge issue.

Within in developer circles I have access to, the Month 13 bug is compared to Y2K only that this time it can also affect private devices. And they at least have to be prepared if iOS/macOS ran into trouble.
 
Last edited:
  • Like
Reactions: Radon87000
Date wise the year/month end on December 31st 11:59:59pm at the date border. On the left side (Australia, NewZealand) it‘s already January 1st 11:59:59pm.

So, on the left side of that border the problem started to spread the problem around the world.

For example, if you fly from North America to Australia you lose two days as you cross the date border. If you fly back you lose no day.

In general, computers, software and technical instruments in general are pretty „dumb“. Back in the days without the internet, you needed to set up the time manually (time zone and time) while installing an operating system. When you changed the internal battery, the time and date needed to re-set up the time in the BIOS.

Now the time is usually set via NTP or it is sent via GSM (resp. the connection to the cellular network).



That‘s not unusual if you may run into a huge issue.

Within in developer circles I have access to, the Month 13 bug is compared to Y2K only that this time it can also affect private devices. And they at least have to be prepared if iOS/macOS ran into trouble.
Well, that would be the 1st then, not the 2nd.
 
I don"t really understand this whole month 13 stuff but you would think the biggest and most successful company in the world would have already have had this figured out a long time ago .. one would think anyways..
 
I don"t really understand this whole month 13 stuff but you would think the biggest and most successful company in the world would have already have had this figured out a long time ago .. one would think anyways..
No software is bug free and no software will ever be bug free.
 
  • Like
Reactions: PR1985 and sunny2k1
No software is bug free and no software will ever be bug free.
I understand that part, but if this was such a big deal then I would think Apple to be little bit more on top of this.. That's why I'm leaning towards this is mostly hype and wont effect the private user as much as people think ... by no means I know this for a fact i'm just stating as an opinion..
 
  • Like
Reactions: PR1985 and sbailey4
I don"t really understand this whole month 13 stuff but you would think the biggest and most successful company in the world would have already have had this figured out a long time ago .. one would think anyways..
Computer languages are not simple.
[doublepost=1514409978][/doublepost]
I understand that part, but if this was such a big deal then I would think Apple to be little bit more on top of this.. That's why I'm leaning towards this is mostly hype and wont effect the private user as much as people think ... by no means I know this for a fact i'm just stating as an opinion..
You well may be correct. I don't see much panic on Apples end.
 
  • Like
Reactions: Jayderek and Bobout
Well, that would be the 1st then, not the 2nd.

No. At 10:00am UTC on the first of month, you have one time zone on the last days last month at 11:00pm and one time zone at 12:00am the next day. Just google International Date Line...

I understand that part, but if this was such a big deal then I would think Apple to be little bit more on top of this.. That's why I'm leaning towards this is mostly hype and wont effect the private user as much as people think ... by no means I know this for a fact i'm just stating as an opinion..

The date bug was caused by the Month 13 issue. That is proven. The problem here to find a new method. The problem occurred on local (on the device), recurring reminders/appointments.

On the macOS side it really affects the system. Especially old system are affected. It made the system of my wife unusable. It overloads several tasks within the system and can make the system unusable...
 
Last edited:
No. At 10:00am UTC on the first of month, you have one time zone on the last days last month at 11:00pm and one time zone at 12:00am the next day. Just google International Date Line...
Right, so while some are on the 1st some might still be on the 31st/30th (or 29/28th) depending on the month. 2nd doesn't seem to factor into that.
 
So they probably should release something this Thursday or Friday or maybe Saturday (like iOS 11.2)...
If something was to happen, they'd probably try to release something quickly. Hopefully nothing will happen though.
 
Right, so while some are on the 1st some might still be on the 31st/30th (or 29/28th) depending on the month. 2nd doesn't seem to factor into that.
This is how I understood it, The 1st is treated as the previous month and current month simultaneously due to time zones. The 2nd completely turns over the month triggering the issue.
 
I think, I noticed this problem on my AW. I did the last update on release day, I went out the next day and I noticed that the display was black, so I pushed the side button. The Apple and the circle appeared... waiting, waiting until the circle was complete... Reboot... A calendar message appeared from 1980! I saw it and then it disappeared again.
 
Last edited:
I think I noticed this problem on my AW. I did the last update on release day, I went out the next day and I noticed that the display was black, so I pushed the side button. The Apple and the circle appeared... waiting, waiting until the circle was complete... Reboot... A calendar message appeared from 1980! I saw it and then it disappeared again.
Ah man, you just leaked their new time machine feature (not bug) they are working on for the next release. Probably due in version 11.32.5 but they could be saving it for the AW gen 4. :)
 
This is how I understood it, The 1st is treated as the previous month and current month simultaneously due to time zones. The 2nd completely turns over the month triggering the issue.
But then reports of the reboot issue were already coming in during the day that some people were crossing into 1st while others were still on the last day of the month.
 
I will go out on a limb and say that there won't be a release this week due to the battery/CPU throttling issues. Apple has their hands full this week.
 
Ah man, you just leaked their new time machine feature (not bug) they are working on for the next release. Probably due in version 11.32.5 but they could be saving it for the AW gen 4. :)
:D...but we have this time machine feature already (when you turn the Digital Crown), If you have not disabled it, like I did.
 
  • Like
Reactions: sbailey4
But then reports of the reboot issue were already coming in during the day that some people were crossing into 1st while others were still on the last day of the month.

Apple released iOS 11.2 on December 2nd around midnight PST. It was a reaction to issue based on the problems which started to spread around the world. In Sydney for example, it was already 7:00pm (December 2nd) when Apple released iOS 11.2.
 
  • Like
Reactions: Chazzle
Status
Not open for further replies.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.