Deleting and re-creating the same events

[phw198]

Deleting and re-creating the same events

[phw198]

On 2016-05-20 15:15:07 UTC, phw198 commented:

What version are you on? Please upload your OGcalsync.log file.

[phw198]

On 2016-05-25 19:59:51 UTC, canton7 commented:

I'm seeing the same issue. Log is here (it was too long to paste inline):
https://gist.github.com/canton7/e99d58712acbd3bf702c16d40891b955. Meeting names have been censored.

The appointment in question is "Spring Bank Holiday".

[phw198]

On 2016-07-02 06:17:47 UTC, phw198 commented:

Can any of you confirm if you created these Outlook items by copying them from someone elses Outlook calendar into your own?

[phw198]

On 2016-07-02 20:52:35 UTC, toddhisted commented:

Yes, it was copied from a shared group calendar to my personal calendar.

[phw198]

On 2016-07-04 23:30:22 UTC, phw198 commented:

OK, that's what I suspected - I have a comment in my code saying that the GUID of the Outlook item seems to change on access for copied items. However, I just can't seem to replicate the problem.

Would appreciate it if you could follow these steps to help troubleshoot:

In Application Behaviour, check "Create CSV files" Run the sync to replicate the create/delete issue. Go to where your logfile is stored (eg. %APPDATA%\Outlook Google Calendar Sync)
Zip up the CSV files Repeat another sync and zip the files Attach the zips to the ticket

NB: The only fields I'm really interested in is start, finish, subject, google ID and Outlook ID - you can remove the rest if you like.

Thanks!

[phw198]

On 2016-07-09 18:56:27 UTC, phw198 commented:

Hi - Any update for this?

[phw198]

On 2016-07-11 00:39:17 UTC, canton7 commented:

Sorry, I haven't seen the issue for a while, so I can't reproduce.

For me, I think it was a public holiday appointment, added by telling Outlook to automatically add public holidays.

If I see it again with the Autumn bank holiday, I'll report back.

[phw198]

On 2016-12-04 00:51:23 UTC, phw198 commented:

This should now be fixed with the attached hotfix v2.3.1.1.

[phw198]

On 2016-12-14 23:55:56 UTC, toddhisted commented:

I just tested and can confirm it is working. Thank you!