Is there a tricky bug in the implementation of the profiles in the Joplin Android app?

Coffee · 2023-10-04T07:31:47.013Z

Another question I have now is how can I tell which action is coming from which of my clients.
During the time in question, I was using Android, Windows and two different Linux apps.

The Windows Joplin app seems to deliver entries with
(Nextcloud, windows-10.0.19045 ClientArchitecture: x86_64 OsArchitecture: x86_64)

But which app might have entries with
(X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/117.0"
and
(Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/118.0"
which come one after the other, so that I almost suspect that they come from one and the same app. Is it possible that this is how the Android app appears?
It must be, because I wasn't using the Linux apps at the time. Unless there was some kind of synchronisation process.

Coffee · 2023-10-04T09:01:16.167Z

Coffee:

. "Error: MKCOL
I Parent does not (Exception
(409): . O"
«d:error xmlns xmlns :s="http://sabredav.org/ns">
: except ion>Sabre ic s : except ion>
node does not exist</s:message>

Could the substring
(409): . O"
or perhaps also
(409): . 0"
mean that at some point when changing the profile information in the app, a procedure is run that requires a certain variable with path information to be set, but which is not (any longer) set at that point?

Coffee · 2023-10-04T09:05:28.333Z

Coffee:

I get the full logs of my hosted Nextcloud from my hosting provider.

The logs I currently have of my NextCloud instance seem to contain only successful actions, but unfortunately no details of error situations. I have asked my provider if a verbose mode could be activated for a while, which also logs details of errors.

Coffee · 2023-10-04T10:42:52.673Z

Coffee:

First some research with the help of Google

Probability 50%
The problem is not new in connection with Joplin:

github.com/laurent22/joplin

(Android) Can't synchronize after a profile change

opened 11:52AM - 19 Jun 23 UTC

closed 04:02PM - 29 Aug 23 UTC

gabidanpremier

bug stale

After an app restart following a profile change, a synchronization can't complet…e successfully, leading to this: > Last error: Error: MKCOL locks/: Parent node does not exist (Exception Sabre\DAV\Exception\Conflict) (409)! After ~15 minutes without any profile change, a sync will complete successfully and quickly without any other action than waiting. ## Environment Joplin version: 2.10.8 Platform: Android OS specifics: 13 (Samsung) ## Steps to reproduce 1. Change profile, the app closes automatically 2. Start the app 3. Try to Sync using the synchronize button: a sync would be expect to complete sucessfully. 4. Wait ~15 minutes 5. If not in the app, start it then use the synchronize button: a sync will complete quickly. ## Describe what you expected to happen A sync should be allowed to complete right after a profile change. ## Logfile ![Screenshot_20230619_075042_Joplin](https://github.com/laurent22/joplin/assets/47070419/ed4cbe4e-533c-49c0-b71e-9195c80f9a71)

Perhaps because other procedures have then refilled a necessary variable?

After ~15 minutes without a profile change, a synchronisation is completed successfully and quickly without any action other than waiting.

Coffee · 2023-10-04T10:50:20.669Z

Coffee:

First some research with the help of Google

Description

Some WebDAV clients that create collections do that without including the trailing slash. The logs offer no further explanation, and to a casual user the 409 error is confusing (as it indicates that the parent collection is absent).

RFC4918 recommends them to have a trailing slash, but given that several applications don't send a trailing slash, it stands to reason that it's common for servers to accept it. Section 5.2 even gives concrete guidance that in such a case, the server should accept and send a Content-Location header ("There is a standing convention").

Example clients that don't are webdav-js (GitHub - dom111/webdav-js: A simple WebDAV client written in JS for use as a bookmarklet, or integration into a web server.) and Stratospherix FileBrowser for Business; some examples are around for other clients that employ workarounds (eg. Does not play nice with nginx WebDAV · Issue #523 · laurent22/joplin · GitHub).

https://trac.nginx.org/nginx/ticket/1966

Coffee · 2023-10-04T10:58:17.900Z

Coffee:

(eg. Does not play nice with nginx WebDAV · Issue #523 · laurent22/joplin · GitHub).

I am currently clarifying with my provider whether my NextCloud runs in or with an nginx.

Coffee · 2023-10-04T11:29:28.034Z

Coffee:

I am currently clarifying with my provider whether my NextCloud runs in or with an nginx.

yes, we use the official nginx configuration as a base here:

NGINX configuration — Nextcloud latest Administration Manual latest documentation

Coffee · 2023-10-05T09:07:53.855Z

Coffee:

O.k. I have to look why there was no update on the one Linux

I had probably installed Joplin manually once.
Have now installed the current Joplin normally after deleting the old, manually installed version as described on 20.04 - How to uninstall Joplin if you don't know how it was installed? - Ask Ubuntu
( I did a reboot after uninstalling before reinstalling the package. )

Joplin is often installed manually, though there are Snap and Flatpak options available. To remove a manually installed Joplin installation, you can follow these steps:
Open Terminal (if it’s not already open)
Remove Joplin:

sudo rm -r ~/.joplin
sudo rm -r ~/.config/joplin-desktop
sudo rm ~/.local/share/applications/appimagekit-joplin.desktop

Enjoy a coffee

Coffee · 2023-10-09T15:18:49.056Z

Coffee:

Can you tell me what information the Joplin (Android) app tries to WRITE to the WebDAV server when the profile credetials are changed in the app?
The 409 error should be connected to a write operation ("PUT" ? ), if I understand correctly.

@laurent , can you please answer this question for me as well?

Coffee · 2023-10-22T18:50:06.011Z

@laurent

2023-10-22 - Interim report

This issue only occurs with the Joplin app for Android.
This problem does not occur with the Joplin app for Windows or the Joplin app for Linux.
Even if I evaluate the detailed log files of the NextCloud server, I cannot determine the exact cause of the error.
However, I am sure that I can reproduce the error with a newly installed Joplin app on Android.

Can I somehow provide you with detailed information about this in a personal message without communicating all the details of certain personal data here in public?

laurent · 2023-10-23T08:55:51.725Z

For support queries please post them here so that other contributors can help too (and the forum also serves as a knowledge base). If there's private data in a log, you can remove it before posting it

Coffee · 2023-10-23T14:16:02.125Z

Then, for the further tests and documentation of this topic, I will temporarily create a separate NextCloud with its own domain and user IDs at my hosting provider, which I will delete again at the end. Then I won't have to worry about personal data being transported via the associated log files of future tests.

Coffee · 2023-10-24T18:19:24.807Z

START of the 2023-10-24 documentation

Coffee · 2023-10-24T19:03:21.937Z

2023-10-24 – V001 - New test scenario for
Is there a tricky bug in the implementation of the profiles in the Joplin Android app?

A WebDAV connection to a managed Nextcloud 100, version 26.0.6 of the provider hosting.de is used. When I asked if my NextCloud runs in / with an nginx webserver I got the answer
» yes, we use the official nginx configuration as a basis:
NGINX configuration — Nextcloud latest Administration Manual latest documentation .
«

Two user IDs have been created on the NextCloud instance I have temporarily commissioned for this purpose:
A-User
B-User

For each of these user IDs, a new profile was successfully set up in a Joplin Windows app and a Joplin Linux app. The access data including the WebDAV path to the user's Joplin directory were documented in a password safe, which was also synchronised with the Android test device. This ensured that the identical access data was used in every case.

Android - test device is a Samsung Galaxy S23 Ultra with Android 13 and a Joplin Android app "Joplin 2.12.3" newly installed from the Google Play Store before each of the tests.

Coffee · 2023-10-24T19:09:49.941Z

Test with A-User first
2023-10-24 – 18:4x – Android App installed from Play Store
2023-10-24 – 18:45 – long screenshot from Log
2023-10-24 – 18:53 – Profile name changed from Default to A-User
2023-10-24 – 18:55 – Default Notebook „Wilkommen!“ deleted
2023-10-24 – 18:56 – Synchronisationsziel set to „WebDAV“
WebDAV-URL, User name and Password from A-User copied copied from Passwordsafe
2023-10-24 – 18:58 – connectivity test and first synchronization successful
2023-10-24 - 18:59 - long screenshot from Log
2023-10-24 – 19:03 – New profile B-User created and App restarted
2023-10-24 – 19:05 – Default Notebook „Wilkommen!“ deleted
2023-10-24 – 19:06 – Synchronisationsziel set to „WebDAV“
WebDAV-URL, User name and Password from B-User copied copied from Passwordsafe
2023-10-24 – 19:07 – connectivity test and first synchronization ERROR
2023-10-24 – 19:08 – Screenshot 1st error message
2023-10-24 – 19:08 – Profile B-User saved
2023-10-24 – 19:09 – long screenshot from Log after 1st error message
2023-10-24 – 19:15 – try sync again and get 2nd error message
2023-10-24 – 19:17 – Screenshot 2nd error message
2023-10-24 – 19:24 – long screenshot from Log after 2nd error message

Coffee · 2023-10-24T19:27:11.261Z

Test with B-User first
2023-10-24 – 19:28 – Joplin App uninstalled from Anfroid test device
2023-10-24 – 19:29 – Android App installed from Play Store
2023-10-24 – 19:32 – Profile name changed from Default to B-User
2023-10-24 – 19:33 – Default Notebook „Wilkommen!“ deleted
2023-10-24 – 19:35 – Synchronisationsziel set to „WebDAV“
WebDAV-URL, User name and Password from B-User copied copied from Passwordsafe
2023-10-24 – 19:35 – connectivity test and first synchronization successful
2023-10-24 – 19:37 – New profile A-User created and App restarted
2023-10-24 – 19:38 – Default Notebook „Wilkommen!“ deleted
2023-10-24 – 19:56 – Synchronisationsziel set to „WebDAV“
WebDAV-URL, User name and Password from A-User copied copied from Passwordsafe
2023-10-24 – 19:40 – connectivity test and first synchronization ERROR
2023-10-24 – 19:41 – Screenshot 3rd error message
2023-10-24 – 19:44 – Profile A-User saved
2023-10-24 – 19:53 – try sync again and get 4th error message
2023-10-24 – 19:58 – long screenshot from Log after 4th error message

Coffee · 2023-10-24T19:29:19.340Z

END of the 2023-10-24 documentation

Coffee · 2023-10-24T19:32:30.604Z

I think with this description it should be possible to reproduce the problem I described.

@laurent , what do you think?

Coffee · 2023-10-24T19:52:13.102Z

If you are interested, I can give you the passwords of A-user and B-user on my test environment so you can reproduce the tests yourself without having to use your own NextCloud.

laurent · 2023-10-24T21:07:02.337Z

I don't really get what you want to do. Could you narrow it down a bit? And by the way you use two different webdav urls for each profile, right?