I just installed a fresh instance of the EssentialPIM 9.9 Pro (so far in the trial mode) and set it up to synchronize with my Google account (mail, calendar, and contacts). It looks like everything has been successfully downloaded but I noticed that contacts are not being synchronized back to the Google Contacts.
The error happens when EssentialPIM tries to upload the changed contact. It's being reported in the synchronization popup dialog and GoogleSync logs contain further details. It seems to be caused by binary image data of the contact photo being improperly encoded by the Base64 encoding.
"error": {<LF> "code": 400,<LF> "message": "Invalid value at 'photo_bytes' (TYPE_BYTES), Base64 decoding failed for <Base64-data>
"status": "INVALID_ARGUMENT",<LF> "details": [<LF> {<LF> "@type": "type.googleapis.com/google.rpc.BadRequest",<LF> "fieldViolations": [<LF> {<LF> "field": "photo_bytes",<LF> "description": "Invalid value at 'photo_bytes' (TYPE_BYTES), Base64 decoding failed for <Base64-data>
It doesn't affect just the contact photo but no other field is being synchronized back to the Google Contacts. It actually looks like the whole synchronization is interrupted by a failure to upload one of the fields of one of the entries in one of the modules. I guess so since that error is the last entry in the GoogleSync log. The very last line contains the following:
If that's the case, I don't think that the interruption of the whole synchronization is the best handling of a failure of the upload of one of the entries.
Will check this, thanks. Meanwhile, you can mark the contact as private, exclude private items from synchronization in options and see if it starts working then.
OK, thanks for the suggestion. I have identified the particular contact that's causing it, so I'll try it to see if it's an issue of that specific contact photo or with contact photos in general.
According to our tests that should be an issue with that particular contact. Although, we found out there were still some adjustments to be made for the sync of pictures with Google Contacts. These changes will be included in the next update. Thanks!
Somehow, I very much doubt that a particular contact causes this problem. In my case anyway.
I happen to experience the same problem.
I used EPIM Portable r 9.6 for quite some time, and never had any problems synchronizing my contacts with Google.
From the moment I upgraded my EPIM Portable from r9.6 to EPIM Portable r9.95, I experienced this HTTP/1.1 400 Bad Request upon synchronizing my contacts. Theproblem also occurs in releases 9.96 and 9.97, but not in 9.6
Sync settings are: One way sync, contacts only.
When rolling back to EPIM r9.6, with the same database, no problem synchronizing whatsoever. So, the database doesn't seem to be the problem.
Also tried to upgrade to EPIM Pro r9.95 (NOT the portable version): Same database, same problem again as the portable version.
Tried to upgrade to EPIM Pro r9.96 (NOT the portable version): Same database, same problem again.
Rolled back to EPIM Portable r9.6, same database, no problem synchronizing.
Tried all this on my second computer: Same problem with EPIM Portable r9.9x and the same database. No problem with EPIM Portable r9.6 and the same database.
,
Last edited by EFvanGelder on Thu Aug 05, 2021 8:19 am, edited 1 time in total.
Ehm......I just may have found a clue to this problem.
I experienced this problem, when I upgraded from EPIM r9.6 to r9.95, r9.96, r9.97.
Since I upgraded to r9.9x I had this http 400 sync problem, every time I tried to synchronize with Google:
On every sync attempt I received a BAD REQUEST error (http 400)
I used to synchronize inidirectional, from EPIM to Google. Apparently. Apparently, that was the cause of the problem.
After I changed the setting to unidirectional, but the other way around (so, from Google to EPIM), the problem as I experienced, was gone.
Several changes in my database were made, i.e. some fieldlabels were added/changed, but those wer minor changes.
When I then changed my settings back to the original settings, i.e. unidirectional from EPIM to Google, the problem did not occur anymore.
At least for me, this remedied the problem. I hope, for others who use to sync their contacts unidirectionally from EPIM to Google, this works too.