You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 26, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on May 26, 2026. It is now read-only.
I was able to set up a personal test account in DAVx5 using https://caldav.calendar.yahoo.com.
Tested with an Android 13 emulator.
Event added on server syncs to device
Event added on device syncs to server
Event changed on server syncs to device
Event changed on device syncs to server
Event deleted on server syncs to device
Event deleted on device syncs to server
Recurring event with exception syncs fine both ways1
Task added on server syncs to device
Task added on device syncs to server
Task changed on server syncs to device
Task changed on device syncs to server
Task deleted on server syncs to device
Task deleted on device syncs to server
Footnotes
I used the web interface to change an occurrence of a recurring all-day event to a DATE-TIME event with a different summary text. However, this exception doesn't appear to be synced to the device via CalDAV.
Making the same change on the device rewrites the event to exclude the exception in the CalDAV version. However, the webinterface is showing the exception as the device has originally created it.
Exceptions that don't switch from DATE to DATE-TIME or the other way around seem to work fine. ↩
Activity
sunkup commentedon Apr 15, 2026
caldav.calendar.yahoo.comorcalendar.yahoo.comcketti commentedon Apr 15, 2026
I was able to set up a personal test account in DAVx5 using
https://caldav.calendar.yahoo.com.Tested with an Android 13 emulator.
Footnotes
I used the web interface to change an occurrence of a recurring all-day event to a DATE-TIME event with a different summary text. However, this exception doesn't appear to be synced to the device via CalDAV.
Making the same change on the device rewrites the event to exclude the exception in the CalDAV version. However, the webinterface is showing the exception as the device has originally created it.
Exceptions that don't switch from DATE to DATE-TIME or the other way around seem to work fine. ↩