Guest user not able to add account on Android client

Seafile Client
1

Hi!

I have installed Seafile Pro 12.0.13 on Unraid. For our Barbershop Quartet, I set up a library containing sheet music, recordings, and learning tracks. Since there are only four of us, it seemed simplest to create just one user with the “Guest” role, share the library with read permissions, and pass the credentials to everyone. This way, each member can install the Seafile client on their smartphone and access all resources.

I checked the setup by logging in via the browser, which worked fine. Then I installed the client on an Android smartphone (version 3.0.9 from the Google Play Store) and tried to log in by adding the account.

However, I kept getting the message “Username or password is incorrect” or “the signed-in user was not found.” At first, I thought there might be an issue with the SSL certificate. Then, as a test, I tried logging in with my other user account, which worked flawlessly.

I was only able to log in with the second user after changing the role from “Guest” to “Standard.” It was pure luck that I tried this first. After successfully adding the account in the client, I switched the role back to “Guest.” So far, it seems to work as expected.

I also tested this on my primary smartphone, where the Seafile client (version 3.0.12 from F-Droid) has been installed for a while, and I am logged in with my admin account. The behavior was the same: I had to change the user role from “Guest” to “Standard” to log in.

Has anyone else encountered this issue? Thank you in advance!

Best regards,
Tom

2

I have a Seafile Server Pro 12.0.14 with a single user (“Standard”) running under Docker behind an Apache reverse proxy. Since 2 months (it will probably have been the update from version 11 to 12) my Android client (currently version 3.0.13) is not uploading any new photos - “the signed-in user was not found”. However, downloading photos or documents works.

3

Same problem on my secondary account… I’ve no log to add.

4

I got this error in Android log : D/Seafile-SLog: BaseUploadWorker, transferFile(), upload failed：{“error”: “Bad request.”}

This error is catch by the default behaviour and return a return SeafException.NOT_FOUND_LOGGED_USER_EXCEPTION.


    public static SeafException parse(int errorCode, String bodyString) {
        //401
        if (HttpURLConnection.HTTP_UNAUTHORIZED == errorCode) {
            return SeafException.NOT_FOUND_LOGGED_USER_EXCEPTION;
        }

        //400
        if (HttpURLConnection.HTTP_BAD_REQUEST == errorCode) {
            //"Repo is encrypted. Please provide password to view it."
            if (bodyString.toLowerCase().contains("please provide password to view it")) {
                return SeafException.INVALID_PASSWORD;
            }

            if (bodyString.toLowerCase().contains("wrong password")) {
                return SeafException.INVALID_PASSWORD;
            }

            if (bodyString.toLowerCase().contains("operation not supported")) {
                return SeafException.OPERATION_NOT_SUPPORTED_EXCEPTION;
            }

            return SeafException.NOT_FOUND_LOGGED_USER_EXCEPTION;
        }

In my caddy server in front of the docker seafile service I don’t see any error… strange

6

In Seafile 12, if the account is a guest role, the connection of the Android client is disabled by default, which is “can_connect_with_android_clients: false” in the configuration file. You can customize the permissions of the “guest” role in the seahub_settings.py

2 Likes
7

Hi chaohui.wang!

Thanks a lot! I didn’t read about this in the docs. I’ll try this out soon. Thias ist a great helper.

Cheers,
Tom