[kronolith] Import of Google Calendar (ICS) destroys users calendar and makes sync impossible

[Christian Bierwirth]

Am 29.09.2012 03:12, schrieb Michael J Rubinsky:
>
> Quoting Michael J Rubinsky <mrubinsk at horde.org>:
>
>> Quoting Christian Bierwirth <chris at cb-solutions.de>:
>>
>>> Am 25.09.2012 15:37, schrieb Michael J Rubinsky:
>>>>
>>>> Quoting Christian Bierwirth <chris at cb-solutions.de>:
>>>>
>>>>> Am 24.09.2012 16:29, schrieb Michael J Rubinsky:
>>>>>>
>>>>>> Quoting Christian Bierwirth <chris at cb-solutions.de>:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> I've got an issue with an imported google-calendar
>>>>>>>
>>>>>>> First of all I'm using horde-webmail-edition 4.0.8, updated with
>>>>>>> PEAR to the current level.
>>>>>>>
>>>>>>> Normal sync of calendars and addresses works fine with Android 
>>>>>>> 4.1.1
>>>>>>> on several galaxy-nexus smartphones with several accounts. The
>>>>>>> problem occured when I imported the ICS-export of a new users
>>>>>>> google-calendar. The Import worked fine, I could see all enries and
>>>>>>> modify/delete them. Syncing with Android didn't work at all from
>>>>>>> this point on while it did before with some test-events. I post a
>>>>>>> snippet of  the debug-log at the end of this mail.
>>>>>>>
>>>>>>> Furthermore it is not possible to purge all the events in the
>>>>>>> screwed up calender anymore after the import. Though it's no 
>>>>>>> problem
>>>>>>> to delete a single event. I tried several ways:
>>>>>>>
>>>>>>> - delete the user's standard-calendar
>>>>>>> - create a new calendar, make it the standard calendar and try to
>>>>>>> delete the now non-standard-calendar
>>>>>>> - export the new calendar, containing one single test-event,
>>>>>>> reimport it in the standard-calendar, overwriting all events
>>>>>>>
>>>>>>> the error always shown is:
>>>>>>>
>>>>>>> "Kalender von user at domain.tld" kann nicht gelöscht werden: 
>>>>>>> "Kalender
>>>>>>> von user at domain.tld" kann nicht gelöscht werden:
>>>>>>> 20120918102621.QMxlDmRHsl5QWDAthn4AHvA at www.domain.tld not found
>>>>>>
>>>>>> It sounds to me like there was some error on import, or a corrupt
>>>>>> event in the imported data. The error message (if I'm translating it
>>>>>> correctly) means that a specific event in that calendar was not 
>>>>>> found,
>>>>>> so it could not be deleted.  This was causing the entire delete
>>>>>> operation to fail. I have fixed this particular issue in git.
>>>>>>
>>>>>>
>>>>>>> (no paste error, this duplication is shown as posted here)
>>>>>>>
>>>>>>> So there is no way back to a working sync for this user?
>>>>>>>
>>>>>>> Any suggestions?
>>>>>>>
>>>>>>> If more information is needed I'll post it here.
>>>>>>>
>>>>>>> Thanks in advance!
>>>>>>>
>>>>>>> Chris
>>>>>>>
>>>>>>> (...) deleted the log-stuff for better readability
>>>>>>
>>>>>> This error is usually do to the device either not receiving the full
>>>>>> server response or it not liking the data that it did receive. It
>>>>>> handles this by requesting a SYNC with the same sync_id again - this
>>>>>> is normal and expected in this case. We need to figure out what 
>>>>>> about
>>>>>> the sync'd events the device does not like.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> -- 
>>>>>> mike
>>>>>>
>>>>>> The Horde Project (www.horde.org)
>>>>>> mrubinsk at horde.org
>>>>>>
>>>>>>
>>>>>
>>>>> Hi Mike,
>>>>>
>>>>> thanks for your response. Do you need any more information than 
>>>>> already
>>>>> posted? Unfortunately the whole logfile ist about 80MBs in size. I 
>>>>> could
>>>>> ask the calendars owner for the google-ICS-exportfile if this would
>>>>> help.
>>>>
>>>> If you can get me the ICS export, I'll try to take a look when I can.
>>>>
>>>
>>> No Prob. Will send this lateron (actually I'm at work) to your
>>> @horde.org address.
>>>
>>> Thanks again
>>>
>>> Chris
>>
>> Whatever is happening, it's only happening on Android. I've tested
>> on multiple iOS devices, a WinMo device and Android. There is
>> something in one of those events that Android does not like so it
>> ignores it and pretends it never received the data - so it send the
>> same synckey again to signify this.  I'll look and see if I can
>> figure out what the data is....
>
> It was a bug in how we were generating the alarm values. Certain types
> of VALARM data were causing a broken, negative, value for this field.
> Android was choking on this value causing the entire sync to fail,
> while other clients were just ignoring it.
>
> The root cause (the incorrect imported alarms) has been fixed in Git
> for Kronolith 3.0.18.
>
>
> -- 
> mike
>
> The Horde Project (www.horde.org)
> mrubinsk at horde.org
>
>

Hi Mike,

that's good news! Thanks a lot for your work, man.

Cheers

Chris

--
Diese Nachricht wurde auf Viren und andere gefährliche Inhalte untersucht
und ist nach aktuellem Kenntnisstand virenfrei.

cb-solutions Antispam/Antivirus Service