Block References are not preserved while exporting

[sawhney17]

In Logseq, once the database has been imported, you still don't get working block references and instead get red highlights suggesting that the original point of references doesn't exist. If you find the corresponding block that was supposed to be referenced, you will notice that it has a different UUID.

Logseq 0.028 and Athens Beta 89 on an M1 Mac

[bshepherdson]

Hm, that's odd. I specifically tested that case while initially writing the original version, and it worked fine.[1]

Can you supply a minimal Athens DB that shows the problem?

[1] I did accidentally preserve the output directory and was overwriting it repeatedly, which might have introduced a subtle bug.

[sawhney17]

Looking through my DB, i noticed that some of the references are preserved and looking closer, I noticed some edge cases that are prominent throughout my DB and narrowed it down to 2 issues.

1. When a block is referenced by more than 1 block
2. Some weird hierarchical edge case which I think should be self explanatory in the DB I'm attaching. It's a sample DB which once working fine, should fix the export for myself and many others.

There is a page in the DB called Example where i've created a testing page illustrating all the edge cases, the default welcome page could also be a good testing point.

Test DB Example.zip

Sorry for the late reply, didn't see the notification.