Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google workingLocation fix part II: 2-way sync for recurring series #1843

Closed
phw198 opened this issue Apr 21, 2024 · 2 comments
Closed

Google workingLocation fix part II: 2-way sync for recurring series #1843

phw198 opened this issue Apr 21, 2024 · 2 comments
Assignees
Labels
bug Something's not working right resolved Working hotfix available
Milestone

Comments

@phw198
Copy link
Owner

phw198 commented Apr 21, 2024

OGCS Version: v2.10.4.0
Sync Direction: O<->G

Bug Description
OGCS is not able to update a Google "working location" recurring event that starts before the date range being synced.

Steps to Reproduce the Issue

  1. Sync a working location series G->O before v2.10.4 prevented this.
  2. Modify the series in Outlook somehow
  3. OGCS fails to sync the modification back to Google.

Any other information
📎 Attach your OGcalsync.log file.
OGcalsync.log

2024-04-15 09:38:14,380 DEBUG  14 OutlookGoogleCalendarSync.GoogleOgcs.Calendar [797] -  Processing >> 20.01.2023 (R) => "Zuhause"
2024-04-15 09:38:14,382 DEBUG  14 OutlookGoogleCalendarSync.Recurrence [32] -  Creating Google iCalendar definition for recurring event.
2024-04-15 09:38:14,391 DEBUG  14 OutlookGoogleCalendarSync.Recurrence [48] -  RRULE:FREQ=WEEKLY
2024-04-15 09:38:14,393 WARN  14 OutlookGoogleCalendarSync.GoogleOgcs.Calendar [1042] -  Evading Google bug - not allowing default calendar notification to be (re?)set for all-day event.
2024-04-15 09:38:14,394 DEBUG  14 OutlookGoogleCalendarSync.Console [348] -  Recurrence: RRULE:FREQ=WEEKLY;BYDAY=FR => RRULE:FREQ=WEEKLY
2024-04-15 09:38:14,395 DEBUG  14 OutlookGoogleCalendarSync.Console [348] -  Privacy: public => default
2024-04-15 09:38:14,395 DEBUG  14 OutlookGoogleCalendarSync.Console [348] -  Free/Busy: transparent => opaque
2024-04-15 09:38:14,395 DEBUG  14 OutlookGoogleCalendarSync.GoogleOgcs.Calendar [1071] -  Saving timestamp when OGCS updated event.
2024-04-15 09:38:14,595 FAIL  14 OutlookGoogleCalendarSync.GoogleOgcs.Calendar [2243] -  The service calendar has thrown an exception. HttpStatusCode is BadRequest. A working location event must have a transparency setting of transparent.

Originally posted by @lestarte and @hakarune in #1817 (comment)

@phw198
Copy link
Owner Author

phw198 commented Apr 21, 2024

📦 This should now be resolved with hotfix v2.10.4.3.zip (see instructions for applying).
      CRCs: Zip = 2F1A77F7 Exe = D3E9327B

Please note, because working locations are not supported, it will mean that any that have been synced to Outlook whilst using OGCS v2.10.3 or earlier will now be removed from Outlook.

@phw198 phw198 added the waiting fix confirmation Hotfix available for testing label Apr 21, 2024
@lestarte
Copy link

lestarte commented Apr 23, 2024

@phw198 Thanks, Paul.
It works smoothly again, finally :)
And the old ones were safely removed from Outlook, too.
Damn you, Google!
Praise you, OGCS / Paul!

@phw198 phw198 added resolved Working hotfix available and removed waiting fix confirmation Hotfix available for testing labels Apr 27, 2024
@phw198 phw198 added this to the v2.10.5 milestone Apr 27, 2024
@phw198 phw198 closed this as completed in 2da41e1 May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something's not working right resolved Working hotfix available
Projects
None yet
Development

No branches or pull requests

2 participants