WebCal calendars cannot be seen (selected) by DAVDROID on mobile system

[hitam4450]

I created a new calendar including web cal subscription (version 1.4) of my favorite soccer team and deleting the "old" static one. After that, DAVDROID 1.3.1 reported "synchronization errors". Ok, I deleted the appropriate account and created a new one. After hitting finished, i does not show any of the "newly" created calendars including web cal subscription. There are not visible at all!

In this case I cannot thze schedule of my favorite soccer team!

regards, hitam4450

[tcitworld]

Webcal calendars are subscriptions that don't seem to be supported by DAVdroid. Use ICSdroid instead : https://davdroid.bitfire.at/faq/entry/subscribe-ics-file/

[rfc2822]

Webcal calendars are subscriptions that don't seem to be supported by DAVdroid.

These calendars should be reported as read-only CalDAV calendars by Nextclound, and then be detected by DAVdroid.

Do you know whether Nextcloud reports these subscriptions as calendars?

[georgehrke]

Do you know whether Nextcloud reports these subscriptions as calendars?

No, it does not. It's not a calendar collection, but a subscription.

[georgehrke]

These calendars are also not cached on the server, only in the users browser.

[rfc2822]

No, it does not. It's not a calendar collection, but a subscription.

Ah ok, so CalDAV clients can't see it of course.

[georgehrke]

They do, this calendar app is also only a caldav client.
The iOS and OS X calendar app will also display it properly.

[rfc2822]

No, it does not. It's not a calendar collection, but a subscription.
/
They do, this calendar app is also only a caldav client.

As fas as I know the CalDAV RFC, CalDAV clients can see only calendar collections. Have I missed something?

[georgehrke]

The subscribed collection is not an official part of the CalDAV standard. It's some extension by apple

[rfc2822]

I see, Nextcloud reports:

<d:response>
    <d:href>/nextcloud/remote.php/dav/calendars/test/my-subscription/</d:href>
    <d:propstat>
        <d:prop>
        <d:resourcetype>
            <d:collection/>
            <cs:subscribed/>
        </d:resourcetype>
[…]

So it's not a calendar collection and thus can't be listed (and synchronized) by DAVdroid.

Thanks for your help.

[untitaker]

Is there any reason why only Apple's non-standard extension is used? Couldn't the resource be described like this:

<d:resourcetype>
    <d:collection/>
    <cs:subscribed/>
    <cs:calendar/>
</d:resourcetype>

[georgehrke]

Because there is no official standard for it and Apples private standard is the most widely used one

[untitaker]

What is wrong with describing it as calendar?

[georgehrke]

The calendar will be empty. The entries are not stored on the server, but the browser loads them directly.

[untitaker]

Also contact birthdays are exposed as calendar but WebCAL subscriptions aren't. Both are described as subscriptions in the Calendar UI.

It wasn't clear to me that the calendar UI is not a pure CalDAV client.

[georgehrke]

Subscriptions are just read-only calendars. if you share a calendar with someone read-only it will also show up as subscription.

[untitaker]

I'm arguing that it is counter-intuitive to label two things as subscription when they have entirely different semantics in CalDAV.

[georgehrke]

Well, but the semantic here is calendars = read-write, subscriptions = readonly. I'm very open for a discussion to rename subscription to something else.

when they have entirely different semantics in CalDAV.

Sorry, but ordinary users frankly don't give a shit about what CalDAV is and how it handles calendars.

[untitaker]

Sorry, but ordinary users frankly don't give a shit about CalDAV.

Users do give a shit as soon as they use that protocol to sync ownCloud with DAVDroid or any other non-Apple client. They have to give even more of a shit as soon as they notice that only parts of their subscriptions are discovered by standards-conformant CalDAV clients.

[georgehrke]

They have to give even more of a shit as soon as they notice that only parts of their subscriptions are discovered by standards-conformant CalDAV clients.

We are considering making them available as ordinary caldav calendars, but this requires changes to the server-part. It's nothing we can do in a simple calendar release. Something like this would come in a bigger Nextcloud release.

[untitaker]

That's totally understandable.

[jancborchardt]

@georgehrke @untitaker so for making them available as ordinary CalDAV calendars, should there maybe be a separate planning issue opened? :)

[ghost]

Any news on this? I would like my subscribed calendar feeds to show up on my mobile device.

[tcitworld]

For starters, see nextcloud/server#1497

[leopoldfajtak]

Are there any news about this? Vdirsyncer still can not sync Nextcloud's WebCal subscriptions, and the workaround on the client side is janky at best.

[tcitworld]

@leopoldfajtak please open a new issue with details, as things have changed since then