I'm really grateful you're putting so much effort into this. After updating both the desktop client and the Android client, now the sync seems to run smoothly – with one exception: When I hit the “check sync settings” button in one of my four profiles on the Android client, it returns this message:
“Error: Please check that URL, username, password, etc. are correct and that the sync target is accessible. The reported error was: WebDAV directory not found”
Since the sync with the same Nextcloud server works for all the other profiles (and for all profiles on the macOS client), there's a small chance the problem lies with the Nextcloud user account, which I am about to investigate, but I presume the Joplin app on Android might be the cause of the issue as well. When I ignore the failed sync test and initiate the sync it spits out a “completed” message followed by “Last error: Error: MKCOL locks/: Parent node does not exist (Exception Sabre\DAV\Exception\Conflict) (409): <?xml version="1.0" encoding="utf-8"?> <d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns"> <s:exception>Sabre\DAV\Exception\Conflict</s:exception> <s:message>Parent node does not exist</s:message> </d:error>
When I do a search on SabreDAV, its website says that it comes with an experimental WebDAV-Client that's a wrapper around curl. Can we rule out that the Joplin Android app implements alpha/beta stage code from that WebDAV client?
(I triple checked my config input in the Joplin Android app, and even retyped the URL when I noticed a bug that moves the cursor to the left of a character that I insert anywhere in the string but the very end.)
