End date bug at recurring events

[GoogleCodeExporter]

When you create recurrent whole day event and sync it with kolab-android all 
seems fine. But with the next sync the event changes and the END param has 
wrong date as follows:

ABC
Location: null
Start: 0:00:00 13. 5. 2011
End: 0:00:00 31. 12. 1969
Recurrence: FREQ=MONTHLY;WKST=MO;BYMONTHDAY=13

The corresponding kolab.xml contains same values.

Original issue reported on code.google.com by milan.be...@siphone.cz on 12 May 2011 at 9:38

• Merged into: #23

[GoogleCodeExporter]

Original comment by arthur.z...@gmail.com on 20 May 2011 at 12:59

• Changed state: Accepted
• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Please upgrade to the latest Version. I can't reproduce the error.

Original comment by arthur.z...@gmail.com on 20 May 2011 at 3:24

• Changed state: WontFix

[GoogleCodeExporter]

Had that issue on my Phone too. Trying to reproduce.

Original comment by arthur.z...@gmail.com on 23 May 2011 at 7:57

• Changed state: Accepted
• Added labels: Priority-Critical
• Removed labels: Priority-High

[GoogleCodeExporter]

My Issue was with my Outlook-Kolab sync tool. With what other Tool do you sync?

Original comment by arthur.z...@gmail.com on 24 May 2011 at 5:41

• Changed state: WontFix

[GoogleCodeExporter]

Hi,
unfortunately the issue persists. We are using Kontact, Android 2.2 and latest 
KolabDroid-0.7. It does not happen immediately but during next couple of syncs.

How could we assist to identify the issue?

Milan

Original comment by milan.be...@siphone.cz on 26 May 2011 at 2:36

[GoogleCodeExporter]

Who changed the event? Kolab-Android or Kontact? A possible way to reproduce 
the issue would be to track every XML document to see, who is updating the 
wrong values. 

Changing Status to New.

Original comment by arthur.z...@gmail.com on 27 May 2011 at 7:28

• Changed state: New

[GoogleCodeExporter]

Original comment by arthur.z...@gmail.com on 29 Jun 2011 at 8:10

• Changed state: Duplicate

[GoogleCodeExporter]

I can reproduce this issue. It seems that the Android calendar is the source of 
this problem. I have a TestCase here that inserts a recurring event with proper 
end date and retrieves it again right afterwards with end date 0. My TestCase 
currently uses a few internal methods of KolabDroid, that's why I cannot check 
it into Git yet. I'll work on it though since this issue is really annoying. 

Original comment by tolang...@gmail.com on 28 Sep 2011 at 10:32