iOS 8 Calendar on iPhone showing GMT times for new events.

If you use gmail (Google) calendar I can tell you how I corrected mine. I logged onto to google calendar and removed time zone settings by telling Google not to convert the time to any zone. Do this by clicking on the time zone and checking remove event time zone.

JG, the bug is not translating over to my iPad after I edit the appointment using the All Day on-off trick; the appointment on my iPad came through without the GMT entry in the body of the appointment and without GMT in the time zone field. For kicks, I edited the appointment on my iPad to see if it would add GMT. It did not add GMT; The edited appointment also came though back on my iPhone without the GMT entry;

So a round about solution appears to work this way:

1. Add an appointment on the iPhone,

2. Let the GMT bug hit,

3. Open/edit the appointment

4. Turn the All Day switch on and then off,

5. Correct the appointment to the correct time for your time zone,

The appointment appears to stick with the correct time across synced iOS devices.

Working for me so far. A pain in the butt, but at least it gets rid of the GMT bug for now.

Thank you DaveWhite! This, setting it up as an Exchange account solved my iPhone 6 GMT issue. I had previously set the calendar up using the iPhone's Google account menu.

Turns out it is also the Google-recommended way to set up mobile calendar synch. I can now create a Google calendar event on my phone and it resolves normally on my desktop calendar as well as all of my mobile devices.

For all others still suffering and looking for more additional info, here is the Google help page instructions:

https://support.google.com/calendar/answer/151674?hl=en

@rick287: Thanks for posting that E-mail. It confirms what we (AppRiver and I) have been told by Apple as well. I agree....at this point it seems pretty obvious that this is an iOS bug and also how the bug is manifested based upon various users' setups.

Inevitably...some new person is going to find this thread and post something like: "The senior supervisor at my local Apple store confirmed that this is not a bug with iOS and that Google needs to update its servers to resolve the issue." Or "All you need to do is hard reset your device." And then the next person who comes along reads that as the last post and assumes that this was the final answer....and then instead of reporting the problem to Apple, they don't do anything or worse yet they do something that is a total waste of time and energy like hard resetting their device.

The fact that Mr. Jones confirms this is an iOS bug (i.e. Apple is no longer blaming everyone else on Earth for it) is encouraging, along with his prediction that there will be an update "soon." Well "soon" is a very subjective term. I suggest that if we want to make "soon" something that happens in the next 4-6 weeks instead of in the next 4-6 months....that it's a good idea for as many people as possible to report this individually. That will make it a "widespread impact" and a very high priority at Apple.

Also, I assume people in Apple Engineering have read and are monitoring this thread. That's what I would do if I were tasked with actually fixing the code to resolve this bug. Several users here have provided highly detailed information about how the bug is manifesting in their different setups which ultimately would be of major benefit to anyone who actually has to revise the iOS code. So I hope if anyone else has a totally different experience with this bug and has figured out either how to replicate it or better yet, identified exactly what causes it to show up in their technical environment, that's helpful.

Thank you for pursuing a tech support case with Apple and apparently getting somewhere with it!

I solved this problem on my iPhone5 by doing the following:

Go to settings --> General --> Date & Time

Change Set Automatically to off

Go to settings --> Mail, Contacts & calendar -- Time Zone Override

Change Override to on

It was a little strange -- having to change the setting in two places -- to say nothing about turning one of them on and the other off, but, hey, it worked for me anyway.

I have a temporary solution that works on my iPhone 6 running 8.1.2 if you're interested...

1) create a new appnt

2) select repeat... Every day

3) choose end date... On date... The same day as appointment

4) Add

Apparently repeating appointments are immune to the bug and by making the end date the same as the start date it creates a one time appointment. I hope it works for you too 🙂

A temporary solution is to enter the appointment as usual on your iOS device. After you click Add, the GMT will appear. Then edit the appointment, change it to an All Day appt and then immediately change it back to a non-all day appt; The time listed for the appt will now be the GMT time but you can now change it back to the proper time. do that and save the appt and the GMT entry will go away. As I said, a pain for each new appt but its worked for me.

Gator5000e wrote:

A temporary solution is to enter the appointment as usual on your iOS device. After you click Add, the GMT will appear. Then edit the appointment, change it to an All Day appt and then immediately change it back to a non-all day appt; The time listed for the appt will now be the GMT time but you can now change it back to the proper time. do that and save the appt and the GMT entry will go away. As I said, a pain for each new appt but its worked for me.

This worked! thanks!

Apples needs to come up with a proper fix. This is obviously an IOS8 bug.

No. There is no solution or even a decent workaround. This is a BUG in iOS 8. It is baked in to the code of the operating system. Even a brand new device you purchase at the Apple Store today will have this exact same problem because it will be running iOS 8. We are all stuck waiting for Apple to fix this.... The best thing you can do is repott your case to Apple. Use the link provided in my post above.

@rajshree: this is incredibly frustrating. Have you READ through this thread? The problem is not "only with Google." I don't use a single Google product....I use Microsoft Exchange and I have had this problem since September. I have spent hours of my practically non-existent free time trying to work toward a solution on this. So has Aaron Cohoon at AppRiver, my Exchange host. He also has confirmed this is a BUG in iOS. And by "confirmed" I mean received written confirmation from Apple that this is a bug in iOS 8.

When you go and call Apple tech support.....and make claims such as "this only affects Google Calendar" you are MOVING US BACKWARD!

