Syncing new block and reference to that new block results in non-render

[da5nsy]

Search first

• I searched and no similar issues were found

What Happened?

When receiving new content via a sync, if the new content contains both a block and a block reference to that new block, the block reference is not recognised and is rendered a raw reference with coloration indicating a missing link:

Reproduce the Bug

1. On desktop create a new block, and a block reference to that new block
2. Sync to mobile

I've just tried and failed to reproduce this abstractly, despite having seen it multiple times in practice, so I must be missing a required condition somewhere.
I think I've seen it mainly when I open logseq on mobile having not opened it for a couple of days - the problem block is on a previous day, and it is referred to on the current day.
I have assumed that it's because it renders the current day's journal before processing the previous days' journal pages, and so it doesn't recognise the link in time.

Expected Behavior

No response

Screenshots

No response

Desktop or Mobile Platform Information

App Version: 0.10.9
Git Revision: c67b8b5
Platform: Mozilla/5.0 (Windows NT 10.0 Win64 x64) AppleWebKit/537.36 (KHTML like Gecko) Logseq/0.10.9 Chrome/118.0.5993.159 Electron/27.1.3 Safari/537.36
Language: en-GB
Plugins: harmony-theme (v.1.3.0), logseq-cusgit-theme (1.3.2), logseq-flow-nord-theme (v0.9.32), logseq-ozean-theme (v0.1.1), logseq-dracula-theme (0.0.5), logseq-pdf-export-plugin (2.2.10), logseq-oxford-blue-theme (v0.2.0), logseq-tabs (v1.19.1), logseq-block-to-page (v1.3.0), logseq-emoji-picker-fork (v0.0.5), logseq-dev-theme (v1.26.17), logseq-graph-analysis (0.10.2)

Additional Context

No response

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

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