"Synced" status on Android not always correct (especially after item delete)

[Jayden_Navarro]

I was browsing the bugs page, and saw this comment you made in another post, which is really enlightening:

@Shida

Internally, dynalist uses a “diff” system to sync changes to the server. We store a local copy of your current Dynalist file, and a local copy of the “last synced” Dynalist file. When it’s time to send changes to the server, a “diff” is created by comparing these files and summarizing the difference.

When we compute the diff, an additional step of optimization is done to avoid scanning the whole file: we mark each item with a version number, and when they’re edited locally, the version number is bumped to indicate that it’s been changed. When computing a diff, any item with version numbers below the last synced number is ignored.

Given these details, I was curious whether the item version number was not incremented, or if it just didn’t realize we needed to perform a sync-up.

So I reproed the issue again, but rather than refreshing to force it to sync I modified a different item. This caused both items to sync-up immediately, so it seems that the verison number is correctly incremented, but the app just doesn’t realize there are new changes that need to be synced up.

This is different than the behavior I observed for collapsed items, which did not sync-up when a different item was modified. Therefore they are likely isolated issues (unless I’m missing something).