TB fails to update an existing contact via CardDAV

RESOLVED INVALID

Status

Thunderbird
Address Book
--
critical
RESOLVED INVALID
4 years ago
4 years ago

People

(Reporter: rogr, Unassigned)

Tracking

24 Branch
x86_64
Windows 7

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

4 years ago
Exact Steps to reproduce:

Have Thunderbird 24.2.0 with Inverse SOGo Connector 24.0.2 and a CardDAV Server (we tested with Baïkal 0.2.6 as well as with Owncloud 5.10 and 5.12)
As well as one other (e.g.) Android client syncing via CardDav.

-Generate a NEW contact (e.g. "Kontakt TB3") in TB addressbook, enter a private phone number.
-Sync addressbook with other client, checking new Kontakt TB3 has appeared.
-Then Go back to Thunderbird and edit existing Contact "Kontakt TB3" by changing the private phone number. Click OK to Save.
-Make sure a Sync is performed again.

 => Contact is NOT updated on other clients (e.g. CardDav sync on Android).

Conclusion:
Hence Thunderbird has problems updating an existing contact via the CardDAV protocol.

Is there a workaround for that?

Exact system specs: 
Thunderbird: 24.2.0
Inverse SOGo Connector Thunderbird 24.0.2 (released on November 22nd 2013)
Baïkal 0.2.6 or Owncloud 5.X
Android: CardDAV sync (multiple clients)
Betriebssystem + Version: Windows 7



See also bug report here: http://www.sogo.nu/bugs/view.php?id=2575
(Reporter)

Comment 1

4 years ago
See also bug report here: http://www.sogo.nu/bugs/view.php?id=2575

Bug has been confirmed there by other users.

Absolutely reproducible.


I am not a programmer myself, but I would be happy if the Tb-Sogo developers could look into that.
With the situation as is, CardDAV sync remains absolutely unreliable!
Sorry, but we are unable to handle third-party add-ons and issue - we do not always have access to the source, nor do we have privileges to change their code. Please follow up with the Sogo developers.

If there is a specific fix that they need with in Thunderbird, then we can help them with that in a fresh bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.