It works fine now. Thank you for quick reaction and bugfixing!
Doesn't sync with davical
So where’s the problem? DAVdroid requests DAV:getetag and CALDAV:calendar-data / CARDDAV:addressbook-data. Can you give me a hint?
it doesnt request any of CALDAV:calendar-data / CARDDAV:addressbook-data, i checked that adding logs in caldav-REPORT-multiget.php
$fd = fopen(“/tmp/php-davical”, “a”);
// write string
fwrite($fd, print_r($properties, true).“\n”);
// close file
if ( empty($properties) ) $properties[‘DAV::allprop’] = 1;
and it did shown me that nothing was requesting except href
DAVdroid does request getetag and calendar-data/addressbook-data, but maybe DAViCal doesn’t understand the request and thinks that nothing of it was requested? Or please give me hint what could be wrong in the request.
how to log what xml and type of request is made in davdroid? in what class does it generate?
The adb logcat with tag “davdroid” shows generated requests (they’re logged). The multiget request is created https://github.com/rfc2822/davdroid/blob/8e8bc1c7722fffae3dbd2a6e8bcb30af98c6c1c2/src/at/bitfire/davdroid/webdav/WebDavResource.java#L283 here (but of course other classes are involved/referenced).
In line 290/292 you can see how the addressData/calendarData prop is set for the request.
@khades Can you please try to put the <href>s after the <prop> in the request (with curl again) and check if it works for you?
didnt understood what you want
Can you try doing the request with curl again, but not
... <href>href1</href> <href>href2</href> ... <prop>...</prop>
... <prop>...</prop> <href>href1</href> <href>href2</href> ...
and see if DAViCal then parses the request correctly?
yes, it works that way
Great, Thanks a lot, I will confirm it’s working in next release