Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot initiate sync #23

Open
vegettoo opened this issue Feb 21, 2023 · 4 comments
Open

Cannot initiate sync #23

vegettoo opened this issue Feb 21, 2023 · 4 comments

Comments

@vegettoo
Copy link

Hi Team,

I hit below error when try to initiate sync via logseq plugin.
image

I have enabled remote sync logseq beta feature.

Below is all my graph
image

@vegettoo
Copy link
Author

The issue cannot reproduce after reinstall this plugin, but cannot sync the latest 1 week's highlight records.

@TimLamoureux
Copy link

I am having the same issue. Readwise plugin does not recognize my graph anymore even though it is (theoretically) the same as before. I am using the graph on multiple devices and sync'ed with the official Syncing client. Readwise is not configured to pull highlights automatically, I want to be able to tell it when the content is ready to be pulled. I am failing to find whether this is saved locally or on Readwise's servers. For now, I would prefer to not have to reinstall the plugin to avoid missing the last month of Readwise notes

@TimLamoureux
Copy link

I found out the cause of my issue. The file ~.logseq\settings\logseq-readwise-official-plugin.json contains the reference to the current graph and its path on the disk. In my case, I had moved the graph from ~/graph to ~/Documents/graph and this is what caused Readwise plugin to fail to recognize the graph. Updating the paths in the file and restarting Logseq solved it.

@iamgodot
Copy link

The issue cannot reproduce after reinstall this plugin, but cannot sync the latest 1 week's highlight records.

Same issue. You can refresh selected notes in https://readwise.io/export/logseq/preferences and sync in Logseq again to get them back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants