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

OK. I'll revise my assessment to say that a preponderance of the evidence indicates that what we are observing today, with the GMT issue disappearing from Google synced calendars exclusively, is the result of a fix implemented by Google, rather than anything done by Apple.

I never claimed that what happened today occurred on the client side. I claimed, quite specifically, that I believe Google has blocked the time zone of its servers from being transmitted to clients that sync with those servers. This GMT Bug manifests when the iOS code picks up the time zone setting from the server and then transposes your appointments to that time zone. This has been confirmed by AppRiver, a HUGE provider of hosted MS Exchange services.

I hypothesize that if the buggy code can't acquire the server's time zone setting, it can't subsequently transpose your appointments. I believe Google has blocked that setting data from being transmitted to synced clients, which is why we are hearing from multiple users of Google Calendar today that their issue is "fixed without them doing anything" and we are hearing from no Exchange users....other than you....that this issue is fixed.

So, while I cannot be 100% certain, I believe it is totally fair to say, until other evidence presents itself, that Google did something that fixed this for Google users, and that Apple did not do anything yet.

OK then, let's assume Google fixed it, would that not mean that Apple was right from the very beginning claiming that it was a Google problem and not theirs?

The GMT BUG is gone for me as well I sink using Google Calendar with my iPhone Calendar only and it is now working GMT is gone. iOS 8.1.3 THANK YOU Google at least someone cares about the end user and how software should work.

@Backgammoner, not necessarily. See JG's recent posts.

Also, no one (including Google) said this was "fixed"; it's merely not exhibiting symptoms, which is different. Google may have done something on their end to work around the already-acknowledged bug on Apple's end.

I would say no since this started when everyone loaded iOS8 update. iOS8 changed something Google just made a change on their side to fix the issue. Plus you have issues with users that are using Exchange that have the GMT problem. So I believe the final fix still sits in Apple's lap. This is a BUG from Apple Google just did a work around for their users.

"OK then, let's assume Google fixed it, would that not mean that Apple was right from the very beginning claiming that it was a Google problem and not theirs?"

No. Absolutely not. Because, as has been confirmed over and over again, this BUG affects plenty of people who don't use Google for anything. The one single unifying factor common to everyone who experiences, or has experienced this bug, is iOS 8.

All Google did was a smart update on its side that prevents the bug from manifesting on its users' devices. The bug is still right there in the iOS code, but Google blocked the essential data it needs if it is to show up.

MS Exchange has not blocked that data, and the bug is very much alive and well for users who sync with Exchange.

So Apple's claim that this problem was due to Google was, and continues to be utter BS. Their software is just as buggy as before, and Google simply has deprived the bug of the data it needs to transpose the times of users' appointments to GMT. Also, at this point, there are multiple reports of the BUG being fixed in the 8.2 update. OK?? Why would Apple "fix" something that was not a problem with their software??? I know you read the 8.2 beta 5 release notes yesterday...because you tried to argue about them. Now there are other reports out confirming this may be fixed in 8.2.

I don't have time to get into an argument about the obvious today. If you can't understand what is happening, then you are never going to understand it. I believe what has happened here is obvious to just about everyone with any programming experience. I am not even a programmer, but I have enough experience to quickly identify what likely happened here.

Why do you enjoy arguing simply for the point of argument itself???

"This is a BUG from Apple Google just did a work around for their users."

^^^ Precisely. I wish I had simply said this, which is concise and 100% accurate.

I'm using Google calendar with iOS 8.1.2 and the GMT problem just cleared up for me at the same time as the other recent posters.... So it sure looks like Google has found a way around the iOS problem.

Kudos to Google for making their users' lives easier - even though we have not paid them hundreds of dollars each for a smartphone.....

To your question "Why do you enjoy arguing simply for the point of argument itself???"

it is simple - you present theories, without evidence, and treat them as fact. They are just that, theories and belief, not fact and evidence. When you say that "Apple claims are utter BS" it prompts me to bring up a scenario which is plausible and contradicts your theory. I will not argue with facts when I see facts, I am entitled to argue with theory.

