You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Five years ago, I set up synchronization via WebDAV for a backup to my cloud. Now my phone broke, and I discovered that the last synchronization was three years ago. So, the notes from the last three years are missing. Nevertheless, Joplin always reported a seemingly successful synchronization. There were also no notifications indicating that the synchronization target was unreachable.
Expected behaviour
Joplin should display at least one error message on the interface. Even better, Joplin should notify about every failed synchronization via notification.
Logs
No response
The text was updated successfully, but these errors were encountered:
So to clarify, you have set up the webdav sync on your new device, and when you complete the initial sync, you have your note collection, but the notes available on the device are 3 years out of date?
Just to rule this out, are you absolutely sure you are syncing to the same webdav account which you were originally syncing to before your phone broke? I for one have set up a few different sync targets on Joplin for testing since I started using Joplin, so it could be an easy mistake to have 2 similar accounts and forget that one of them was abandoned.
Also have you tried accessing the webdav account in whatever online portal the provider offers, and seeing if there are any files on there with a modified date between 3 years ago and now in the folder where the Joplin data is stored?
Operating system
Android
Joplin version
3.1.8
Desktop version info
No response
Current behaviour
Five years ago, I set up synchronization via WebDAV for a backup to my cloud. Now my phone broke, and I discovered that the last synchronization was three years ago. So, the notes from the last three years are missing. Nevertheless, Joplin always reported a seemingly successful synchronization. There were also no notifications indicating that the synchronization target was unreachable.
Expected behaviour
Joplin should display at least one error message on the interface. Even better, Joplin should notify about every failed synchronization via notification.
Logs
No response
The text was updated successfully, but these errors were encountered: