Sunik Kupfer

I will look into it one of the coming days and create an overview of the current state.

> * handle when renaming the account I think this is where it belongs logically. We could just call [disable()](https://github.com/bitfireAT/davx5-ose/blob/6b1367d6dc691a2d18a3bbfc82e5a98937262d2b/app/src/main/kotlin/at/bitfire/davdroid/syncadapter/PeriodicSyncWorker.kt#L106) from `RenameAccountFragment` no? At least this is where I would...

True, any ideas other than an app intro?

Oh, nice! I would go with B or C and make the whole card clickable. :)

> @sunkup interested in giving it a try? Sure, I wonder which servers support the COMMENT field already though? Seems like [nextcloud (tasks) does not](https://github.com/nextcloud/tasks/issues/109) ?

> Ricki wrote to use "debug info level" ... The debug level Ricki meant was most likely `INFO`, but I can see the confusion with the word "info" :D

> ### Purpose > > Check whether "Show only personal" can use `DAV:owner` instead of "belongs to a homeset that belongs to the user". > > Check especially with eGroupware....

> I wonder whether we should really hack this into the existing `DavResourceFinder` / `CollectionListRefresher` or whether we should do another refactoring round of service detection before. > > What...

> So I'll close this PR and we should open a new one when #1588 is done. Right. Probably better. Sorry for my misjudgement.

In `AccountProgressUseCase` (probably) just add a callback flow `pendingInSyncFramework` with `ContentResolver.addStatusChangeListener()` checking for pending and combine that flow in `AccountProgressUseCase.invoke`.