Bugzilla – Bug 122
Cannot sync contacts with Android when birthday is defined
Last modified: 2014-06-18 07:33:05 CEST
Zimbra : Release 8.0.6.GA.5922.UBUNTU12.64 UBUNTU12_64 FOSS edition.
Kernel : 3.2.0-60-generic #91-Ubuntu SMP Wed Feb 19 03:54:44 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Mobile terminal : Wiko Cink Five Version 8 (Android 4.1.2 / Kernel 3.4.5)
When syncing a zimbra account with this android 4.1.2, if at least 1 contact has a birthday defined, the sync will fail for all contacts (without error message).
As soon as I remove all birthday in every contacts, sync works well.
I use the default mail, calendar & address book applications.
The bug occurs with both 1.8.13 and 1.8.15 releases of ZeXtras.
I can't upgrade to kitkat as Wiko doesn't provide this version for their phones.
I don't know what kind of traces, logs, screenshots you need for investigating, please ask, I'll do !
your issue seems similar to that reported here:
Please take a look at informations requested on that similar case for more investigations.
Created attachment 25 [details]
Log for contact sync issue
Created attachment 26 [details]
Log for mail issue
Well, it's getting worse, I also notice it's impossible to download attachements in mails...
** bugAndroidMail.log shows the problem with the attachements :
info GetAttachment: Attachment reqested: 2
warn GetAttachment: Requested attachment id 2 is not valid.
=> Same mailbox works perfectly on an iPhone
** bugAndroidContact.log shows the problem with the contacts. About this point, I checked what we were using before switching to ZeXtras : Z-Push+Zimbra backend. In the code, I can find this comment :
"Limiting Birthday to Nokia/Apple as Android constantly tries to resync the contact if it sees a birthday field"
Searching on Internet shows android seems to have an issue with birthday field. I'd be happy if you could find a workaround, but if not, better to disable this field when syncing with android...
Additionnally, I have to say if I configure the android device to use the old ZPush inplace of ZeXtras, I can display attachement correctly.
Regarding the attachement issue, I found something in the URLs. I tried with 2 different devices. Both are Android 4.1.2.
On the Samsung device, the URL is :
On the Wiko device, the URL is :
We can notice the AttachmentName= parameter is different.
What I can guess from that is, despite the OS seems to be the same version, it seems there are different implementations.
Z-Push seems to be able to handle both, tt would be nice if ZeXtras could do the same.
The issue is currently being analyzed, will report back ASAP
Created attachment 27 [details]
Log after switching to EAS14
After switcing the account to EAS14 as suggested by Cine, no more issue with attachements. Thanks a lot !
I've attached the log of this successful sync as requested.
The only issue remaining is the sync of contacts having a birthday : If at least a contact has a birthday, sync fails for all contacts.
Issue resolved (added a server-side workaround to an Android out-of-spec behaviour).
Fix pushed to the production branch, it will be included in ZeXtras Suite 1.8.16.
Created attachment 29 [details]
Test Sync without birthday
Created attachment 30 [details]
Test Sync with birthday
For me, the issue is not solved, or something specific must be configured but I don't know what.
Version installed :
Attached, 2 logs. One (test_no_birthday_anon.log) of a sync with no birthday in contacts, the other (test_birthday_anon.log) with a birthday. The result shows, in the second log, the birthday is still sent to the android device, resulting in a failure of address book sync on device :
Line 330: <n3:Birthday xmlns:n3="Contacts">1981-03-19</n3:Birthday>
Copyright © 2017 ZeXtras, All rights reserved.
Zimbra is a trademark of Zimbra Software, LLC.
ActiveSync is a registered Trademark of Microsoft Corporation