I can’t imagine why it shouldn’t work with Ownclou 10. However, without logs and more details, I can’t say anything reliable about it.

Everything is working perfectly now. The address you get to give DAVX is this : “https://www/folder whereowncloud is located/remote.php/dav/calendars/userid/calendar name/” Now, you get to synchronize the name of the account in order to make the related calendar app display the calendar. Enjoy.

I just tried the medicine, but it has no effect. While thinking about the issue it is like a one way sync but without davdroid reading the entries on the server. My girlfriend actually has the exact same phone with an older android version i will install davdroid there and see if it shows the same behavior.

Please note that Thunderbird is not an iCalendar validator. However, I don’t see any problem with this iCalendar event here, it looks like this on my Android 8.1 emulator (25 Nov 2016 10:30 +00 = 25 Nov 2016 11:30 CET, which is used in the calendar view): Also, which past time event limit have you set in the account? This information is also contained in the debug info, so please provide the debug info as described in [READ BEFORE POSTING] What’s required to diagnose a problem.

We got a message from another user using the Blackberry Hub who found the solution: In the Blackberry contacts app in the preferences check all accounts (also accounts that don’t have any address books). As a server the reporting user is using a mac OSX. Thank you!

Thank you that link helped. The Problem is gone now. However OpenTask should ask for permission instead of letting the user unknowing he has to request them by hand through the settings.

DAVdroid connects to the server and tries to connect to /my-hidden-dir/remote.php/dav . As an answer it gets a 401 Unauthorized answer with a Basic auth request. Why does it get a 401? It sends the Autorization header preemptively. Maybe the IP has been locked because of too many attempts? Is there any info in the OwnCloud logs? I would expect either that DAVdroid tries to connect with correct Authorization headers starting with the first attempts That is how it behaves here, and how it should behave. Are you sure that there is no problem with the password? Does it contain non-ASCII characters? Can you provide the necessary steps so that we can reproduce the problem? Without that, I can’t do anything.

@sarahbesic Indeed "HTTP\/1.1 415 Validation error in vCard: REV MUST NOT appear more than once in a VCARD component See here: https://forums.bitfire.at/topic/1259/rev-must-not-appear-more-than-once-in-a-vcard-component/25

@rfc2822 Yes, this solved my issue. Thank you very much.

Hello. Sorry. It’s was my problem. I thinked that the sync button in the top of the screen syncs the calendars too. Why it can’t do this? I find the sync calendar list in the submenu of the Calendars form and now the new calendars are visible in the list. Thanks you. Have a wonderful day.

Good. I try and now its ok. Thanks you. Good luck.

Of course, I meant to write “DAV” where I wrote “David.” I suspect the spell-checker got me there.

@rfc2822 said in Contacts lose their `CATEGORIES`for reasons unclear: Thanks for your report. Can you please provide verbose steps to reproduce and DAVdroid debug info? I wish I could, I have no Idea how to re-introduce those faulty VCARDs back into the system (I presume they got there from earlier versions of nextcloud calendar). If I were to guess the reproduction steps, thou would probably be have faulty (i.e. containing escaped comma) VCARDs on your server of choice SYNC (creating faulty entries on your android device) correct VCARDs on the server (i.e. remove comma) SYNC → wonder where your actual categories/groups went. Why has the VCard version changed from 3 to 4? As far as I can see, all VCARDS written by DAVdroid 1.3 and later are VERSION:4.0, so I do not fully understand the question. Is DAVdroid still set to the CATEGORIES group method? I don’t remember ever changing this setting (as far as I can tell your question was the first time I checked that deeply into settings). The chosen method is (and always has been) “Gruppen sind Kategorien der Kontakte” -> “groups are categories of contacts” (loosely translated from german translation) I’ll have to be able to reproduce the problem so that I can have a look at it. Yes, I can totally understand that. I will gladly help. There’s limits on what I can do, though. I don’t really have a debug setup, only my actual phone with my actual contacts.

Yeah, I could narrow down the conflicting event by playing with the past event setting. With past event up to 112 days everything works fine. The event in question is one with accidentally interchanged start and end date. I have no clue, why in spite of this the multi days event was displayed corrently - and moreover could even be synced with CalDAV-sync. As soon as I have corrected start and end time, I am able to sync past events with no limit. Thanks for feedback. So topic could be marked as “solved”.

Re: Owncloud 9.1: Could not create new calendar entries on shared calendar I found the solution! It is not a flaw of Davdroid, it is because of the new dav-URL. The old url which needed to be used for caldav was https://hostname.com/remote.php/caldav But with Owncloud 9.0 and newer it is now for caldav and carddav https://hostname.com/remote.php/dav So the solution is, delete your old account in davdroid and recreate it with the new url. Details here If you use the wellknown-notification, keep in mind to change the owncloud-apache config too, like this: Redirect 301 /.well-known/carddav /owncloud/remote.php/dav Redirect 301 /.well-known/caldav /owncloud/remote.php/dav Source

I think you should check for the caldav-URL. Your debug-log shows the same problem like mine, so my solution could help you too

Is this maybe the same problem like mine? Did you upgrade your owncloud from <9.0? Then my solution my should help u 2

@danjde Unfortunately, DAVdroid can’t know whether the password is actually wrong or whether the server rejects the login for other reasons, so we have decided to simply show the “no service found” message + details. Happy to hear that it now works for you!

This is an OwnCloud problem, please follow up here: https://github.com/owncloud/contacts/issues/466 I tried it with another CARDdav-App (CardDAV Sync free) and syncing in both directions worked fine. So it seems that the other CardDAV app doesn’t even support VCard 4.

Thanks for the help. Saved the vCard, found there 2 records of groups. It’s not clear how they signed up, but after their removal, the synchronization went with the groups.