Davdroid 0.5.8 crashes

DAVx⁵
Log in to reply
  • A

    Hi,
    I am (was) quite happy with davdroid and radicale, until suddenly all my devices start to fail syncing the calendar (contacts are fine). Below is a logcat and the corresponding VTODO snippet in the calendar file (at least I believe this is it, because that is the file name that was mentioned last in the catlog…

    D/davdroid.SyncManager( 4834): Adding 1d633416-cf90-4fdc-842f-ca184bb15044.ics
BEGIN:VTODO
CREATED:20120426T142538Z
LAST-MODIFIED:20120427T063450Z
DTSTAMP:20120427T063450Z
UID:1d633416-cf90-4fdc-842f-ca184bb15044
SUMMARY:Send to Volker MISQ\, SMJ\, Stefan User Entrepreneur
STATUS:COMPLETED
DUE;TZID=Europe/Zurich:20120504T170000
COMPLETED:20120427T063447Z
PERCENT-COMPLETE:100
SEQUENCE:1
X-MOZ-GENERATION:2
X-RADICALE-NAME:1d633416-cf90-4fdc-842f-ca184bb15044.ics
END:VTODO


E/AndroidRuntime(21823): java.lang.NullPointerException
E/AndroidRuntime(21823): 	at at.bitfire.davdroid.resource.Event.hasTime(Event.java:319)
E/AndroidRuntime(21823): 	at at.bitfire.davdroid.resource.Event.isAllDay(Event.java:315)
E/AndroidRuntime(21823): 	at at.bitfire.davdroid.resource.LocalCalendar.buildEntry(LocalCalendar.java:417)
E/AndroidRuntime(21823): 	at at.bitfire.davdroid.resource.LocalCollection.updateByRemoteName(LocalCollection.java:203)
E/AndroidRuntime(21823): 	at at.bitfire.davdroid.syncadapter.SyncManager.pullChanged(SyncManager.java:199)
E/AndroidRuntime(21823): 	at at.bitfire.davdroid.syncadapter.SyncManager.synchronize(SyncManager.java:89)
E/AndroidRuntime(21823): 	at at.bitfire.davdroid.syncadapter.DavSyncAdapter.onPerformSync(DavSyncAdapter.java:71)
E/AndroidRuntime(21823): 	at android.content.AbstractThreadedSyncAdapter$SyncThread.run(AbstractThreadedSyncAdapter.java:259)
I/ActivityManager(  529): Process at.bitfire.davdroid:sync (pid 21823) has died.```

P.S. Update: I am not sure if it was the update to the latest davdroid, a change in configuration of the radicale server, or a change in the calendar data. I deleted the specific VTODO, but it stopped and died at another VTODO (which had not been changed for a long time), so I do not think it is the calendar data that is at fault.

P.P.S. THis is with 0.5.8a, I will test 0.5.8.1 as soon as it is on fdroid.org
    0
  • rfc2822
    developer

    Duplicate of #178, fixed with 0.5.8.1

    0

Similar topics