Replies: 1 comment 2 replies
-
Hey there, and thank you for the extensive report. This is a known issue with with SimpleCalendar. The details on why this happens are discussed there. In short: SimpleCalendar has a special way of handling exceptions. DAVx5 however treats the Android calendar provider the standard way which most other calendar apps do too. You may consider using another CalendarApp. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all! I'm a long time user of DAVx5 and I'm really pleased with the freedom it gives me overall. I'm using SimpleCalendar + DAVx5 + radicale.
I have a bug 🐞 . Lately, I've started getting sync failures with "400 Bad Request". Some of my events sync but one of them fails and then the rest stay unsynced until I delete the bad event. I get these screens which I expect you're familiar with
and
Eventually, I figured out how to turn up debugging on my server and found the exception is
which seems to be
radicale
objecting to multiple incompatible event repetitions (RRULE
s) in the buggy event.Reproducing
I don't know exactly how to reproduce this. I know I did edit the recurrence on this particular event a couple of times, but I don't know exactly what order I did things in. I've had this happen before though, and those times I just deleted the buggy event and hoped it wouldn't come back. This time I'm reporting what I know so at least there's somewhere to start solving it!
Discussion
I'm not sure whose issue this is. I think radicale is probably doing the right thing here by rejecting the weird event, which means it's either SimpleCalendar's fault for generating the weird event and/or DAVx5's for accepting it. Though, does DAVx5 have an opportunity to reject an event when saved by the calendar app?
If it does, I think it should reject broken events like this, the same way radicale is. That is, DAVx5 should port this logic into itself. That way the event will become uneditable, while leaving other events still syncable, instead of most (all?) events becoming surprise unsyncable. And then it will be possible to convince SimpleCalendar to fix their recurrence logic to avoid this case in the first place.
Logs
Client Side UI
I don't see multiple repetition definitions in the event; there's no way to tell from the UI there's a problem until the sync fails:
Client Side Logs
Here's the client side logs; I'm only including the first part because there's personal details in the rest, but I have the rest of
davx5-debug.zip
if you need them and I can audit them more carefully to strip out details if sharing them would be helpful.debug-info.txt
Server Side Log
Versions
Client Side Versions
Hardware:
harpia
Android version: 10
LineageOS version: 17.1-20220209-microG-harpia (from this dead link).
DAVx5 version: 4.2.1-ose (from f-droid).
Sinmple Calendar version: 6.18.3 (from f-droid)
Server Side Versions
OS:
Calendar server:
radicale
installed viapip
(i.e. PyPI).Beta Was this translation helpful? Give feedback.
All reactions