logseq / logseq/db-test

[sync , web app] Cant create encrypted graph to upload to sync in the web app (app.logseq)

Open
#1,128 2 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?

When I try to upload a local graph for sync, and I select to use encryption, Logseq asks me for a password, I type it, it asks again, I type it, and then an error shows up on the console but nothing is shown to the user in the UI
This is the error:
[frontend.worker.sync.crypt] {:db-sync/user-rsa-key-cache-invalid {:base "https://api.logseq.io", :user-id "MY USER ID WHICH I LEAVE OUT", :graph-id nil, :first-error #error {:message "decrypt-private-key", :data {}, :cause #object[DOMException OperationError]}, :retry-error #error {:message "decrypt-private-key", :data {}, :cause #object[DOMException OperationError]}}, :line 523}

### Reproduce the Bug

1. Create local graph
2. Click cloud icon on top right
3. Select Use encryption
4. Type password twice

### Expected Behavior

_No response_

### Screenshots

_No response_

### Files

_No response_

### Browser, Desktop or Mobile Platform Information

2.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

Reproduce the flow from the web app's cloud icon: create a local graph, select encryption, and enter the password twice. Start with the frontend.worker.sync.crypt error at line 523 and trace the encrypted sync upload path. Done means the graph uploads successfully or the failure is shown clearly in the UI.

Written by the indexing model from the issue text.

Assessment

Domain
cloud, security, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.