beta-release Logseq DB app shows 5 missing assets for sync, but files are not missing from Assets folder!
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?
The app says I have 5 missing assets, but the files are actually present in the assets folder. I tried removing the files from the folder and adding them back, and also deleting the blocks and adding the files back via drag and drop to the block in Logseq (got error "duplicate asset"), and neither worked.
### Reproduce the Bug
1. Go to block with missing asset
2. Click "reload" button
### Expected Behavior
Asset should load properly
### Screenshots
_No response_
### Files
_No response_
### Browser, Desktop or Mobile Platform Information
MacOS 26.5.2, Logseq 2.0.1 (first beta release)
### 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in Logseq 2.0.1 on macOS: open a block with a reported missing asset and click Reload. Trace the missing-asset and duplicate-asset behavior against the Assets folder. Done means assets present in that folder load successfully without the app reporting them missing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100