There should be some error in Mobile Safari, since I have this problem, it works everywhere except for the iOS device. It does not correctly handle the correct ISO date and time (for example, "2011-10-09T14: 00: 00.0000000 + 01: 00").
The problem is using the UNIX timestamp, although it works with the new Date () method. setTime (); time is converted to UTC, so if your application does not handle UTC offsets, it will show the wrong time. In particular, if the date-time refers to a date in the future or during a period when the daylight saving time has changed, the time in the time stamp of the era will be incorrect. This is why timestamps are not used to store date and time values.
The only workaround I could fix was to split the date object into a JSON object containing its properties, and then restore them on the client back to the Date () object.
source share