Unable to import db in logseq

[shvmsaini]

Search first

• I searched and no similar issues were found

What Happened?

Getting Invalid data writing to db! when I try to import my db.sqlite in logseq web.
On every reload I get Invalid data writing to db!
console log :

36b59a7c.logseq-db-test.pages.dev-1778090541759.log

Though I can still view my pages, I cannot mutate them properly or export them.
When I try to export using EDN file I get:

36b59a7c.logseq-db-test.pages.dev-1778091296810.log

Any other way to export leads to app crash.

Also when I try to import on desktop version, I cannot even see anything, logseq just becomes unresponsive.

I have backups till 3 April and even those are having the same issue.

Please help.

Reproduce the Bug

I don't know it's happening on my db.sqlite

Expected Behavior

No response

Files

No response

Browser, Desktop or Mobile Platform Information

No response

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!)

[shvmsaini]

If I try to import using old version of logseq I still get
SQLiteDB import error: #error {:message "invalid sqlite import data", :data {:code :invalid-sqlite-import-data, :repo "logseq_db_o"}}

I am not sure what to do with so many backups but all seem to be useless.

I tried importing 3 April backup into 22 April release (cannot get past this because of expired releases) I got
SQLiteDB save error: TypeError: Failed to fetch

[hdansou]

Try: Download an older build of logseq from a date close to the backup date.

Retry the graph validation and see if you still have errors. Clear the validation errors, then retry the import

[shvmsaini]

I have tried importing 30 April backups (zip, sqlite, edn) in 30 April releases, same issue.

Also validation is stuck on 10 invalid blocks

and one of the invalid blocks is this

However trying to delete this block does not work, I only get notification **Invalid data writing to db!**. Restore button does nothing. Delete button logs:

36b59a7c.logseq-db-test.pages.dev-1778120319248.log

[lraieph0]

I encountered the same problem, an error occurred when exporting the zip file.
Moreover, the scheduled backup feature is no longer working.

[shvmsaini]

Hi @tiensonqin, sorry but can we prioritise this? I am happy to provide as much logs as you want. I am not able to use logseq other than just viewing and not even able to reliably work on new graph from the file version due to #863.

[tiensonqin]

@shvmsaini Can you send me a db.sqlite or debug transit file to reproduce this bug?
My email address is tienson@logseq.com.