DAVx5 reverts task completeness state

[sunkup]

Problem scope

• I'm sure that this is a DAVx⁵ problem.

App version

• I'm using the latest available DAVx⁵ version.

Android version and device/firmware type

n/a

Steps to reproduce

As described here. Reproducible with both jtxBoard and Tasks.org.

1. Sync the same task capable collection/calendar in our nextcloud on two devices (A and B) with DAVx5.
2. Device A: Create a task in tasks app with due date two days in the future and give it a short name. Don't complete it.
3. Device A: Synchronize the collection -> task shows as incomplete in nextcloud interface ✅
4. Device B: Synchronize the collection -> task shows as incomplete in tasks app✅
5. Device A: Mark the task as complete
6. Device A: Synchronize the collection manually -> task shows as complete in nextcloud interface✅
7. Device B: Synchronzie the collection manually -> task shows wrongly as incomplete in the tasks app ❌and in the nextcloud interface❌
8. Device A: Synchronize manually -> Task completeness state is wrongly reset to incomplete here too❌

Actual result

The task completeness state is reset when it should not be.

Expected result

The task completeness state should be "pulled" correctly on the second device.

Further info

Maybe you will need to retry 1-2 times.

[sunkup]

Here are few tests which seem to confirm the suspicion of @CelianGdfrd. It seems the issue is either related to switching away from the tasks app too quickly or simply that the change needs to be somehow processed by the sync framework first?

Test 1: Manual syncs from within DAVx5 ❌

Test 1

Test1.-.Manual.syncs.from.within.DAVx5.webm

Test 2: Manual syncs via Sync Framework in Tasks.org ✅

Test 2

Test2.-.Manual.syncs.via.Sync.Framework.in.Tasks.org.webm

Test 3: Manual syncs from within DAVx5 ❌

Test 3

Test3.-.Manual.syncs.from.within.DAVx5.webm

[sunkup]

@bitfireAT/app-dev Any ideas on why this happens? Can you verify/reproduce my findings?

[rfc2822]

I can give it a try after 4.5.4