@computingfroggy Thanks for the update. Good to hear that it now works!
Sync error on Android although calender seems to sync correctly
- Android mit e/os
- DAVx5 version 4.0-ose
- Nextcloud server 23.0 - self hosted
In Nextcloud we use the Deck app, which appears as an additional calender in DAVx5 on the Android device. Syncing the cards works well in all cases, except one. As soon as we modify one specific card on the server, we receive an error message in Android, that DAVx5 got a 404 response. When looking at the server log, we see that request, which is causing the issue:
[17/Dec/2021:06:38:42 +0100] "PUT /remote.php/dav/calendars/jurgenhaas/app-generated--deck--board-7/card-20.ics HTTP/1.1" 404 905 "-" "DAVx5/4.0-ose (2021/10/13; dav4jvm; okhttp/4.9.1) Android/9"
OK, one would normally say this must be a server issue, but the strange thing is, that the card syncs just fine! Both ways. Doesn’t matter, whether we change that card on the server or on Android, it always sync correctly but throws the error. And it happens only for that one card.
When I try to open the card in the browser with https://www.example.com/remote.php/dav/calendars/jurgenhaas/app-generated--deck--board-7/card-20.ics that works correctly too. So the URL is valid and the 404 is probably caused by the PUT request?
I’m lost here and hope somebody could help me finding out, who of all the involved parties could be helping here to fix the issue.
Seems that you have changed a Nextcloud Deck card. Write access to Nextcloud Deck is not supported by Deck (yet) and they return 404 instead of 403. See the information here: https://forums.bitfire.at/topic/2427/404-when-uploading-a-locally-modified-resource
Does that help?
@rfc2822 Yes, that sounds exactly like my problem. Sorry that I didn’t find this before, I wouldn’t have opened another topic then.
What’s strange though, changing the label of a card on Android still gets synced back to the server. I really wonder how that’s possible, if the PUT request is denied in the first place.
Never mind, at least I now know that there is nothing wrong with my setup. And for everybody else, eventually ending up here, it looks like the issue is handled at https://github.com/nextcloud/deck/issues/2355