Thanks, I’m looking forward to the new VCard lib and hope that it does not have this issue. Won’t fix might not be the right tag, since this will hopefully be fixed 😉
0.7.6 Wrong timezone for newly created all-day events
I just upgraded from DAVdroid version 0.7.2 to 0.7.6 and created a new all-day event in aCalendar.
The newly created event was syncing to my owncloud server and after syncing i reopen that all-day event in aCalendar.
It is no longer an all-day event.
It is now starting from today 02:00 am to tomorrow 02:00 and the timezone for that event is showing a British timezone.
My timezone on my device is Middle European Summertime (GMT+2) and all other events are correct, only the newly created all-day event is showing a British timezone.
If i create a new event (not all-day) starting from i.e. 14:00 to 15:00 pm there is no problem.
After syncing the right timezone is displayed and starting time is still 14:00 pm.
After that i reinstalled DAVdroid 0.7.2 and created an all-day event again.
After syncing to owncloud the event is correct. It is all-day and correct timezone.
So only all-day events are affected and only in DAVdroid 0.7.6.
Going back to 0.7.2 is a workaround.
Does anyone else can confirm and reproduze this problem?
DAVdroid 0.7.6 from F-Droid
LG Nexus 5 running Android 4.4 (CyanogenMod 11)
Thanks for reporting. This regression bug in handling all-day events has been fixed.
Wow, that was quickly. Thank You!