Automatically sync new calenders / task-lists

[NextBlaubeere]

I am using Nextcloud tasks quite heavily. Therefore I often create new task projects which are synced to my android phone via DAVx5.
However, everytime I create a new project i have to refresh the list on the CALDAV tab within the android app and manually select the new projects/calenders.

How can I make DAVx5 to automatically refresh the list and turn on sync for new entries?

[sunkup]

Syncs are automatic. You can change the polling interval in the settings. We are working on a solution (webdav-push) to bring near instantaneous updates, but for the time being you will need to make the polling interval shorter.

The collection refresh is not automatic. At the moment it is not possible to enable automatic collection refreshes.

We have considered refreshing the collections before syncing a few times now, but some users have huge collection lists, which would slow down the sync unnecessarily every time.

Since the introduction of work manager we could now prepend the sync with a refresh by chaining the two work requests, which seems relatively easy. So I guess we could make this a setting that is disabled by default without too much effort. Might be interesting for managed customers as well. How about it @devvv4ever @rfc2822 ?

[Atemu]

We have considered refreshing the collections before syncing a few times now, but some users have huge collection lists, which would slow down the sync unnecessarily every time.

Besides of proper solutions to scalability issues, is there a reason this couldn't just be a toggle which users could manually enable?

I imagine most users don't have huge collections but rather just a handful of items but enough where it gets tedious to enable on all of their devices.

You could perhaps even enable it by default and have some basic size heuristics to disable it with the mentioned "huge" collections (but still let those enable it manually).

The fact that new items aren't added automatically is a huge usability issue IMHO. Nerds might understand but mere mortals? No chance.

[sunkup]

@Atemu I am with you on this.

If I remember correctly, our head of engineering @rfc2822 had some other reasons as well, though I can't see why we could not make this a setting which is turned off by default.

[rfc2822]

I imagine most users don't have huge collections but rather just a handful of items but enough where it gets tedious to enable on all of their devices.

We know at least one server/service where the collections of all users are detected when you're admin (and thus access to all collections).

In this case, this would enable sync for all user collections by default (and there can be many) and they would have to click through an endless list of collections to disable most of them.

So I think this would be useful for 99% of the people, still the problems which arise for the other 1% are serious... Maybe we can automatically enable only all "own" collections?

[Atemu]

Ideally, this would be behind a toggle that controls default collection subscriptions.

These edge-cases could also be prevented using some simple heuristics which would disable the "subscribe to all available collections by default" toggle by default.

[rfc2822]

Unfortunately the heuristics wouldn't be that simple, because we would have to know how many collections there will be before detecting them. Because when we're detecting them, we already insert them into the database with the value of the "enabled for sync" flag taken from the settings.

Of course we could split the process etc. but it's not simple and we have to be careful with such changes.