Should be fixed with https://gitlab.com/bitfireAT/davx5-ose/commit/5709fd38d9df62ca0afc03e764487917fc9cc2e5 / 2.5.1, will send an APK for testing. For testing: Install the new APK Open DAVx⁵ and the account Switch to Webcal tab Swipe down to refresh the Webcal list Subscribing to webcal(s):// URLs should now work

@rfc2822 thanks again

@habazut I see. Excellent.

I agree. With DS-Lite though it is not as easy as it was in the past to get a nice VPN to your home network. Thanks anyway. Maybe I get VPN to work someday.

I might be able to try on another device next week, will update if I can reproduce

Screenshot

@TheIvan Thanks for the update. If you can find a way to reproduce the problem, just let us know.

Hello, There are no such restrictions. Theoretically, you can sync hundreds of calendars, so I guess there’s another reason why some calendars don’t show up. Do those calendars have something in common, for instance are they shared calendars?

Hello, I can reproduce the problem. The (a) problematic event is BEGIN:VEVENT DTSTART;VALUE=DATE:20170820 DTEND;VALUE=DATE:20170821 EXDATE;VALUE=DATE:20180415 EXDATE;VALUE=DATE:20181216 EXDATE;VALUE=DATE:20190120 EXDATE;VALUE=DATE:20190818 RDATE;VALUE=DATE:20170916,20171014,20171118,20171216,20180120,20180217,2018 0317,20180519,20180616,20180714,20180818,20180915,20181020,20181117,2019021 6 RRULE:FREQ=MONTHLY;BYDAY=3SU UID:a6p98i2kp66mg5e5ep6t2ot96g@google.com … This is an event without end (no COUNT or UNTIL in RRULE), and it seems that the existence of RDATE/EXDATE in such events can’t be processed by the Android calendar provider, which sends: icsx5 : Found VEVENT: a6p98i2kp66mg5e5ep6t2ot96g@google.com icsx5 : a6p98i2kp66mg5e5ep6t2ot96g@google.com not in local calendar, adding RecurrenceProcessor: DateException with r=FREQ=MONTHLY;WKST=MO;BYDAY=3SU rangeStart=135390560256 rangeEnd=9223372036854775807 CalendarProvider2: Could not calculate last date. CalendarProvider2: com.android.calendarcommon2.DateException: No range end provided for a recurrence that has no UNTIL or COUNT. CalendarProvider2: at com.android.calendarcommon2.RecurrenceProcessor.expand(RecurrenceProcessor.java:768) CalendarProvider2: at com.android.calendarcommon2.RecurrenceProcessor.expand(RecurrenceProcessor.java:663) So, it seems that such events are not supported by Android.

Afaik there is no software that allows you to sync with x servers and concurrently with x clients and keep everything in sync. You can only have one server for a “server wins” architecture. Ofc there is the possibility of mirroring or clustering on the server side but with 2 different types of servers (fruux and NC for instance) this would not be possible for various reasons.

Duplicate of https://forums.bitfire.at/post/6487, please follow up there

Steps to reproduce: Set up a Caldav calendar (mailbox.org here). With DAVx5 connect to this calendar. Cause an syncing error. In this case deleting a recurrent birthday reminder caused an error 403 (Forbidden) from the server. Expected behaviour: DAVx5 continues with the next sync item, trying to sync as many items as possible. DAVx5 informs the user about all failed items. Actual behaviour: DAVx5 stops the sync. Many other sync items are not synced because one single failure.

Steps to reproduce: Set up a Caldav calendar (mailbox.org here). With DAVx5 connect to this calendar. Cause an sync error. In this case deleting a recurrent birthday reminder caused an error 403 (Forbidden) from the server. Current behaviour: DAVx5 writes a log file with technical error information (e. g. HTTP request and response, technical device information, Java stacktrace). The information might help the developer, but it doesn’t help a non-tech user at all. The information about the failure appears as a tiny icon in the status bar only, where it can easily be overlooked. Expected behaviour: DAVx5 informs the user in a visible message, in understandable, non-tech words that it could not synchronize, which item is affected (the displayed name of the contact, date or task), what caused the error, how he/she can solve the problem and go on. For instance see https://www.nngroup.com/articles/top-10-application-design-mistakes/, chapter 3. If the log file is needed for the developer, DAVx5 helps the end-user with easy-to-follow steps to send it to the developer.