Upload to Google failed

[Julien Cubizolles]

I see a lot of sync errors between bbdb and google with this error message:

[18:01:34.617 ERROR] Upload to Google failed for: John Doe: Reason: If-Match or If-None-Match header or entry etag attribute required. Code: SYNC_FORBIDDEN

What does it mean ?

I'm running the bbdb-phones branch.

Julien.

[Sriram Karra]

The duplicates is because of these sync errors.

The error message you point to started appearing suddenly due to some change in Google's contacts api implementation. I have tried various hacks mentioned around the net but nothing has really worked. This has been the situation for a few months now.

I am sorry about the duplicates after sync error - those should be handled better.

--
You received this message because you are subscribed to the Google Groups "ASynK Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to asynk+un...@googlegroups.com.
To post to this group, send an email to as...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/asynk/87ha10h6vo.fsf%40free.fr.
For more options, visit https://groups.google.com/d/optout.

[Sriram Karra]

I was just catching up on the status of the ticket at google's end, and a work around has been suggested which sounds promising. I will explore this over the next few days

https://code.google.com/p/gdata-python-client/issues/detail?id=700&thanks=700&ts=1401265148

[Julien Cubizolles]

Sriram Karra <karr...@gmail.com> writes:

> I was just catching up on the status of the ticket at google's end, and a
> work around has been suggested which sounds promising. I will explore this
> over the next few days
>
> https://code.google.com/p/gdata-python-client/issues/detail?id=700&thanks=700&ts=1401265148
>
>

I'm looking forward to try it. Feel free to request my assistance in
testing it.

Julien.

[Sriram Karra]

I have pushed fix to a new branch (gdata-bug). Can you give that a try, Julien? 

The main problem seems to be fixed with this work around, but Google's servers are still causing an issue, where after a sync they keep insisting that the contact has changed on the server. Will have to investigate that separately, perhaps. 

Note: I have updated the google contacts api to a more recent version and added it as a new submodule instead of including the entire sdk directly in the repo. So you may want to just do a full clone for your tests.