search

coscip / kolab-android

Automatically exported from code.google.com/p/kolab-android
Other
0 stars 0 forks source link

Error while syncing calendar entry #85

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. add attached entry to calendar folder on imap server
2. sync this folder

What is the expected output?
Calendar entry in calendar of my phone

What do you see instead?
Syncing stops at entry 2891 of 2956 (which is exactly this file - syncing works 
fine if I delete this file)

What version of the product are you using? On what operating system?
Kolab-Droid 0.9
Android 2.3.6

Please provide any additional information below.
Kontact says for this calendar entry the duration is "forever"

Original issue reported on code.google.com by matt.hei...@gmail.com on 22 Jun 2012 at 10:36

Attachments:

GoogleCodeExporter commented 9 years ago 
Using Kolab-Droid 0.9.1, I still have this problem.

Meanwhile I found out that I have this problem with several calendar entrys. 
All have in common that there is a <start-date> with time but no end date.

Attached is a second calendar entry with which I was able to reproduce the bug.

Unfortunately I don't know at the moment if calendar entrys of this kind are 
valid, therefore I want to update the following question:

What is the expected output?
If this calendar entry is valid, the calendar entry should be in my phone.
If this calendar entry is invalid, there should be an error message reporting 
the invalid entry and continue syncing other entrys afterwards.

Original comment by matt.hei...@gmail.com on 23 Jun 2012 at 1:29

Attachments:

GoogleCodeExporter commented 9 years ago 
an missing end-date is for my interpretation of kolab-xml not valid.

The current behavior is, that the event is one hour long - same if end is 
before start.

Interesting detail: The first code that will work with a null end date is 
Time.compare() (not the isAllDay check!!!). At this point no 
NullPointerException is thrown but the process dies. That was the stop behavior.

Release: >= 0.9.2

Original comment by arthur.z...@gmail.com on 26 Jun 2012 at 3:50