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

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 🙂

I was having the same problem and this is what helped me.

1)If you have Gmail try this...

2)Sign into gmail on your computer.

3)Type in your bowers www.google.com/calendar

4)On the upper left hand side there is a small monthly calendar, under the small calendar it says 'Other calendars', under 'Other calendars' it says 'Add a friend's calendar.'

5)I typed in my own email under 'Add a friend's calendar' and it fixed it on my phone.

Hope this helps.

Same problem. Pretty big problem: GMT pave-overs when generating or editing events on synced gmail calendars from within iOS 8.x. No reasonable solution seems possible until Apple (deep sigh) acknowledges this bug and deigns to fix it. Looks like a low priority on their part though - as this effects lots and lots of iOS users NOT using iCloud for calendar sync we will have to struggle and wait. And wait...

After speaking with Apple support about this issue for hours a senior advisor told me that it is a known issue with no solution at this time. Hew advised that I report it which I did. Now we wait.

Awkward, but this worked for me. Thanks Angelitos

I noticed that when I am offline, it keeps the correct time. As soon as I go online, it updates to GMT so it must be interacting with a server to change it. Modifying the settings as suggested made no difference. I have not noticed this tidbit in the postings that I read. Interesting

this is NOT an iOS bug. Your repeated insistence on this is why there has been no resolution. You are not being truthful that its happening to Exchange servers. it's only happening with google calendars.

I am a google apps users. If i sync with the google preferred method on iOS devices i have the GMT issue. If i delete the google setup method and use MS Exchange on the iOS device there is NO GMT problem (to be clear I am setting up my google apps account with exchange) Folks this is a Google issue. it started when they upgraded the calendar recently. Google is ALWAYS changing things and some of those times its not for the better.

also if you google "google calendar GMT issue" you will find posts about this issues dating back to 2009.

https://productforums.google.com/forum/#!topic/sites/Zsn512HhPJE

@thekingfishh225: Normally I make it a point not to respond to misinformed yet outspoken morons, but I am making an exception in this case and I am going to respond to you.

Here is a video I made demonstrating this bug....on my Exchange server:

http://youtu.be/cgP1zyi_iV8

The video demonstrates this bug occurring via MS Exchange...I don't use a single Google product for anything. You, and anyone else, can see it clearly with your own eyes. It has over 1200 views and many people commenting that they are also experiencing the same thing...using Exchange.

Also, here's confirmation for a 3rd party source: an article about this bug on the AppRiver blog:

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

Here are the first two sentences of the article in case you are too lazy to click the link....

"We’re getting reports from users on both AppRiver’s Hosted Exchange and Microsoft Office 365 platforms that calendar events are displaying two time zones on iPhones and iPads running iOS 8. Calendar events that were created on an iPhone or iPad running iOS 8 or higher, or created in Microsoft Outlook in some cases, display the server time below the device’s local time when opened on an iPad or iPhone running iOS 8.0.0 through 8.1.1."

AppRiver is talking about their customers using Microsoft Exchange.

Then there's the not so insignificant fact....documented in several posts above...that APPLE HAS CONFIRMED THIS IS A BUG IN IOS.....and that they are working on a solution. So this sort of indicates you are 100% wrong about 1) this issue not being due to a bug in iOS; and, 2) whether "repeated insistence on this being an iOS bug" is preventing/delaying a solution. You are 0 for 2. Outstanding.

Also, if you had bothered to READ any of the preceding thread before jumping in and telling us we are all liars....you would see why it is possible that this might not affect YOU on Exchange but is affecting others using Exchange. Its the exact same reason why it affects YOU using Google but doesn't affect some others using Google. It has to do with the system time setting on the server that hosts your Calendar account...in Exchange, Google whatever. That's what the bug acquires and then references when it is displaying dual time zones.

Generally, it's a good idea to make sure you know what you are talking about before you spout off in a forum and call people liars. That is unless you absolutely don't care about looking like a moron in which case proceed as you have done above.

Have a great day.

When I use Google's preferred method I get the GMT issue when I use exchange I don't. I have three Exchange accounts and the only time I have seen this has been with GOOGLE calendars and NOT just with iOS. I have seen this for years which is why I chimed in. I am not sure why you have to get so personal in your posts you must be a miserable individual outside of an online forum where you can talk big. Anyway I digress guess what YOU are having this issue I am not, I figured out what works for me and ALL OF MY CLIENTS that was having the same issue. Not sure who the moron is supposed to be here because YOU are still having this problem not me. Maybe you need to brush up on some of those troubleshooting skills.

No matter it's Google problem or not,it happens on ios,then apple should slove it or provide an announcement.

having exactly the same issue syncing google calendar with iphone.

obviously IOS8 related:

1) never had this problem with IOS7

2) all old events created before are fine. no matter account deleted on iphone, re-added, re-synced, etc...

3) only new ones created from iPhone have this problem.

4) new events created from google calendar website do NOT have this problem.

guess IOS8 calendar is trying to be smart on where user is located. As I only allow map apps to access location, it has to fall back to the default value of GMT?

time schedule is still correct w.r.t. my time zone, just that the default GMT mode not so cute.

Apple please fix the bug. IOS8 and Yosemite... what else do i have to say? you can do better.

@thekingfishh225: Let's look at the thread above. I am not the guy who showed up and immediately claimed everybody here is "not being truthful" without having read the preceding posts or having any background on this issue other than my own personal experience. That was you.

Also, after I presented three (3) different concrete and independently verifiable means to confirm that this issue affects people on Exchange servers...not just Google......you continue to insist that it doesn't. In light of facts that are not subject to interpretation or dispute, you still insist this "only affects Google users."

So yes, I am perfectly happy to allow others to decide for themselves who the moron is here.

Have a wonderful day.

Exactly the same with me only mine shows actual GMT time in parenthesis. Tried every setting I can think of but to no avail. Stunning that it hasn't been fixed!! A couple of settings I tried moved the appointments to the GMT time, unbeknownst to me...missed a couple of things. Infuriating!

WWhat baffles me is that not only has the particular problem been on this discussion board for THREE MONTHS (to the day) without any helpful info. or changes from apple, but if you do a search, it was also a problem with ios7, ios6... Good job on this one, guys... Come on, what's up??

The current problem does not affect iOS 6.1.6, the version installed on my old iPod Touch 4.

This didn't work for me.