Trigger Synchornization on Account Deletion

[dilyanpalauzov]

As outlined at https://gitlab.com/techbeeat1/jtx/-/issues/293, when an account is deleted in DAVx⁵, jtx Board is not told about the change and it does not delete the account internally.

DAVx⁵ shall tell jtx Board when an account is deleted, so that jtx Board can delete the account.

[rfc2822]

Thanks for your suggestion!

@patrickunterwegs I think because jtx Board is the content provider, it could implement OnAccountsUpdatedListener (like here) and remove stale accounts from the database when the system accounts are updated.

What do you think about that?

[patrickunterwegs]

Hey, well, I explained already in the other thread that previously a check was already implemented that would request the accounts on loading the list view and check if the known accounts are still present, the listener was not really necessary in this case.
However, in rare cases the account manager did not return the DAVx5 accounts. The synchronization was done but on opening jtx Board all synchronized data was deleted immediately as the accounts were interpreted as deleted (but in fact it was just the account manager that returned an empty result set). Using the OnAccountsUpdatedListener wouldn't fully solve the problem und could still cause the same issue.

As I couldn't reproduce or find the root cause for this problem and the impact was severe when it happened, I decided to remove that piece of code and let the user remove the account manually from jtx Board (with a dedicated message in the collections overview).

It might still be interesting to let DAVx5 do the cleanup (meaning run a last synchronization with no active collections when an account gets deleted).
But I also like the idea of leaving it up to the user to delete the account from jtx Board - now it is consistent, it is never deleted automatically. Letting DAVx5 do a final sync could make it inconsistent if you delete the account directly from the account manager.

[dilyanpalauzov]

But I also like the idea of leaving it up to the user to delete the account from jtx Board - now it is consistent, it is never deleted automatically. Letting DAVx5 do a final sync could make it inconsistent if you delete the account directly from the account manager.

Currently, when the collections are first deselected, the account is synchronized, and then the account is deleted the result is no account in jtx Board. If the account is however just deleted in a single step, then the account name is still present in jtx Board. That said currently it is alreay inconsistent.

[patrickunterwegs]

@dilyanpalauzov de/selecting collections in DAVx5 is a different action than deleting an account

[dilyanpalauzov]

It is subjective, whether removing an account is the same or different, from first deselecting the collections and then removing the account.