You cannot refute that the argument that the problem with Exchange is not in the mighty hands of Microsoft just like it may have been in the mighty hands of Goole all along. The fact that this problem manifested itself with iOS8 does not mean that it is a bug introduced by Apple in iOS 8. This is not necessarily the only way to argue it. I can argue that Apple has mis-interpreted the Internet standard (prior to iOS 8) just like Google and Microsoft did. In iOS 8 Apple introduced a change which is consistent with the Internet Standard but had a side effect of breaking the communication with Google Calendar and with Exchange. After some period of examination Google may have concluded that Apple's interpratation of the standard is correct and they fixed their code to be consistent with that interpretation. Do you see my point? This leaves the next fix in the good hands of Microsoft for the Exchange part.

Thank you Google for working around the Apple IOS defect!

My iPhone6 currently running IOS8.1.3, which had the GMT bug while syncing with my Google calendars, no longer exhibits that defect when creating new appointments on my phone.

I was also able to repair the appointments made during this dark time of the GMT defect by using the phone to edit the appointment(s), changing the time zone from GMT to my own, then adjusting the appointment time by subtracting the number of hours from GMT to my time zone. For example an appointment that is really at noon would show 8pm GMT before/during edit, so I'd scroll that time back to noon and done. Those appointments are keeping the "clean" non-GMT time now as well.

Backgammoner... Yes, you definitely have a point or perspective on what came first..... "chicken-egg problem". It is logical and possible that Apple "had it right" with regard to the use of UTC/GMT timezones in how their native iOS Calendar apps should work (at least with iCloud users). And, Google, Microsoft and others had it "wrong" and are now "fixing their issues" to be compatible with Apple iOS and/or Apple's native iOS calendar app.

I will say -- from and End-User viewpoint -- the problem with Apple's native iOS 8.x/Calendar surfaced after iOS 8.x was released.... and it is really on Apple to have gone public (perhaps with Google and Microsoft??) and explain "what happened" and "what are 'we' going to do about it".

Other calendar apps (Calendar5, Outlook, etc.) -- that connect to Google, Microsoft Office365 and/or Yahoo services -- did not have the GMT problem -- perhaps because how they use the TZ setting when syncing.

Whatever the reasons -- or who's responsible --- I think we can all agree that from a public relations viewpoint -- this is a "F" grade for Apple -- and perhaps even Google and Microsoft --- for poor customer communications. It has been a painful and frustrating 100+ days living with this "bug"... including the radio silence from Apple (and Google/Microsoft/etc..).

FYI.... I have three (3) Office365 accounts - and all three continue to have the GMT "bug". So -- no joy here yet 😟

I also tested my "backup" iCloud and Google accounts -- they are both working properly (no sign of GMT issues). So -- let's see if Microsoft fixes things on their end -- or if Apple fixes the problem with iOS 8.2 release in a couple of months.

Meanwhile, I continue to use other 3rd party, non-Apple calendar apps (Calendar5 and Outlook) -- and have ditched the native Apple iOS calendar app until this issue is resolved

@Lameduck fully agreed Apple's handling of the case was abhorrent and dis-respectful of it paying customers. Their silence is roaming, at least thus far. We are dealing with three proud Behemoth organizations and I don't think we will ever know the full story, none will want to take full blame for this.

If Apple did this "intentionally": 1) knowing in advance that it would screw things up for so many users due to Google and MS needing to "catch up"; 2) failed to notify customers, Google, or Microsoft; 3) failed to document the new design in any way; and 4) failed to offer any explanation of what they did even after thousands of customers complained, that is 1000x worse than if this was simply a bug due to crappy coding and a lack of regression testing and/or quality control.

Iphone 6, iOS 8.1.3, synching Google Calendar... no more GMT bug for me either.

I'm here to confirm that I no longer see GMT in my events that I create from iPhone 6 Plus iOS 8.1.3. Google Calendar (CalDAV).

People at the Google forum are rejoicing as well.

https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!topi c/calendar/CaPn0hLOU0c%5B176-200-false%5D

Who flicked the switch or fixed this is anybodies guess.