"Setting file [PLAIN_NOTE_FILE] is not matched to the current configuration. skipped."

[flyingnobita]

Abstract

Getting a lot of errors as: Setting file [PLAIN_NOTE_FILE] is not matched to the current configuration. skipped.

PLAIN_NOTE_FILE:

• is just a "bunch" of regular .md file, and not a settings file
• PLAIN_NOTE_FILE are only recently edited files, though this list seems to be growing

Synchronisation, either LiveSync or Manual Sync, doesn't seem to work anymore unless the app (desktop and/or mobile) is restarted. Though the errors persist.

Expected behaviour

• Not receiving this error
• synchronization succeeds for all PLAIN_NOTE_FILEs

Actually happened

• Synchronisation shows the errors above, in the desktop, as well as my iphone and android clients
• Synchronisation of all the PLAIN_NOTE_FILEs fail

Reproducing procedure

1. Perform sync

Other information, insights and intuition.

• using Self-hosted LiveSync version 0.22.2
• Hidden file synchronization: Disabled
• Customization sync: Disabled
• problem only happens recently (perhaps after a version upgrade?)
• not sure if it's related, but I'm also getting the error described in Conflict resolve window is uncloseable #368
• On mobile phone, tried setting up again using "Open setup URI" with URI from desktop. Same error when setup finished unfortunately.

Thank you.

[vrtmrz]

Thank you for reporting this issue! This message should have only appeared in the verbose log. This has been fixed in v0.22.3. Possibly, #368 is not related to this. However, probably occurred in the same release as you mentioned. The conflict issue may have been caused by #372. This is also fixed in v0.22.3.

Would you mind trying v0.22.3, please?

[flyingnobita]

Yes with 0.22.3 I don't see the error messages anymore.

I rebuilt my DB as you instructed for #368 and I don't see the conflicts anymore.

Thank you again for your prompt reply and of course your awesome plugin!