#1408 Version 4.2.1 duplicate contact and conflict of commitments

[FABIO FURLAN DE CARVALHO]

After last update version 4.2.1 When synchronizing Google with Outlook, it is duplicating contacts and finding birthday reminders as conflicts without having made any changes in Outlook or Google, every time the synchronization is run, and it presents as a conflict but with identical information between Outlook and Google. This only started to happen after the last version update.

[James]

I have similar issue with latest version 4.2.1 and 4.2.0 - I've downgraded to 4.1.33 and syncing is quick again. Hopefully this can get resolved in future releases. If it helps, I am using Microsoft® Outlook® LTSC MSO (Version 2502 Build 16.0.18526.20286) 64-bit

[bennor3814]

Can confirm. Both 4.2.0 and 4.2.1 have the issue in my setup. Downgrading to 4.1.33 and the sync runs correctly, without this issue.

[Gregory Brown]

I'm having the same issue too. I tried deleting the birthday appointment on both Gmail and Outlook, but syncing again gives the below prompt every time:

"Both the Outlook and Google Appointment "XYZ's Birthday - 2000-12-31 Recurrence" have been changed. Choose which you would like to keep"
"Keep Outlook Entry" or "Keep Google Entry" or "Skip" or "Cancel"

(I have both "Sync Deletion" and "Prompt Deletion" checked)

So there's no way to actually remove these birthday reminders with v4.2.1.

Thanks,
Greg

[bennor3814]

Roll back to version 4.1.33 and it should sync properly without the errors one gets n 4.2.1.

[Gregory Brown]

Still no new version released. Has this been acknowledged as a bug to your knowledge?

[bennor3814]

So far as I've seen, it doesn't appear that this bug has been acknowledged by the developer.

This bug apparently has been mentioned in several other open requests in the past:
https://sourceforge.net/p/googlesyncmod/bugs/1411/
https://sourceforge.net/p/googlesyncmod/bugs/1410/
https://sourceforge.net/p/googlesyncmod/support-requests/1026/

I've rolled back to 4.1.33 which doesn't exhibit this issue that 4.2.1 did and just ignore the 4.2.1 update nag message when running/using the program.

[Florian Saller]

I think I found the reason after several internet searches and trying out: Obviously, the hash algorithm we are using to collapse the Google Account name into an Outlook Property name changed between the .NET Framework 4.7.2 (used in 4.1.x versions and earlier) and 4.8.1 (used in the newer versions). Unfortunately we needed to upgrade to 4.8.1 to be on the Microsoft supported Framework, but there seems to be no backward compliance with the hash algorithm.
Please test the version I released here and let me know, if it works https://sourceforge.net/projects/googlesyncmod/files/Releases/4.1.34%20-%20Branch%20for%20.NET4.7.2%20fixes/

Anyway, I would advice you to upgrade to latest .NET Framework to not oppose your system any security threads. To do so, you should install the latest version (4.2.x), then Reset matches first, before resync (maybe, if possible, delete all entries first on one side, Outlook or Google, and then reset, and then start the sync again to copy over a synched version to the other side again)

[James]

Can you verify the link above is for a newer version?

[Florian Saller]

yes, it is the newest version of GCSM, just with Microsoft .NET Framework 4.7.2 with same hash calculation as 4.1.x versions

[FABIO FURLAN DE CARVALHO]

Hello, yes, I tested version 4.1.34 and it still has the same problem as version 4.2.1.

It keeps constantly updating unchanged contacts in all synchronizations even though no changes have been made to the contact.

[James]

Thank you for trying, but I concur with Fabio, 4.1.34 still has the issue mentioned. Went back to to 4.1.33 for now. Appreciate the effort.

[Jason King]

I’m maintaining an unofficial fork of GO Contact Sync Mod because the upstream project appears inactive.

Parts of this report look similar to issues I’ve been fixing in my fork, especially repeated no-change contact re-sync behavior and some profile/folder persistence problems. I would not assume it fixes every appointment/calendar conflict described here, but it may help with the repeated contact update side of the issue.

Current jkfix release:
https://github.com/jaywking/go-contact-sync-mod-jkfix/releases

Source and issue tracker:
https://github.com/jaywking/go-contact-sync-mod-jkfix

It’s an unofficial fork, so please back up first and test carefully. If you do try it, I’d be interested to know which parts of the problem improve and which do not.]