[kronolith] Kronolith - Birthdays off by one day

[Michael J Rubinsky]

Quoting John H. Bennett III <bennettj at thebennetthome.com>:

> Quoting Michael J Rubinsky <mrubinsk at horde.org>:
>
>> Quoting John H. Bennett III <bennettj at thebennetthome.com>:
>>
>>> Quoting Simon Wilson <simon at simonandkate.net>:
>>>
>>>>> Hello,
>>>>>
>>>>> I've stumbled across a problem that I don't know what's going on.
>>>>> I've added birthdays to some of my contacts, I put them in with the
>>>>> correct date, but some time in the future, I look at them on the
>>>>> Calendar, and some show a day off (ahead one day).  I edit them in
>>>>> turba again, and again some time in the future some are off a day.
>>>>> This has happened 4 times in the last 2 weeks.
>>>>>
>>>>> I don't know what's triggering this. Anyone else seeing this?  What
>>>>> can I look for to help try to explain this.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> John
>>>>>
>>>>> --
>>>>
>>>> There has been discussion on this in the past on the list...  
>>>> mostly around birthdays syncing incorrectly through ActiveSync  
>>>> and back.
>>
>> If this is due to ActiveSync, it should only affect the contacts  
>> that have been edited on the client. Is that what you are seeing?
>>
>>
>> -- 
>> mike
>> The Horde Project
>> http://www.horde.org
>> https://www.facebook.com/hordeproject
>> https://www.twitter.com/hordeproject
>
> Hi Mike,
>
> Yes, that is what I am seeing.  I made a change to my contact info  
> on my Note 3, then the next sync period, my birthday was off by one  
> day earlier.  I made a change to my Wife's contact info within  
> turba, and all was good.  So for now, I'll try to remember to make  
> all contact changes within Turba.  Not real fun when the wife checks  
> the calendar and sees that her birthday showd up a day earlier,  
> questioning and thinking I didn't know when it was.

This is basically an issue with the EAS protocol. Without getting too  
much into it, the protocol defines the birthday field as a datetime  
(so it is required to be transmitted as a full datetime in UTC) but  
yet doesn't offer any standard time of day to represent the birthday  
as. Different clients seem to expect the birthday to be represented at  
a different time of day, so when the UTC <-> local time conversions  
are done multiple times, the date can creep. We already work around  
this in code for some clients that this has been reported for. I'll  
see if I can figure out the offset required for the Note 3.




-- 
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5869 bytes
Desc: S/MIME Signature
URL: <http://lists.horde.org/archives/kronolith/attachments/20140919/02febf57/attachment-0001.bin>