-
Notifications
You must be signed in to change notification settings - Fork 8
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
[Bug]: Sync on Remote tries to sync multiple times #98
Comments
Additionally if I turn Sync on Save, Sync on Remote off and only manually sync. Somehow the metadata is synced before the end of step 3? This only happens when I reset the metadata file I believe. Found this trying to uninstall the original Remotely Save which I can't seem to remove even after resetting the metadata. And then the metadata is synced again at the end. This might be one of the causes that Sync on Remote is running multiple. |
Interesting... maybe sync config dir is syncing your remotely save plugin and preventing deleting it? Does it work with just remotely sync? |
I have sync config dir on. If I disable it will it delete the .obsidian on the remote? I think everytime I delete Remotely Save it thinks my local doesn't have it and resyncs it back in. Not sure why. This is kind of a seperate issue though.
Not sure what you mean, sorry. |
Yeah you need to delete your metadata file with the reset dev setting after disabling and this has to be disabled on all devices where it is enabled - related to the issue where we can't track deletes outside obsidian. |
What happened?
I'm finding that after detecting remote changes 'password is blank? false remote has metadata? false' gets printed around 10 times then it runs multiple syncs at the same time.
Not entirely sure why or how it is managing to sync multiple times at once.
At the end the metadata sync is all bunched up.
What OS are you using?
Windows, Android
What remote cloud services are you using?
Dropbox
Version of the plugin
0.4.36
Version of Obsidian
No response
Using password or not
Ensure no sensitive information
The text was updated successfully, but these errors were encountered: