Logseq Sync stablility on Android // Data loss with Sync Beta

[TimLamoureux]

Search first

• I searched and no similar issues were found

What Happened?

I noticed 2 occurrences of partial data loss while using Sync Beta.

The first time I noticed it today was with a block I created on the 2023-01-13 journal based on a template for "Calls". I have not noticed the green or orange light right away for the Sync status. I only used that device on that day so I was not worried and I know that the sync light was green later that day. Fast forward to today, on the same computer, the block is totally missing, it appears that all the other content is still around. The computer is using version 0.8.16. It is highly likely that the journal page has been accessed on Android app 0.8.15.

The second time is with another journal entry for 2023-01-16 which was modified in the late evening on Android 0.8.15. There was no template involved, just typing content. I waited to make sure the entry had been synced before locking the screen on the mobile device. While revisiting the journal entry to add content today, I noticed that the edited block along with its grand-parent block (2 levels up) was missing. This one was easy to notice because my journal uses a template and the entire section is missing. The grand-parent had been initially created on Android 0.8.15, I added more content on another computer (not the one from the example above) using version 0.8.15, the content was accessible on Android throughout the day. I opened the graph on the computer from the example above (0.8.16) to edit other pages. When I went back on Android, I noticed that the block was missing.

I looked in the logseq/bak/journals on both Android and the 2 Computers for any trace of the missing content but I couldn't find it,

I am aware that this report is most likely missing crucial debugging information. I hope it provides a bit of information to be able to correlate with possible future incidents.

Reproduce the Bug

I have tried to reproduce the bug by entering data in both Andoid and the computer but was not able to reproduce it. It seemed that sync was pickup changes much slower than previously (~15 seconds to sync). That did not cause any block or child-block to lose its content though, especially not in the middle of a journal entryAndroidchild block

Expected Behavior

Sync does not lose content

Screenshots

No response

Desktop or Mobile Platform Information

Computer 1: Windows 10, Logseq 0.8.16, using Sync Beta
Computer 2: Windows 10, Logseq 0.8.15 using Sync Beta
Mobile: Pixel 7 on Android 13 (Build TQ1A.221205.011), Logseq 0.8.15 using Sync Beta

Additional Context

Could the version mismatch be the cause of the data loss?

Are you willing to submit a PR?

• I'm willing to submit a PR (Thank you!)

[TimLamoureux]

I discovered another block which went missing from a journal page. It was also created on Android 0.8.15 and I noticed it was missing on the computer running 0.8.15. The parent or grand parent block was not deleted. With the assumption that the version is the problem, I am upgrading both Android and Win machines to 0.8.16 to address if it still happens.

[andelf]

Could you check the Page History to see if there's any backup?

0.8.16 fixes some issues related to Logseq Sync stability.

[TimLamoureux]

Hi andelf, thanks for the trick on the Page History. Yes I am able to see the previous versions in the History which is handy to recover when something goes missing and it is noticed. Is there anything that can be useful in the history to further troubleshoot the issue?

I am glad to hear there's been some sync improvements in 0.8.16. The versions < 0.8.15 seemed to perform better than 0.8.15 itself.

[Bad3r]

@andelf moved from 0.8.17 to 0.8.18 milestone

[vhbsouza]

I believe this might be related with #8513 that I faced in iOS

[lelong88]

I had sync issue between Mac and Android too, with both on version 0.8.17. The issue was that pages with either character "," (comma) or "&" in the title either won't sync or sync incorrectly creating 2 conflicting markdown files.

As soon as I changed pages' titles to remove these characters, it synced okay again.