Again, if you had bothered to read all of the extensive troubleshooting that has been done, and is documented in this thread, as well as documentation of correspondence with Apple, including correspondence from Apple CONFIRMING THIS IS A BUG IN iOS, you would have been able to convey this information during the time you just wasted talking to upper level tech support.

Instead, you have allowed them to log a case and state "Customer confirms problem is unique to Google Calendar. Problem is generated by Google not Apple." That is undoing all of the work we have been putting efforts into for the past 3 months.

If you had bothered to read this thread, you would have been able to tell the tech helping you that they were full of sh1t when they claimed the problem is generated by Google, cited several examples the very same problem occurring in environments that don't include Google, and actually gotten them to look for a solution or at least register an additional case of the problem.

I don't care what sort of "creative troubleshooting" you tried or how "adamant" you were. No amount of "troubleshooting" is going to generate a solution because the problem is due to bad code that is part of the iOS operating system. Until Apple fixes their buggy code, this issue will remain. Having them talk to Google.....which they won't do in any case....is a waste of time. Apple needs to FIX ITS CODE. Period. That's the only solution.

Everyone, please do your research before you go and provide incomplete information to Apple that they will ultimately use to blow all of us off.....

So, this bug with iOS8 was first reported here in this thread on September 21, 2014 and so far there is still no solution from Apple? Perhaps this was introduced and/or is not being fixed because Apple doesn't like Google. 🙂

I too am having the problem ever since upgrading to iOS 8. I use CalDAV and CardDAV to sync with Google Calendar and Contacts. Since upgrading to iOS8, all new events created on my iPhone are in GMT time. If I go back and edit the event, I can change the time zone to Pacific Time (where I live) but then this keeps the time (numbers) the same (from GMT time) so I then also have to change the time back to the correct event time. If I create an event directly on Google Calendar via the web, then the event is in the correct time zone.

Definitely an iOS bug. Instead of trying to excuse it or explain that it is a "feature", Apple should be saying "excuse me" and fixing it.

I do not sync to iCloud. My problem exists solely with my iPhone 6 and entering appts using Google as my default calendar.

If I use iCloud as my default calendar, no problem.

If I add the appt from Google, no problem.

BUT, if I add the appt from my iPhone using Google as my default calendar, the appt shows up with the GMT time. I then have to go back in and adjust the time to my time zone. Basically, I have to enter the appt twice. Super annoying but the only workaround other than entering appt from Google.

😠

Question:

"I do wonder what the difference is between those for whom this occurs, and those for whom it does not."

Answer:

This has to do with the system clock time setting on the physical server hardware on which your synced account is located. The "GMT Bug" is picking this up from the server and then transposing your appointments into whatever time zone the server's clock is set to. If the server is set to GMT then you'll see "(GMT)." If the server's clock is set to PST you'll see "(PST)" and so on. If your server's system clock is set to a different time zone that you are in, then you will see this bug manifest on your iOS device(s). If it is the SAME as the time zone you are in then you won't see the bug, but the bug is still there in the code on your iOS device(s).

Here's an article by AppRiver, my MS Exchange host who has spent tons of time working on this both with me and other users:

http://blog.appriver.com/2014/12/ios-8-calendar-events-display-dual-time-zones/

This describes what happens on MS Exchange servers but the same exact thing happens on Google servers.

Others in this thread posted about how stunned the Apple Store employees were to open up a brand new iOS device in the store and see this bug show up without any changes whatsoever being made to default settings. This bug is embedded in iOS itself...every single device running iOS 8 has this bug embedded on it. The only people who will experience the monumental hassle it creates are those who sync to accounts on servers set to a different time zone than their device time zone. There are people out there right now running iOS 8 that don't see this bug. But as soon as either 1) they travel into a different time zone than the one they are in and their iOS device updates its clock; or 2) their account gets migrated to a new server with a different time setting (happens as part of automated load-balancing operations by providers like Google), the bug will show up....and they will all start posting here stumped as to how this happened without them changing any settings.

I promise.....follow this thread (or go back through it) and you'll see it. Every few weeks when the Google servers migrate a new group of accounts around, a bunch of new people show up....don't read any of the previous posts in the thread...and start saying that this "must be due to Google because Apple says it is" and the fact that they didn't change any settings on their device "proves" this. As explained above, this is already on all devices running iOS 8 and you don't have to change any settings to encounter it...all that has to change is the system time setting on your synced account server. The bug was there all along. It's like a leak in your roof: it could be there for months, but you aren't going to know about it until it rains right?

Thanks for taking the time to call in and report this to Apple. That really is the most effective thing you, or anyone can do. We need to register as many cases of this issue with Apple as possible so that they make it a priority.

Your simple fix did it for me, pogster.

In attempts to fix it on my own, I'd turned on Time Zone Override, and thus was seeing events listed in both local time zone and in GMT.

But when I turned Time Zone Override off, then did a restart (holding down power and home buttons), all was fixed. I'm back in my zone.

Yes, exchange is a local account server so that makes sense. I can create an appointment on my iPad and assign it to my exchange calendar and as soon as I reassign it to a google calendar the GMT shows up... of course my toggle "all-day" work around is still clearing it up for all my devices.

Even better... I create on my iOS 8 device assign to my exchange calendar and then reassign it to google and GMT shows up... If I create and assign to google the GMT shows up as expected and if I reassign to my exchange... GMT will NOT go away... I have to toggle "all-day" to get rid of GMT. So as screwed up as this is you are telling me that as soon as I assign my event to a calendar server not housed in my time zone the GMT virus will rear its ugly head? Maybe I will move Greenwich. This is just stupid!