Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi, anyone else having this issue? I just checked my world clock on my iphone, as I have contacts all over the world. It all looks right except for Japan, which of course is many hours ahead of me in the EST of the USA. For London, Paris, NYC, etc. the time is right but now (at 11:26am) for Tokyo, Japan the clock says "1:27AM on 07/12/31".
Since Japan is already in 2008 as I'm writing the message It seems related to the difference in years. I hope this will correct itself when we reach 2008.
Imported from the Apple Support Forums via the Wayback Machine 🔗
You are absolutely correct. I have world clocks configured to show Tokyo which has already brought in the new year, but the date still says that it is "07/12/31" and all of my other cities that have not hit 2008 say "Today" for the date.
So, yes, everyone with 1.1.2 should have this issue as well. I cannot confirm other firmware versions.
0
-Troy-__·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi. I'm new here so sorry if it's a silly question but since we have found this "issue" do we need to alert Apple somehow or do they read through the boards and pick up on issues that way? Just want to make sure they are aware of the problem since having a wrong clock/year could mess up the calender feature/alarms as well. Just checking! Thanks and HAPPY NEW YEAR!
0
cationic·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Same here. My Shanghai clock shows 07/12/31 even though it is 2008 over there.
0
amk829·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I'm also experiencing the issue... Tokyo reads the date as 07/12/31.
0
Grant Davies·
Imported from the Apple Support Forums via the Wayback Machine 🔗
It will change when your local timezone reaches 2008. Try setting you local time ahead until tomorrow, all is right again.
0
MacOsX·
Imported from the Apple Support Forums via the Wayback Machine 🔗
This is still a bug that needs to be fixed via firmware update.
Just because the bug will not be an issue for more than one day a year, it still may be tied into some other underpinning issues that we have not seen to date.
I do hope Apple fixes this issue promptly, which I am sure they will do once they are aware of the situation.
0
Robert Viater·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I have Sydney, Australia in my world clock, and i have the same problem. I hope it doesn't do this when it becomes the new year in Chicago.
When I first got my iphone, i called somebody and in my recent calls it said "Name 12/26/31" which i thought was weird... and every time i called anybody else the one with the funky year would stay on top.. then i cleared my recent calls and it was all back to normal... Maybe this has to do with the weird world clock dates....
0
HighTechTerror·
Imported from the Apple Support Forums via the Wayback Machine 🔗
After seeing this bug on /. I checked my iPod Touch, and this also affects the Touch as well. Has there been any discussion as to when this will be addressed?
0
Goshia·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Stockholm also reads 07/12/31 and does Beijing.
0
Dave Harris·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Now Europe is in 2008, this bug is manifesting itself in reverse: US cities are being displayed with a date of 08/01/01, despite still being in 2007. Europe and Australian cities are listed as "Today".
Dave
Derby UK
0
Elbert Cuenca·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I'm in Asia (GMT +8) and in my case, countries that had yet to turn into the new year were showing up in World Clock as 08/01/01 (yy/mo/dy), which was wrong. Actually, what it should have displayed was the word YESTERDAY, which it's doing now.