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

OK.  Let's agree to disagree and leave it at that.

My position may sound confusing and it is ok.  I agree that Apple has to listen to its customers, and did not demonstrate care to their customers so far. 

At the same time, if Apple would be taken to court and asked me to defend their position I would do so and be on their side. 

Humm.....

and I beg all of the responders who used language such as "...this is mental mustr...ion...", or "...you are mincing words..." or some other similarly offensive language to be a little more tolerant and respectful of other's opinion even if they dislike it.

@Backgammoner:  Sorry if I offended you (or anyone else).  That was certainly not my intent.

I am a Land Use Consultant and I work regularly with many design, technical, and legal professionals.  Many of us use that particular term in our casual conversations as a sort of slang description for the behavior I was describing.  Its a pretty widely used term, and if you search for it, you will find many definitions for it that are all consistent.

Here's one definition:

"Intellectual activity that serves no practical purpose."

I used that term because I think it precisely describes your posts in which you have gone to extensive lengths to make esoteric arguments about why something that is clearly a bug is somehow not a bug.  And you have done this despite the fact that it doesn't make any difference to the thousands of people who are adversely affected by it.  Also, I still disagree with even your highly technical arguments about this.

I think part of what you are seeing is that there are huge numbers of people for whom Apple's completely thoughtless design and careless implementation in iOS 8 Calendar has been extremely disruptive and irritating.  I am one of those people.  When a guy shows up and then tells all of us that really, we are all mistaken and that this issue is really "technically correct" and that there isn't anything wrong with what the Calendar is doing..we just don't understand it, the natural response is that people get ***** off.

I deal with people, and have to try to predict their reactions to arguments I make, for a living and therefore I am totally unsurprised that this has been people's reaction to your posts.  Sometimes people say stuff when they are ***** off that might sound insulting.  That's unfortunate, but it is predictable.  I'm not claiming that this makes it OK, just giving you an explanation for it.  I am sure it feels like a personal attack but in most cases it really isn't, it's more general frustration towards Apple, but its coming out in response to your posts.

Apple's handling of this has been totally sub-par.  It demonstrates a complete lack of leadership and accountability.  It demonstrates that Apple has total disregard for its customers:  it is far more important to Apple to try and maintain an appearance of being infallible than it is to simply acknowledge an obvious mistake they made and provide a timeline for a solution.  No one would knock Apple for acknowledging and fixing a mistake.  In fact I tend to have MORE confidence in companies that admit errors and then move to address them quickly, not less.  I feel like we are dealing with a stubborn teenager who knows he has done something totally stupid but instead of just saying "I screwed up, I'll make it right" keeps ignoring the issue or trying to argue that he didn't screw up at all.  This is a joke, and it's  insulting to me and a lot of other Apple customers.

<Edited By Host>

@JG in SB thanks for your post, I appreciate it!

I am 100% with you that Apple's handling of this situation is sub-par and disrespectful to its customers, at least their support folks are aware of it and communicate that something is in the works, that was the response I got yesterday when chatting with a customer rep.

For what ever it's worth I am currently using the switch to All-day and back trick as a workaround, it is ugly and irritating but achieves its purpose of getting rid of the GMT non-sense and takes only few more strokes to enter a new event and needs to be done only once.

Siri just found me a couple of links to discussions of this problem. It does appear she knows of it even if the geniuses don't!

Jeremy

Apple Support Communities - Terms of Use

https://discussions.apple.com/static/apple/tutorial/tou.html

<Edited By Host>

can anyone ANYONE FIX THIS PROBLEM. Changing all my events to GMT. Have tried everything above with no resolve. Help.

I was bored and read all the posts here. Jeez what a nightmare. I continue to have the issue even with 8.1.3. You'd think at least one of R&D's chief software architects would have encountered this bug with their own calendar, months ago. Maybe they don't eat their own dog food at Apple.

Yes. Apple can. However, it will be several months before we hope to see this fixed.  The current hope is April. Circa iOS 8.2.

It's more likely that Apple employees don't use Google Calendar or Exchange.  Therefore, they don't encounter the problem.

FWIW it appears new events created post-8.1.3 are not being affected yet by the GMT bug when I edit them. Events created before I upgraded to 8.1.3 are still obviously affected.

Even with the new iOS update...it it still doing it in my end.... 

Apple please address this issue ASAP, it's really a serious BUG and making calendar mtgs very confusing, cannot believe that it wasn't at the top of 8.1.3 bug fixes

I have to agree. Look at what Marriott did today. Their CEO finally stated that wifi blocking was viewed as anti customer, greedy, and that Marriott "failed" but at least wanted to do it fast. They have pulled the wifi blocking request from FCC application and admitted that they were wrong.

They (Marriott) are 100% customer/consumer based firm and realized their policy had backfired. The iOS GMT issue is appalling and Apple should do the same, "we are sorry that we have not adequately addressed this bug and will do so in the next iOS release" : simple, truthful, and customer focused.

Not so hard.

I tested with new events following 8.1.3 and it is still doing it on my setup.

In other news, I was at my local Apple Store yesterday and can confirm there has been sort of a "Sea Change" with regard to this issue.  Every Apple employee I spoke with yesterday was familiar with it.  Compare that with two weeks ago when they still claimed they had never heard of this.

The one guy I spoke with at length said he was well aware of it, that many people had come into the store reporting the same thing, that the Geniuses at the store were all aware that this is a bug, and that many of his friends (who are also experiencing this bug) were asking him about it since he works for Apple.

You seriously have to wonder if all this occurred just in the last two weeks.  Or whether this has been going on for months and the only thing that has changed is an Apple policy that now allows their employees to acknowledge this problem exists.......

Either way, I consider that progress.

Hello,

same problem... After having spent hours trying different settings or called Apple helpdesk where I got stupid people on the line pretending I was the only one to have this problem I finally understood ( - by the way the support is really useless as their only "solution"  - that wouldn't have worked - was to completelly re-initialise my phone!).

Problem : Whatever the device used (iphone, Ipad, ...) if you are using IOS8xx with a sync account on Google or Exchange, you'll have the problem as soon as the calendar entry was enterred on the device side (not in Google) and when it is synchronized.  It's well explained here in this video : http://youtu.be/cgP1zyi_iV8

If you search the web for "IOS8 GMT bugs" you'll find thousands of people in many countries having this problem. What is also frustrating (reading the forums) is that a lot of people that have contacted Apple's help line have been told that it was a Google problem and not an Apple problem... so it is Google that would have to provide a fix !!!??

Google sync was working with IOS7, it is working with a Samsung or Windows device, it is NOT working since the IOS8 update and Apple pretends that the problem is not on their side !!! It's really a SHAME... !!!!

-------------

update : Just installed IOS 8.1.3 and................ NOT FIXED !!!!!!!

I'm disgusted....