search

vrtmrz / obsidian-livesync

MIT License
3.92k stars 132 forks source link

Configuration mismatching between the clients? v0.23.12 #446

Closed Robertschv closed 4 weeks ago

Robertschv commented 1 month ago

Hello, I have a problem since I updated to version 0.23.12 from 0.23.11 , it doesn't synchronize my notes with Cloudant IBM.

This is what the log says:

Initialized, NOW TRACKING! 2.6.2024, 15:03:56->Before LiveSync, start OneShot once... 2.6.2024, 15:03:56->OneShot Sync begin... (pullOnly) 2.6.2024, 15:03:56->Configuration mismatching between the clients has been detected. This can be harmful or extra capacity consumption. We have to make these value unified. 2.6.2024, 15:03:56->Could not connect to server.

Funny enough I literarily copied the whole vault with this plugin to my other devices, and only changed the “Device Name” since then I haven't changed any configuration, and it worked fine until now.

So I am basically clueless, does anyone know why this happens, or where can I find this “bad configuration”?

hobbesjaap commented 1 month ago

I'm having exactly the same issue. I've had a popup screen once or twice, which then asks me to choose a configuration (local or remote, I remember). After I've selected one, syncing resumes. Until five minutes later, when the problem strikes again. So syncing is currently not working between my different devices.

hobbesjaap commented 1 month ago

I've just updated all 3 of my clients to the latest version, killed the app, restarted it, and now sync is working. Hope this fixes it more permanently, since it worked intermittently yesterday too.

sawamaru commented 1 month ago

I also got the same error message and could not synchronize. I then performed a Rebuild. As a result, the rebuild process completes, but when I restart Obsidian, I get the message “Initialized, NOW TRACKING!” during the CHECK AND SYNC process and the process stops.

vrtmrz commented 4 weeks ago

Thank you for opening the issue! This dialogue is displayed if different values are set for items that should have the same value on several devices. It does not depend on the device name. So I would like to think that it just happened to coincide with the timing of the upgrade.

It must therefore be decided which configuration to use. (It will eventually appear again, if 'Use ours' has been selected on all devices). If you have decided to Use ours, please select Remote 1 on the other devices.

However, we have a bug in detecting non-configured items before v0.23.12. It will be fine now.

Robertschv commented 4 weeks ago

Ok, I did a downgrade before and now i did an update again, everything works now, thanks 🥹