-
All replies
-
Helpful answers
-
Jan 12, 2015 8:04 AM in response to abubasim66by JG in SB,Thanks for the link!! This is the first story I have seen which actually identifies a projected release timeframe. Let's hope this update includes the real fix for this issue!
-
Jan 12, 2015 9:51 AM in response to jaw444by klare9,This explanation & info for a solution (temporary solution of course, until apple fixes this!) was the most helpful thing I read on this discussion. I put an iCloud calendar as my default and the whole issue with the GMT showing up was gone! Thank goodness!!! And like you said, events that were created during the time where GMT did show up, I simply went in and deleted them completely and re-entered them.
Thanks for the detailed info!
-
Jan 13, 2015 7:34 AM in response to Whimsy Collectiveby Whimsy Collective,FYI, there's Google Groups post on this as well.
Google Groups Gmail Help: https://productforums.google.com/forum/?hl=en#!topicsearchin/calendar/clock$20in %7Csort:relevance/calendar/CaPn0hLOU0c
Another option that didn't work.
Settings > Privacy > Location Services > System Services (scroll all the way to bottom) > Setting Time Zone (off/on)
I toggled this option and still the issue persist.
-
Jan 13, 2015 10:47 AM in response to Whimsy Collectiveby BobH1.3.4.5,iPad screenshot here. Shows what is going on for me using Google Calendar as my calendar sync source. Any calendar events made with Apple devices, which then are viewed on iOS (iPad) show GMT. Events made on Android or directly on Google Calendar display .... BUT they don't show any time at all.
Calendar events viewed on my Mac (Yosemite) all show correct (local) time and not the GMT for all events no matter where they were created.
-
Jan 13, 2015 3:05 PM in response to JG in SBby kcf316,It stems from Gmail. Go to your gmail, open your calendar settings, and change your timezone. Hit save and boom! you're done
-
Jan 13, 2015 3:11 PM in response to kcf316by MDC17,Didn't spend much time reading the prior 30+ pages in this thread did you kfc316?
-
Jan 13, 2015 3:14 PM in response to MDC17by kcf316,not as much time as you spent waiting to pounce on someone trying to help others. must be a nice life
-
Jan 13, 2015 3:44 PM in response to kcf316by Ghupka,For God's sake people, read the earlier messages!
A dozen people come on here every day saying "I've solved the problem!" and it's always something that someone already tried two months ago and has been demonstrated to NOT solve the problem.
The problem can only be solved by Apple in an OS update. Period.
-
Jan 13, 2015 5:04 PM in response to Ghupkaby kcf316,Or by changing your gmail calendar settings, like I wrote.
-
Jan 13, 2015 5:15 PM in response to kcf316by Ghupka,kcf316, that is one of the FIRST things I tried several weeks ago. FYI, my gmail calendar settings were always correct. This does not solve the problem. Nor does it solve the problem for the many people who use Exchange servers etc.
Read the detailed information that is available on the links earlier in this thread.
-
Jan 13, 2015 5:22 PM in response to kcf316by darylefromjacksonville,Unfortunately kcf316 the GMT bug occurs on phones where the user does not use Gmail or a Google calendar at all. The exact same problem happens to people using only Outlook. I also use Gmail and uninstalling gmail from my phone and reinstalling Gmail fixed the problem for me --- for about 3 days and "the bug" reappeared again. This time uninstalling gmail and reinstalling it ... or trying your fix ... did not work. For some reason IOS starts using the time of the server (whatever time the server for your particular email service uses (London time for some, EST for some and GMT time for others). At this point Apple has acknowledge they have a problem and we are expecting a software update that MAY address this issue within a week or so. Apparently they have already pushed the update out to some Beta testers as reported in other threads discussing this issue. I'm glad changing your calendar settings fixed your phone -- for the moment -- but that is not the permanent solution we need. Only Apple can fix the core problem ....
-
Jan 13, 2015 6:49 PM in response to kcf316by abubasim66,The time zone setting in my Google calendar settings is already correct. If it weren't, the problem would affect all my devices. As it is, it now affects my iPhone 5s (iOS 8.1.2) and MBP (10.10.2 beta) but not my iPod Touch 4th gen (with iOS 6.1.6) and not my Asus NPFI running KitKat.
-
Jan 13, 2015 7:05 PM in response to kcf316by freedomgli,kcf316 You are dead wrong. Stop giving bad advice.
-
Jan 13, 2015 8:42 PM in response to freedomgliby Bcutty,We all know the only fix is Apple and we all hope they will fix it in 8.1.3 but we also know that some people have done different things that may have fixed it on their devices but will not work for other people. Kcf316 was only trying to help we don't have to pile on. At this time we are all just waiting on Apple as the only real fix so let's all just chill.
-
Jan 14, 2015 1:55 AM in response to James Barberby vmaxxx,Actually, I am leaning towards Google being the source of this problem, and not Apple. When sniffing traffic between iOS device and Google Calendar while the events are synchronizing, I see that iOS is sending well-formed iCalendar request, which contains VTIMEZONE section and start & end times contain correct timezone: DTSTART;TZID=Europe/Berlin:20150115T090000.
However, when Google sends event confirmation, it is omitting VTIMEZONE section and instead sends timezone info only in X-WR-TIMEZONE element, which is not a standard one (per iCalendar specifications), and dates are in UTC: DTSTART:20150115T080000Z.
iOS 8 EventKit and/or MobileCall app probably cannot recognize X-WR-TIMEZONE element, so the calendar event timezone gets updated to GMT (probably system default when no timezone info is present in server reply). Changing timezone back to Europe/Berlin (in this example) in EventKit Calendar.sqlitedb database fixes the problem for the event (GMT time will not be shown, and editing the event will show the correct timezone).
The fix for this needs to be either by Apple (add ability to parse non-standard X-WR-TIMEZONE element), or by Google (adhere to iCalendar standard when sending calendar replies/confirmations, and send timezone info in VTIMEZONE section).