Search first

• I searched and no similar issues were found

What Happened?

I use logseq across mobile, desktop, and ipad, syncing with icloud. icloud syncing works fine, but logseq can't regularly track changes to pages or even the pages at all.

This manifests in two specific ways:

Pretty much daily, I populate my daily journal page on desktop. Later in the day, I will go to the same page on mobile and it will be empty, until I start typing and I get a screen that shows me two conflicting versions of the page to choose from, one from logseq (which is empty) and one from disk (which is populated with what I put there on desktop that morning). I choose the version on disk, expecting this to resolve confusion for logseq. But pretty regularly, this will confuse logseq and lead to some loading screen, after which the page is blank again and I have to go through the same process.

Relatedly, several pages that I know exist (because I've used them for a long time and they exist on both desktop and ipad) don't exist in logseq on mobile. I know this because the references to blocks in those pages appear broken only on mobile. Sure enough, when I go to the page with the missing blocks, it's empty. As mentioned above, my mobile logseq has a really hard time keeping up with the syncs, so I will start typing on the empty page and suddenly this conflicting versions page will pop up where I'm supposed to choose between the version of the page on disk (which is nonempty) and the version in logseq (which has whatever random stuff I just typed), and I will choose the populated version. At this point, the references are no longer broken.

The reason I'm even going to the lengths of reporting this is that it's a regular, recurrent problem. The same pages keep disappearing from logseq even though they're there on disk, and it's a hassle to force a version control conflict between disk and logseq every time I have broken references.

Reproduce the Bug

I think if this were a bug that happened broadly, I would have been able to find another issue/it would have been resolved in 0.8.18, so I don't know how to instruct you to recreate it, except by doing the following:

1. Find a page in logseq that is empty/doesn't exist, but that you are sure exists on disk
2. Start typing until you get a conflict resolution screen.

Expected Behavior

I expect logseq to track pages that are on disk, but it doesn't seem to.

Screenshots

Desktop or Mobile Platform Information

No response

Additional Context

macOS 13.2.1, Desktop App v0.8.18
iPhone 13 Pro Max, iOS 16.3.1, v0.8.18

Are you willing to submit a PR? If you know how to fix the bug.

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