Hello, I would like to ask you if anyone can describe background process in DAVdroid. Some people loose theirs events after synchronization but only what I found in server access log is following sequence:
[06/Jul/2017:10:31:54 +0200] "DELETE /calendars/...ics HTTP/1.1" 403 185 "-" "DAVdroid/1.6.2-ose (2017/06/23; dav4android; okhttp3) Android/7.0"
[06/Jul/2017:10:31:56 +0200] "PUT /calendars/...ics HTTP/1.1" 204 - "-" "DAVdroid/1.6.2-ose (2017/06/23; dav4android; okhttp3) Android/7.0"
[06/Jul/2017:10:32:32 +0200] "PUT /calendars/...ics HTTP/1.1" 204 - "-" "DAVdroid/1.6.2-ose (2017/06/23; dav4android; okhttp3) Android/7.0"
[06/Jul/2017:10:32:40 +0200] "PUT /calendars/...ics HTTP/1.1" 412 242 "-" "DAVdroid/1.6.2-ose (2017/06/23; dav4android; okhttp3) Android/7.0"
[06/Jul/2017:10:32:40 +0200] "DELETE /calendars/...ics HTTP/1.1" 412 242 "-" "DAVdroid/1.6.2-ose (2017/06/23; dav4android; okhttp3) Android/7.0"
[06/Jul/2017:10:32:40 +0200] "DELETE /calendars/....ics HTTP/1.1" 412 242 "-" "DAVdroid/1.6.2-ose (2017/06/23; dav4android; okhttp3) Android/7.0"
[06/Jul/2017:10:32:47 +0200] "DELETE /calendars/....ics HTTP/1.1" 412 242 "-" "DAVdroid/1.6.2-ose (2017/06/23; dav4android; okhttp3) Android/7.0"
[06/Jul/2017:10:32:47 +0200] "DELETE /calendars/....ics HTTP/1.1" 412 242 "-" "DAVdroid/1.6.2-ose (2017/06/23; dav4android; okhttp3) Android/7.0"
[06/Jul/2017:10:32:48 +0200] "DELETE /calendars/...ics HTTP/1.1" 403 185 "-" "DAVdroid/1.6.2-ose (2017/06/23; dav4android; okhttp3) Android/7.0"
Path to ics is always the same. I don’t have debug log from DAVdroid. Currently it was 3rd time when this problem occurred. After I went through logs it almost looks like DAVdroid send commands in batches - in that case I don’t understand why there is PUT command after DELETE.
Never heard of that… Can you please log the process using the logging function in the DAVdroid system settings and post it here anonymized?
Please also send us more information about what server/service you’re using.
We would also need to know what you actually did with your event – did you delete it, update it etc.?
Please provide steps to reproduce (including information about the server), debug info, verbose logs etc..
Does this problem still occur with 1.6.5?
