I just found that while the shared calendars can’t be viewed and thus not edited…Where read/write access to the shared calendar applies, calendar events can be created in the shared calendar on the phone and are shown in the Zimbra web based calendar after sync completes.
DAVdroid and ip format urls
I am developing my own caldav server and trying to get it work with DAVdroid. I am running my own caldav server on my Windows machine as localhost. I have Bluestacks Android emulator running on same machine where I have DAVdroid app connecting my server. To reach localhost from emulator I need to configure DAVdroid server “Base url” in ip format and it is 10.0.2.2
My problem is that DAVdroid seems not to handle ip format urls. When I look from my server’s log(HTTP header Request Line) I see that DAVDroid is trying to use url in format “/email@example.com/neo/://firstname.lastname@example.org/neo/” when it should be “/email@example.com/neo/”. Same thing happens when I configure port number in url “10.0.2.2:80”. Can someone tell my if I am making something wrong?
Please provide steps to reproduce (including DAVdroid debug info and verbose DAVdroid logs etc as described in [READ BEFORE POSTING] What’s required to diagnose a problem. These logs contain what DAVdroid receives from the server and how it generates its requests.
Here is zip package containing debug info & log files.
Here I have another DAVdroid log of case where DAVdroid could not make connection to my own server. In this case I used reqular Android tablet and server url is https://firstname.lastname@example.org/neo/. This case did not write debug info files. This server has authentication.
Log is here:
Could someone look my case?
Are you sure that this is a client problem? I guess there was a problem at resource detection, maybe an invalid server response. This is why DAVdroid uses
/email@example.com/neo/://firstname.lastname@example.org/neo/. The logs you have sent do not explain how this resource has been detected.
If you have found a specific problem in DAVdroid, please let us know the exact problem, if possible with exact steps to reproduce and verbose logs of this specific problem.
Maybe it also helps to have a look at the DAVdroid source code: https://www.davdroid.com/source/