Android
3.0.8
For the problem between Joplin with multiple profiles and NextCloud, which I first described in detail in September 2023, I ordered a separate NextCloud from my provider specifically for this problem, and I have been charged for it for some time.
See also
This problem does not occur with either a Joplin Windows App or a Joplin Linux App.
Both profiles (A-user and B-user) can easily be connected to the same Joplin Windows App.
Switching between profiles is possible without any problems.
Both profiles (A-user and B-user) can easily be connected to the same Joplin Linux App.
Switching between profiles is possible without any problems.
opened 10:18AM - 12 Nov 23 UTC
closed 11:13AM - 30 Jun 24 UTC
bug
mobile
backlog
### Operating system
Android
### Application version
2.12.3
### Desktop: Abo… ut dialog content
This problem does not occur with either a Joplin Windows App or a Joplin Linux App.
Both profiles (A-user and B-user) can easily be connected to the same Joplin Windows App. Switching between profiles is possible without any problems.
Both profiles (A-user and B-user) can easily be connected to the same Joplin Linux App. Switching between profiles is possible without any problems.
### Current behaviour
In order to be able to reproduce the problem that has existed for months without jeopardising my productive environment and the database of my productive Joplin profiles, I have commissioned a separate Managed NextCloud instance from my provider for the reproduction of the problem and possible further tests. I also brought forward my investment in a new Android mobile phone so as not to expose my Android mobile phone, which is currently in productive use, to any risk.
A WebDAV connection to this managed Nextcloud 100, version 26.0.6 of the provider [hosting.de](http://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](https://docs.nextcloud.com/server/26/admin_manual/installation/nginx.html) .
«
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.
Both profiles ( A-User and B-User) can be connected in a newly installed Joplin Android app if you connect them as the first profile.
The second profile does not connect but runs into [this strange error](https://discourse.joplinapp.org/t/is-there-a-tricky-bug-in-the-implementation-of-the-profiles-in-the-joplin-android-app/32864?u=coffee).
It doesn't matter whether you connect A-User or B-User first.
### Expected behaviour
Both profiles (A-user and B-user) can be easily connected to the same Joplin Android app. Switching between the profiles is possible without any problems.
### Logs
I have already provided log information at
https://discourse.joplinapp.org/t/is-there-a-tricky-bug-in-the-implementation-of-the-profiles-in-the-joplin-android-app/32864/41?u=coffee
and
https://discourse.joplinapp.org/t/is-there-a-tricky-bug-in-the-implementation-of-the-profiles-in-the-joplin-android-app/32864/42?u=coffee
I suspect there's some bug in how Joplin handles cookies on Android. I am seeing issues even without 2 profiles like this:
start with a clean state
enter nextcloud details and press "Check Synchronization Configuration"
now without leaving the screen change the details to another user on the same server
check configuration succeeds but when you try to actually sync NC returns "permission denied"
I think some cookie specific to a particular nextcloud account gets saved on step 2 and then incor…
I only did a quick check but it seemed that deleting cookies before every request has solved the issue.
Someone still need to implement the fix properly, unfortunately I don't have the time to do it myself at this time.
Who needs to do what to ensure that the fix/workaround proposed by @roman_r_m is included in the Joplin release schedule?
Coffee
20 November 2024 11:42
3
I hope that someone will take up this issue.