Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Totally not happening. Works fine. I live in Kenya, I mean Hawaii, only one American ever confused the two, maybe it is our perfect weather.

"today it is perfect, followed by perfect tomorrow and for the rest of the week"

Seriously, I am on the latest WatchOS and have an iWatch Series 2, and Siri does the weather great.

Maybe this is fake news, or only a subset of watches watchOs versions have the problem?
 
Seems like it was just a bug with daylight savings time. The issue is no longer happening for me after the time change.
 
Peripherally related, but my Gen 1 Apple Watch takes nearly 5 minutes to restart after a hard reset, is this normal? Not sure if it has anything to do with it has also recently been very flaky with receiving notifications even though everything is set to "mirror my iPhone".
 
I'm pretty happy with my Apple Watch, but I rarely use Siri. It's just too slow. It frequently says "I'll tap you when I'm ready" before it recognises what I say.
 
Except it is a rather deeply hidden bug, as said question would only cause the crash on one day out of the year. Any other day, no bug.

People are free to hold this opinion - as long as they never made fun of the Zune leap year bug. Otherwise fair is fair, Apple deserves a little grief over this.
[doublepost=1509922363][/doublepost]
It is a bit amazing since they had problems with the time change before that they would have an issue with something like the weather that is looking ahead a number of hours. Something in the code doesn’t like skipping an hour or have an hour repeat itself.

I remember back when Daylight Saving Time was first extended - Outlook calendars and Exchange servers had a dickens of a time. Microsoft released something like 30 patches, but the calendars still were screwy during that three week period in March between Daylight Saving that is and Daylight Saving that was.
 
Last edited:
Tried this several times and couldn't get it to work. Then realized I needed to update. Updated... still can't replicate. Wonder what makes my watch different than those affected? Series 1 (A1803) WatchOS v4.1 (15R846)
 
Good lord - for those trying to execute the bug NOW, please stop. You had to do it yesterday when it was in effect. No one is experiencing the issue now.
 
Alarm clock is interesting. If I set my alarm to wake me up at 7am, then I want it to run at 7am, no matter what DST changes. On the other hand, I know people who needed an alarm "exactly 24 hours from now", and that alarm shouldn't change to "25 hours from now" or "23 hours from now" just because of DST (think of a chemical experiment where something is mixed and needs to be checked exactly 24 hours later).

Now this problem here is different. There is no excuse for crashing because of DST. I remember a few years ago some game console crashed on February 29th, I think. The crashing code was shown, and within ten lines of code the programmer had written two different ways to figure out whether a year was a leap year, and one way gave the wrong result. So within ten lines of code the software was (a) convinced that Feb 29th was a correct date and (b) convinced that Feb 29th was _not_ a correct date, and then got itself utterly confused.
[doublepost=1509890412][/doublepost]
With the explanation given (something getting confused with a DST change), the problem would have gone away, and come back in exactly six months or exactly twelve months, but only for one day.

Now that's interesting... I've been asking for the weather every day since I got my Apple Watch, and good thing nothing happened.
 
This is an odd problem. It's weird that it is only happening to watches in certain countries, and not all. Hopefully a solution is found soon, or else forgetful users are going to be restarting their watches quite often.
 
How could this happen? This is so common and it does this.

I guess were weathering wrong?
 
OT believe it or not but on last Sunday, October 29 th, I had two brand new Apple Watches Series 3 got stuck at the Apple Logo. This was after entering the passcode. No matter what I did, they got stuck at the logo.

Finally I could unpair both and repair again but afterwards the were completely inoperable. :(

I spoke with Apple Support who did not have a solution.

I also posted this issue on the Apple Discussion Forums but my thread was deleted as not being technical :mad:

Next morning, both Apple Watches were completely fine again and still are. I did a new pairing and both showed some activation lock screen where I had to enter my Apple ID. I have never seen such a scree before.

I still suspect either some connection with DST Apple server issue.:oops:
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.