-
All replies
-
Helpful answers
-
Jan 20, 2015 9:31 AM in response to James Barberby joegrant,I found a solution! If you throw your i-device at the ground really hard, the incorrect timezone no longer displays. However, nothing else displays either. Come on Apple, this needs to be addressed. I miss at least one appointment a week because my calendar doesn't show the right time on the appointment, which is bad for my business.
(WARNING: Do not follow the advice from this post. I am being sarcastic.)
-
Jan 20, 2015 9:53 AM in response to nayo2002by nayo2002,nayo2002 wrote:
i found a way to fix it. Go to google calendar on Safari. It will ask you to upgrade to the latest version and set your time zone on the top of the web page. After you do both, the problem will go away. It seems like it's a Google Calendar update that cleared out your default time zone so it's showing GMT time on devices.
As a clarification. You need to go to the non-mobile version of Google calendar via iPad or a computer. This worked on all my devices. Can someone else check?
-
Jan 20, 2015 9:53 AM in response to joegrantby BobH1.3.4.5,joegrant,
Ha! .... Your fix at least would provide consistent results for everyone!
-
Jan 20, 2015 9:57 AM in response to thekingfishh225by JDM004,The issue is with Google Calendar & while I have no idea how to solve it, it is at least explained by Google Calendar here, as to why they use GMT always...
-
Jan 20, 2015 7:05 PM in response to nonomeoggiby Indros,I also followed the strategy of logging in to iCloud and changing the timezone setting. It seems to have worked on an iPhone 5c, iOS8
-
Jan 20, 2015 8:58 PM in response to Indrosby Lameduck,FYI .... IMHO... per other posts over the past 90 days --- the root case issue is with iOS entries created using the Calendar App. This app has a BUG and Apple is well aware of the problem... and they will hopefully address it with the next iOS 8.x release (crossing my fingers).
INTERIM SOLUTION -- until Apple fixes this horrible BUG -- Just DITCH the iOS 8.x Calendar app... and move to another iOS calendar app
Three calendars that seem to be working fine (tested on my 4 accounts -- 3 Office365 and 1 MS Exchange) are:
+ Calendars 5 (Readdle)
+ Calendar+ (Readdle)
+ Acompli
While not ideal -- these apps "do the job" and are a good bridge solution until Apple addresses the GMT Bug from ****.
-
Jan 20, 2015 9:15 PM in response to Lameduckby Dave Carta,Sunrise Calendar works well too.
I believe in order for an app to bypass the problem, it must interface directly with -- that is, explicitly log into -- your calendar service (Google, Exchange etc.). An app like Fantastical (a great app in its own right) won't solve the problem since it's the same iOS calendar on the back end.
-
Jan 20, 2015 9:52 PM in response to James Barberby TheIssa,I switched to an iPhone 6 from a 4s last week. I'm having the same issue as everyone else here. I've read through this and many other posts trying multiple things to fix the problem. The only thing that "works" are some of the workarounds listed here. Nothing really fixes the problem, and the workarounds are complete hassles for someone booking lots of appointments. I use the calendar for a busy work schedule and have too many appointments to go through and fix all of them individually. So far, I'm really disappointed in Apple and the new iPhone. There seem to be a lot of bugs.
Also, for the record, I have an iPad that I haven't updated the software on that doesn't show the GMT issue, and neither did my old iPhone 4s. However, if I create an appointment on my iPad it will show on my iPhone 6 with the GMT issue. Now I'm afraid to update the software on my iPad.
-
Jan 21, 2015 5:16 AM in response to nayo2002by nayo2002,nayo2002 wrote:
nayo2002 wrote:
i found a way to fix it. Go to google calendar on Safari. It will ask you to upgrade to the latest version and set your time zone on the top of the web page. After you do both, the problem will go away. It seems like it's a Google Calendar update that cleared out your default time zone so it's showing GMT time on devices.
As a clarification. You need to go to the non-mobile version of Google calendar via iPad or a computer. This worked on all my devices. Can someone else check?
Has anyone tried this? It works on all new calendar entries. Existing entries will still show GMT
-
Jan 21, 2015 10:46 AM in response to nayo2002by The-Organist,Events created inside the Exchange or Google Calendar itself seem not to have the issue that creating them on an Apple device generates. So, because your suggestion is to add the event using calendar.google.com, it works as you say. However, it's not always practical to create the event on Safari. I still need the fix.
-
Jan 21, 2015 12:30 PM in response to James Barberby Olio,Same problem on all our iOS devices. This is strictly an iOS 8 error. We've ruled all else out.
Not due to Time Zone changes or "Time Zone Override"; none of the proposed fixes here work.
We're in the Pacific/"Cupertino" time zone. All Calendar events we create on our iPhones, iPads and computers (using iCal) show up correctly in our time zone on our computers (both in iCal and in Google Calendar on the web).
But events that use Google calendar accounts show up incorrectly on all of our iOS 8 devices: they switch to the GMT time zone. In some Calendar views, both time zones appear. This never happened before iOS 8 (or perhaps 8.1), and nothing else has changed.
NOTE:
1) We never leave the Pacific/"Cupertino" time zone, and have never set our time zones differently.
2) We've never used Time Zone Override.
3) When we create an event (whether using iCal or the iOS Calendar), our correct time zone is the only one displayed. But it switches to GMT in Calendar after the event is created.
4) Those same events still display correctly on iCal and in Google Calendar online. It's strictly an iOS 8 glitch.
5) We've tried every fix people have suggested here, including correcting an event's time zone, resetting iCloud, iOS and Google Calendar time zones, reinstalling, whispering sweet nothings into Siri's ear... nothing works.
This glitch renders the Calendar fairly useless. Needs a fix from Apple.
ETA: Yes, we've sent Apple Feedback on this. Everyone should:
-
Jan 21, 2015 12:30 PM in response to nayo2002by Olio,nayo2002 wrote:
i found a way to fix it. Go to google calendar on Safari. It will ask you to upgrade to the latest version and set your time zone on the top of the web page. After you do both, the problem will go away. It seems like it's a Google Calendar update that cleared out your default time zone so it's showing GMT time on devices.
As a clarification. You need to go to the non-mobile version of Google calendar via iPad or a computer. This worked on all my devices. Can someone else check?
Sadly, this didn't work for us.
-
-
Jan 21, 2015 2:27 PM in response to James Barberby TheIssa,I spent about an hour last night chatting with Apple support. They blame it on the fact that Google uses GMT, which if you follow the link a few posts up you will see a solid explanation of why they do. In fact, I was directed to the same link by Apple. Apple said it's because they use "a more sophisticated way of showing the time" in the calendar now (cough, cough...trying to cover up their mistake), so that's why devices using iOS 8 are experiencing the problem. Um, news flash: it's not more sophisticated if it doesn't work. It worked fine before and nothing with Google has changed. It's an Apple problem, and after working my way up to a supervisor last night I was told their engineers are working on a solution, but don't have a time frame for a fix. So, for now I'm trying Sunrise. So far so good.
-
Jan 21, 2015 3:19 PM in response to TheIssaby Olio,TheIssa wrote:
I spent about an hour last night chatting with Apple support. They blame it on the fact that Google uses GMT, which if you follow the link a few posts up you will see a solid explanation of why they do. In fact, I was directed to the same link by Apple. Apple said it's because they use "a more sophisticated way of showing the time" in the calendar now (cough, cough...trying to cover up their mistake), so that's why devices using iOS 8 are experiencing the problem. Um, news flash: it's not more sophisticated if it doesn't work. It worked fine before and nothing with Google has changed. It's an Apple problem, and after working my way up to a supervisor last night I was told their engineers are working on a solution, but don't have a time frame for a fix. So, for now I'm trying Sunrise. So far so good.
Well at least that's an answer: We're not really acknowledging it's our glitch but we're quietly working on it, and have no ETA for when we might have a fix.
Thanks for sharing, Thelssa.