Outlookgooglecalendarsync: All meeting times synced to Google offset by 1 hour (self created, non-recurring)

[Viennasurfer]

OGcalsync.log
:memo: Use the below template to report your issue.
:bulb: Upgrade to the latest alpha release to check if the problem is already fixed.
:paperclip: To aid investigation, provide your OGcalsync.log file (see instructions).

---

OGCS Version: 2.7.2.0 and Outlook installed on PC with Windows 10, Google installed on Portable with Android
Installed or Portable: Installed

Problem Description
We are using daylight saving time in Switzerland. The time entered in Outlook is shown 1hour later in Google. The time shown on the clock in both systems is correct.

Steps to Reproduce the Issue

1. \
1.

Any other information
\

[phw198]

Can you confirm if this only affects recurring meetings organised by someone in another timezone?

[Viennasurfer]

It affects all my (not recurrent) meetings entered by myself before and after the change to DST.

Thanks for your help
Fred

Von: Paul [mailto:[email protected]]
Gesendet: Sonntag, 8. April 2018 22:21
An: phw198/OutlookGoogleCalendarSync
Cc: Viennasurfer; Author
Betreff: Re: [phw198/OutlookGoogleCalendarSync] wrong time in Google (#508)

Can you confirm if this only affects recurring meetings organised by someone in another timezone?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/phw198/OutlookGoogleCalendarSync/issues/508#issuecomment-379583579 , or mute the thread https://github.com/notifications/unsubscribe-auth/AkbCRv3xh6z-K9o9Fm6PhfdILBbXoqr2ks5tmn84gaJpZM4TLsvd .Das Bild wurde vom Absender entfernt.

[Viennasurfer]

Today I have installed your new version 2.7.3.0 but the time in Google is still 1 hour later than in Outlook

[phw198]

Have you performed a full sync by pressing Shift while clicking Sync to fix items already synced? Let me know if that makes any difference on the latest alpha v2.7.4

[ghost]

I had the similar issue using 2.7.0.0-beta

Upgrading to 2.7.5.0-alpha and performing Shift-Sync resolved the issue

Thanks Paul!

[ScottRochford]

Same issue here, also resolved using the 2.7.7.0-alpha and a Shift-Sync.