Seafile Android Client 4.0.4 Login issues

Seafile Client
1

Hello,

I’m new to the forum, please be easy on my first post :slight_smile:

I am a long time user of Seafile and very happy with my self-hosted Docker instance. All was working fine up to Android version 4.0.3. After updating a logged on account remains logged on, but I cannot logon using version 4.0.4. The error message is:

IO Instance(): No current account

When I downgrade the Android app to 4.0.3 I am able to logon again. I am using an mTLS capable HAProxy but I have already redirected traffic through a non-mTLS capable HAProxy and got the same result. When I provide the username and password and press logon normally the 2FA field pops-up allowing me to put in the 2FA code, on 4.0.4 I get the mentioned error. I see no http requests hitting the HAProxy so it looks like a local problem? I have looked at the GIT delta between 4.0.3 and 4.0.4 and there are 2 exceptions it can throw:

IO Instance(): No current account

and

IO Instance(): No current account?

According to GitHub: /haiwen/seadroid/compare/v4.0.3…v4.0.4

app/src/main/java/com/seafile/seadroid2/framework/glide/SeafGlideCache.java has the exception with question mark so I don’t think I’m hitting that. app/src/main/java/com/seafile/seadroid2/framework/http/HttpManager.java holds the same exception without question mark so I guess I’m hitting that?

@Override
public void registerComponents(@NonNull Context context, @NonNull Glide glide, @NonNull Registry registry) {
    try {
        OkHttpClient client = getClient();
        registry.replace(GlideUrl.class, InputStream.class, new OkHttpUrlLoader.Factory(client));

        registry.append(GlideImage.class, InputStream.class, new GlideImageModelLoaderFactory());

    } catch (IllegalStateException e) {
        SLogs.e("SeaGlideCache", "No current account?");
    }
}

f4d8ce04-060f-4bfe-bb9c-10134f997e62
f4d8ce04-060f-4bfe-bb9c-10134f997e62640×768 20.1 KB

Any help is appreciated! Sorry if this has been asked before I couldn’t find anything..

I forgot to mention I’m running GrapheneOS so it might be some restriction causing this issue, I have provided the app with full permissions and disabled hardening. Up to 4.0.3 all was fine on GrapheneOS. Anyone else facing this issue?

2

@pakjebakmeel
This issue has been fixed and has been published to Github Releases(v4.0.5), where you can download and update it.

1 Like
3

I have updated to 4.0.5 and can confirm that login is working again.

Thank you so much for the quick fix! :+1:

1 Like