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

Sorry, JG. You've been our unofficial leader in this crusade. Apparently this problem hitting the blogs have spurred some kind of a solution for the Google sync user. I guess with Exchange there isn't a way to find out what Google did and implement a fix. It's dependent on Apple. And now BGR (BGR.com) is reporting that 8.2 is not scheduled to be released until March to coincide with the release of Apple Watch. Sorry you are still having the issue. Hopefully it gets resolved for you soon but thanks again for helping out all of us.

@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'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.

@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.

All fixed as well. Iphone 6, 8.1.3, synching Google Calander on EST. Started suddenly about one month ago with no warning and began working today just as quick as it stopped. Hope those of you who are still dealing with the issue have relief soon. I will still be following this discussion.

Again, there is no evidence that Apple "intentionally" made a change aimed at disrupting their customers and therefore were not in a position to communicate anything neither to their customers nor to Google or Microsoft. They may have been taken by surprise (just like anyone else) by the non-desired GMT side effect of the change they made in iOS 8. They should have caught it in regression testing but did not. By the time it was noticed by customers it was too late for them. Lameduck is right in calling this a "chicken and egg situation". From here on they had to analyze the new behavior and may have concluded that it is not their issue, but indeed it is a Google problem, and it took Google such a long time to fix it. I don't think we will ever know the full story behind this. You have no choice but to cut them a slack and let them enjoy from the benefit of doubt. You did not show or share any evidence leading to a conclusive decision that it is a bug introduced by Apple.

Now let me address your language. Here is what you wrote:

"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."

Unlike you I am a programmer and have been for many years. Unlike you I engaged in a purely technical discussion and was never dragged by emotion towards an opposing point of view. At no point did I say to you "If you can't understand...." or "...you are never going to understand it" Who are you to dare say that?

The quote also includes "...I believe what has happened here is obvious to just about everyone..." all of your argumentation is based on belief not on facts or knowledge. Obviously, you are entitled to your opinion but you are in no position to put blame on Apple based solely on your belief.

You have previously argued, extensively and consistently, that it is correct behavior for a calendar to arbitrarily convert users' appointments to GMT (or some other time zone), depending upon what their server clock is set to.

I have argued consistently that it is not correct behavior for a calendar to arbitrarily convert users' appointments to GMT (or some other time zone), depending upon what their server clock is set to.

The above two sentences sum up our alternative views of how people use devices, how the world works and how software should work. You are entitled to your opinion, and I am entitled to mine.

Also, neither of us is a statistician (that I know of anyway) but what do you think the odds are that most users of Apple products agree with your idea of how a Calendar is supposed to work?

And I can place blame on Apple, Congress, the Easter Bunny, or whoever else I feel like placing blame on for something based upon what information I am able to gather and then use to form an opinion with. Once again, I BELEIVE, that I am probably just one of thousands of people who, based on what they know, also blame Apple for this.

Nice explanation via the barnacle analogy; curious to see how iOS Beta 8.2 handles things.

Also sounds like the "barnacles" would make a great transport mechanism for malware (or worse)... grab "fake TZ" (binecode" and then what...

Yay!!! I just set a new appointment in my phone and then I did what has become my usual waiting for the GMT time to appear so that I could go back and re-set it to the correct time zone (in my case, Central) but this time, nothing happened...the appointment appeared to be staying in the Central time zone!! I rushed to my computer to check out this thread to see if anyone else had discovered that the problem appeared to be fixed...or if this was just a fluke I was experiencing only to return to the aggravating task of re-setting my appointment. I am SO happy to find that it appears to be fixed (at least for those of us using Google calendars). Unfortunately, it sounds like no thanks goes to Apple for the fix but, rather, it goes to Google. THANK YOU, GOOGLE TEAM!!! YOU'RE THE BEST!

JG in SB - Thanks for keeping on top of this (somewhat entertaining) debacle. For the sake of information, I just added an event using the native calendar app and syncing with my Google account on my iphone5 and it is not displaying an additional time zone. I am still on ios 8.0.2, I stopped updating after my wife contracted the GMT Bug... -Brian

KarnFar being it has been well documented as an Apple bug and it seems you have not read the thread at all even a few pages back to see that other people who don't use Google still have the problem. Just because Apple support blames Google for the problem that doesn't make it true. I was going to stay on the thread to see Apples final fix in 8.2 but with people like you still posting inaccurate information I just can't take it anymore and need to leave this thread. Anyone like me who is just using Google and had Google fix the Apple bug should just leave the thread to avoid these types of inaccurate postings.

bcutty, Wow!!

I found a solution and wanted to help others like me with the problem of GMT showing up in the IOS Calendar. If it doesn't work for you, so sorry. Maybe you should call Apple and stay on phone for an hour. Or like you suggested, maybe you should just leave this thread and live with GMT, wherever you may be.

@KarnFar thanks for your post. Useful information to clean up my calendar for past event.

I see that you like me learned that if you even dare to express an opinion that maybe, just maybe, it was not an Apple bug you come immediately under fire. Amazing.