logseq / logseq/db-test

Assets feature not working in a new graph, but working fine in a Demo graph

Open
#1,139 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

Description

### Search first

- [x] I searched and no similar issues were found

### What Happened?

Since I'm a new Logseq user, I learned and tested all the features in a Demo graph, then created a new personal one.
In that new graph, the Assets feature does not work at all:
- uploading directly in # Assets page
- drag&drop into a node
- / upload a file

No file appears after all of these actions.

- But when I switch to a Demo graph, everything works fine.
- In the folder of my graph on Mac, there are many files I've tried to upload, many of them are just duplicates from all the tries, but not showing in the Assets page.
- Then I've tried to export a SQL backup file, deleted a graph from graphs list, imported it again - didn't work.
- All of the screenshots I've attached are after importing a backup SQL, so there are no duplicated files I've mentioned previously.
- I also gave Logseq full disk drive permissions on my Mac

### Reproduce the Bug

Idk, create a new graph and try to upload assets :)
I wish I knew what causes the problem...

### Expected Behavior

_No response_

### Screenshots

Image

Image

[db-worker-node-20260831.log](https://github.com/user-attachments/files/31662392/db-worker-node-20260831.log)

Image

### Desktop or Mobile Platform Information

App Version: 2.0.1
Git Revision: b09316a
Platform: Mozilla/5.0 (Macintosh Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML like Gecko) Logseq/2.0.1 Chrome/148.0.7778.180 Electron/42.3.0 Safari/537.36
Language: ru
Plugins: logseq-awesome-links (v1.15.16), logseq-bullet-threading (v1.1.4), logseq-journals-calendar (v0.11.1), logseq-plugin-flex-date-format (v1.11.0), logseq-localassets-plugin (v2.0.1)

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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the asset uploads in a newly created graph and compare the result with a Demo graph, using the attached db-worker-node-20260831.log for errors. The fix is complete when direct upload, drag-and-drop, and / upload make files appear in the Assets page for the new graph.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.