Daylight savings pushed all my appointments ahead 1 hour

Lo and behold this is STILL an problem for Apple in 2017 with iOS 10.3 on an iPhone 6plus. 😟

The appointment in question was created in MS Outlook on corporate Exchange server, and is a repeating weekly meeting I've had going for some time, and got pushed to the iPhone's calendar via the sync via iTunes.

The appointment was created to occur at a given time - 16:30 Eastern Time (US).

Now that we have gone past the end of Daylight Savings and back to Standard Time, the appointment in the Apple iOS calendar did not adjust for the end of daylight savings and return back to standard time, so it is showing the appointment not at 13:30 PT (which is where I am, on the west coast) but rather at 12:30 PT.

So a daylight savings handling in the calendar appointments failed apparently. Come on man. Now what? Delete the series out of the iPhone and hope that the sync doesn't delete the master MS Exchange appointment? That seems sketchy. Why is something so basic as managing a calendar in 2017 still a random hoping for the best with no reliability?

Update - Yep, deleting the series that was wrong on the iPhone, of course, on sync with Outlook via iTunes then deleted it from the master Outlook calendar. Expecting that result, I saved off the meeting info in a text file.. which I'll now use to recreate the meeting in Outlook/Exchange again. Then see if it syncs correctly.....

Update: recreated the meeting in Outlook at the same time (for 16:30 Eastern Time (UTC-5)) in the PT (UTC-8) timezone on Nov 9, 2017, which ends up at 13:30 PT. Synced in iTunes, and now the phone has the meeting at 13:30 correctly (rather than the 12:30 version it was indicating from the meeting it had before the change from DST to STD). So its good for now... I expect until we go back to daylight savings time in March/April 2018.

Come one Apple, this is NOT that hard. The appointment carries the info for when it is (at creation time - including the timezone), and the calendar should display when it is in the timezone presently in effect (where the phone is, and if we are in/out of daylight savings time). Why can Apple not get this to work? Every year its daylight savings time changes bugs.

I'm not sure the masses of the population having autocorrect hose up their tweets vs a problem in appointment handling between iOS and exchange is in the same group of users that one could draw conclusions.

