Mobile (CardDAV/ActiveSync) data corruption

Take your Zimbra with you!
jesquivel
Posts: 2
Joined: Sat Sep 13, 2014 2:38 am

Mobile (CardDAV/ActiveSync) data corruption

Postby jesquivel » Sat Jun 09, 2012 5:31 pm

Have anyone found a work around for the Zimbra's CardDAV data corruption problem? Or what do you think is the best alternative Funambol or ZeExtras?
Thanks


ewilen
Elite member
Elite member
Posts: 1429
Joined: Fri Sep 12, 2014 11:34 pm

Mobile (CardDAV/ActiveSync) data corruption

Postby ewilen » Tue Jun 26, 2012 1:21 pm

I'm moving this thread to the CardDAV forum since it doesn't have to do with mobility specifically.
Now, what CardDAV data corruption problem are you referring to? Is there another thread, a link to an outside discussion, or a bug report?
Please see my signature regarding identifying your Zimbra version.
jesquivel
Posts: 2
Joined: Sat Sep 13, 2014 2:38 am

Mobile (CardDAV/ActiveSync) data corruption

Postby jesquivel » Tue Jun 26, 2012 2:09 pm

It is Bug#: 75211


Thanks
ewilen
Elite member
Elite member
Posts: 1429
Joined: Fri Sep 12, 2014 11:34 pm

Mobile (CardDAV/ActiveSync) data corruption

Postby ewilen » Tue Jun 26, 2012 4:11 pm

Thank you. Now that I understand the bug I agree this is a general mobile issue and I'm moving the thread back there.
For the benefit of others, bug 75211 is "irretrievable data loss while syncing contacts". From comments,[QUOTE]This occurs whenever User syncs Zimbra contacts with mobile device (or third

party app), edits upon mobile device, and syncs back.

This is due to Zimbra contact field data being removed and lost following

editing on mobile devices.

See attached chart for detail of what fields are failing to sync or sync back.

As can be seen from the chart, this data loss occurs with both Activesync and

CardDav
sync methods.[/QUOTE]
Unfortunately, I don't have a workaround, and I'm also somewhat disappointed that the target milestone is IM rather than Helix.
I'm not even sure that Funambol or Zextras would fix the problem.
At this point all I can suggest is voting for the bug and (if you care) requesting that any solution be back-ported to Helix if possible.

Return to “Mobility”

Who is online

Users browsing this forum: No registered users and 3 guests