Worldclock went wrong for "tomorrow" items
apple Verified ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hello,
I use to have 4 Cities in my WorldClock
- Los Angeles
- New York
- Berlin
- Manila (Philippines)
i.e. we have the 31st Dec 2007 - 17:32 in Germany (Berlin) and the iPhone shows:
* Los Angeles - Today - 08:31 Uhr
* New York - Today - 11:31 Uhr
* Berlin und - Today - 17:31 Uhr
* Manila - 07/12/31 - 00:31 Uhr
For Manila it should be Tomorrow or at least 1st January 2008 ...
a year 2008 bug ...?
12 replies
Sign in or join Beachball Help to reply.
- 0
Man of Wy ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I noticed the same thing this afternoon in Minnesota. I show New Delhi and Tokyo as 07/12/31. I posted a photo of this strange behavior on my blog at http://manofwy.blogspot.com/
- 0
Malama Pono ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Same here. My clock doesn't reflect the international dateline for places I'm tracking. I'd like to check back to see if this will be answered. Thank you.
- 0
Michael Sherman1 ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I can confirm this. I have two world clocks: DC and London. Right now it says in DC it is 7:16 Today, but for London it says 12:16 07/12/31.
- 0
jpgoldberg ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Me, too. I'm in Dallas (Texas, USA), but World Clock is showing the wrong date for my relatives in Budapest (Hungary).
I saw on another thread (which I can't find now) that the problem goes away once you reach the new year in your own time zone.
Still this is an embarrassing bug, and we have no way of knowing whether it reflects some deeper bug.
Other rumors say that there will be an iPhone firmware update in the next week, so maybe that fixes this. But we might not know until next year.
Happy new year everyone.
- 0
SASChii ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
See what happens when your phone changes year...might need to power cycle the device.
- 0
Agent at Clicquot ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Are these times correct?
0516: UTC - Greenwich Mean Time
0016: Boston
1416: Tokyo, Japan
1616: Sydney, AustraliaIn looking at some World Time maps, shouldn't Tokyo and Sydney only be an hour apart?
- 0
Pasamio ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Sydney is currently on Daylight Savings Time, so it is now one hour ahead. Speaking for all the times ahead of UTC they look fine. Australian Eastern Daylight Time (AEDT, UTC+11) effects New South Wales south not including Queensland which remains on Australian Eastern Standard Time (AEST, UTC+10).
- 0
hexonxonx ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
All times and dates are correct now. It is now midnight January 1 here and the only place that still has a wrong date is Los Angeles because it is 11.05 PM there still. It looks like the iPhone gets confused on January 31. Software update can fix this.
- 0
iholla ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Its Still 11:27 in Alaska too:) We have 30 minutes of 2007 left
- 0
hexonxonx ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
You guys are so yesterday.
(Oh and I meant December 31 not January 31 in my post above) - 0
synapsestudios ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I don't think that this is a bug, but simply a formatting issue. UNIX time stamps use the following format: CCYYMMDDhhmm.SS
CC - The first two digits of the year (the century).
YY - The second two digits of the year. If ``YY'' is specified, but ``CC'' is not, a value for ``YY'' between 69 and 99 results in a ``CC'' value of 19. Otherwise, a ``CC'' value of 20 is used.
MM - The month of the year, from 1 to 12.
DD - The day of the month, from 1 to 31.
hh - The hour of the day, from 0 to 23.
mm - The minute of the hour, from 0 to 59.
SS - The second of the minute, from 0 to 61.(Reference 'man touch' in Terminal)
Therefore, '07/12/31' is actually 2007 Dec 31 and 08/01/01 is 2008 Jan 1. Maybe this field will be localized in a future software update to match the "Region Format" options under Settings. I will be filing a bug report shortly.
Cheers!
Edit: After posting, the forum reformatted the timestamp format -- to prevent this, I have removed the optional braces around CC, YY, and .SS
Message was edited by: synapsestudios
- 0
derchris ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
If this was an formating issus then it should display 08/01/01 on the firtst case (because Manial was in the new year before my other locations).
Let see what happens next year 🙂