How many twitter/imessage users also maintain appointments on an exchange server and an iOS calendar (not sure if iCloud is involved here as the sync I'm doing happens over physical wire between phone and computer running Outlook and iTunes)?

For it to be an isolated case implies the process is non-deterministic. Why would my phone and my computer be the only occurrence of this? I suspect more likely is that most of the folks either don't speak up about it (here) or just stopped trying to maintain a single iOS calendar as its just not reliable.

For what its worth the appointments that iTunes syncs down to the iPhone via wired sync, show up as belonging to Calendar:Calendar for me. The ones I create on the iPhone directly, also get created in Calendar:Calendar. So on my iPhone there is no separation from where the appointments originated, which is what I need/want - for both my phone and my computer calendar to have all appointments so when I look at a calendar I can see what is coming up when - private or work. If your maintaining ios and exchange calendars as separate entities then that may be one difference that causes things not to trigger for you.

There is a bug - proof by example. What isn't clear is what the components to trigger the bug are. It could be a very uncommon set of elements that come together to trigger it. Will see if it reoccurs in the spring 2018. Then I'll hopefully find my way back to this thread, vs the other threads that exist in the world and may get turned up on a google search for problems with ios calendar daylight savings.

I have an Exchange Calendar for work and an iCloud calendar for personal appointments and all of my appointments kept the correct time. Both calendars have individual appointments as well as repeating appointments. Since yours is the first post on my this issue in 2 1/2 years, it doesn’t seem like this is a widespread issue. If this was happening for a lot of people there would be news stories and many pages in these forums demanding a fix. Just see all the questions regarding the “i” autocorrecting to an “A ?.” There are pages and pages of news stories and blogs reporting this problem but nothing about the end of Daylight Savings messing up their appointments. I’m not saying that there isn’t a problem with your calendar but it seems to be an isolated case.

You should have two options for the iPhone to set the time. You can set it manually or you can have it set automatically. With automatically, daylight savings time changes are sent via your cell phone carrier. If you have it set to manually enter, you will need to go in and change the time for daylight savings. I'm not sure why your appointments would have changed. I have my iPhone 6 set to automatically set the time. On Sunday morning the time had been updated for daylight savings and all of my appointments remained as they were supposed to.

This is happening to multiple devices in my organization as well. The same mail account synching with an Android does not have the calendar issue. Updating to iOS 8.2 does not fix it. This is only for recurring entries that were created before daylight savings time shifted. No newly created entries are affected. DST moved those meetings 2 hours forward instead of 1 hour, like it should have.

Some more information on this issue:

-It does not appear to affect the meetings on my iPad, which is on iOS7.

-All of the meetings go back to normal after April 5th, which is the date that DST would shift, before DST was elongated in 2005.

I'm not sure why your appointments would have changed

Because the time for appointments are relative to GMT. DST changed relative to GMT which never changes. You can force the times to always remain the same by turning on Time Zone Override.

You have to remember that when put events into a calendar that the time is relative to GMT and your location. Put an event that is a 5:00P EDT and fly to California the time if the event will change to 2:00P PDT. The event is still occurring at the time you specified as it is still 5:00P on the east coast. If you have an event scheduled in California and you enter the event into your calendar while you are in New York you need to put the time for the event as when the event will occur in New York. Then when you arrive in California the time of the event will adjust.

You can skip all this by turning on Time Zone Override and selecting the time zone you always want to use.

It sort of makes sense once you get used to it. I fly to Europe a lot from the east coast. When I enter my flight information the times are relative to the time in New York when the event will occur in Europe. I have to make some mental calculations to add six hours to the event time. My calendar now shows the true duration of the event, especially when flying.

My recurring appointment shows up at 5:20pm instead of 4:20pm daily (week days), but only for March 9th to April 6th. The meeting appears fine in my work e-mail. This is happening not only to me, but others using iOS devices in my organization. Time Zone override does not help at all.

What is also happening: Appointments from March 8th to April 5th are showing up with time zone issues in our e-mail client, but only after showing that they were updated by the iOS device. They appear as occurring in another time zone. This only happens for repeating meetings updated after synching with an iOS device. With all of the weird DST issues on Apple devices, doesn't this point to iOS8?

I mentioned that this is not occurring on my Android or iPad with iOS7. I am an MDM Admin, so I have to synch my mail to multiple devices to be able to assist people with their issues. This really looks like an iOS8 issue to me.

This really looks like an iOS8 issue to me.

I misunderstood what you were getting at. It does seem to be affecting some events. I have a recurring event that shifted 1 hour but other recurring events are just fine. I don't remember when I entered those recurring events. Events that are single events are fine and did not shift in my calendar.

I wish Apple would add a field to the calendar events where you specify the time zone. Once you do that the time zone for that event is locked and will not change when the device changes time zones. I think that would solve a lot of the problems with times changing on events.

I agree, that would help, but I think there is something flawed in how they are correcting for DST. It's like they over-corrected by going ahead 2 hours for DST, and everything returns to normal once DST returns to where it was pre-2005. I can only guess that they built in the logic for the DST settings as they were before 2005 and no one re-wrote them. They keep trying to correct DST when the timing changes. That's what it seems like to me, at least.

I agree, that would help, but I think there is something flawed in how they are correcting for DST. It's like they over-corrected by going ahead 2 hours for DST, and everything returns to normal once DST returns to where it was pre-2005. I can only guess that they built in the logic for the DST settings as they were before 2005 and no one re-wrote them. They keep trying to correct DST when the timing changes. That's what it seems like to me, at least.

Your guess is as good as anyone else. I don't understand why only a few events were affected. Only one recurring event on my calendar was affected. All the other events seem to be OK, recurring and one time events.

I don't use the Apple calendar app and instead use a purchased app. It had the same problem which indicates it is using some of the date routines that Apple provides rather than the apps own date routines.

This is only affecting some repeating appointments on mine and my customers calendars. I'm unsure why it is not affecting all of them. I wish someone from Apple would weigh in on this.