App does not not log in on Android or crashes

[MathiasRenner]

Actual behaviour

Cannot login into nextcloud with official app. This bug has been filed here #1738 for app version 2, but now I have a similar issue with the latest app.

Expected behaviour

1. Provide server URL and credentials to the app
2. After I pressed the button "grant access": see list of files of my Nextcloud

Steps to reproduce

Provide server URL and credentials to the app via the wizard. The credentials seem to be accepted, this screen is shown:

Environment data

Android version:
LineageOS 14.1, Android 7.1.2

Device model:
Samsung S7, SM-G930F

Stock or customized system:
Stock system with MariaDB. Docker images fresh from upstream, no relevant changes in config.

Nextcloud app version:
3.4.1

Nextcloud server version:
15.0.0

Logs

Neither in Nextcloud server nor in App are relevant log entries. I used LogCat to record the log while reproducing this issue.

Fun facts

Several notebooks are connected with the same account I'd like to use on the phone to the app and work fine.
Also the "Notes" app with the same Account works fine. The Nextcloud app is the only part in the ecosystem I have an issue with.
I had the same issue with version 13 of Nextcloud. Updating to v 15 unfortunately did not help.

[nextcloud-android-bot]

GitMate.io thinks possibly related issues are #2529 (App crash), #2147 (Android App V3 doesn't log in), #1848 (App Android crash on click left menu Activity...), #1174 (Android O), and #1550 (User does not stay logged in. ).

[tobiasKaminsky]

Can you create us a test account, test if the problem occurs also there and if so send the credentials to tobias at nextcloud dot com with a reference to this issue?

[MathiasRenner]

@tobiasKaminsky Test account created and credentials just sent via Email.

Interestingly, the problem does not occur with the test account! I am confused.

Hmm... my own user was a fresh one, I did not import any backup which could have imported old problems...
The difference is only that the test user does not have admin rights.

[tobiasKaminsky]

If the problem does not occur on the test account, I cannot try to reproduce it.
Can you temporary disable admin rights from your account to see if this helps?

[MathiasRenner]

@tobiasKaminsky Tried that today. Same error without admin rights. Still no log entry in the settings when the issue occurs on the phone.

I don't wanna invest more time here bugfixing it, especially because it seems I cannot make it reproducible for you. I probably create a new user for me and take the effort of migrating the configuration (esp. calender, contacts).
Gonna do this in the upcoming days - except you have another idea :-)

[tobiasKaminsky]

Is the problematic username something special? Like special chars, whitespaces, etc?

[MathiasRenner]

@tobiasKaminsky: Nope, just normal chars.

[MathiasRenner]

Update: After update to 15.0.2 today, an error is shown. I updated the problem description in the very first post.

[tobiasKaminsky]

@nextcloud/server-triage do you have an idea?

[MorrisJobke]

@nextcloud/server-triage do you have an idea?

@tobiasKaminsky Could you reproduce this on your device? Because I'm not aware of something related to this. It looks like the HTTP header is not correctly send over.

[tobiasKaminsky]

No, I cannot reproduce it and @MathiasRenner also cannot reproduce it with a new account…

[MathiasRenner]

Update: For me this is reproducible now. Any new user I create and try to log in with in the Android App fails. It's always the same error as above.

I did not change the environment, just added and deleted new users to try out...

This is really frustrating :-(

@tobiasKaminsky I just sent you new login infos.

[tobiasKaminsky]

@MorrisJobke thanks to the credentials by @MathiasRenner I can now reproduce it.
Do we wanna try to debug this together?

[tobiasKaminsky]

As we get "Error
Access Forbidden

Invalid request" I assume that somewhere the header is not correctly passed and thus it refuses to login.

[tobiasKaminsky]

There is something strange happening during weblogin flow, we cannot debug this from here.

Can you give us a bit more insight on your server? apache/nginx? config, etc?

[MathiasRenner]

@tobiasKaminsky Thanks for your effort.
This is the infrastructure I use: https://github.com/bitleaf/simple-traefik-proxy-and-services
Thus, reverse proxy is handled by traefik.
This is the docker-compose file I use for Nextcloud as backend service: https://github.com/bitleaf/simple-traefik-proxy-and-services/blob/master/backend-nextcloud/docker-compose.yml

There is not much config. Traefik just forwards incoming requests to the domain to the latest official nextcloud container...

[MathiasRenner]

@tobiasKaminsky Figured out that this bug is introduced with server version 15 and higher.
Testing with 14.0.6 -> all OK. As soon as I upgrade to 15.0 the bug comes in.

I deleted my testing env (incl. your test account) and will go down to 14.0.6 now, waiting until v 15 is of higher quality.

I am not that eager in testing more, wanna use the system eventually :-)
Thanks for having beeing in touch with me, I hope you find the issue soon!

[tobiasKaminsky]

@nextcloud/server-triage do you have an idea how we can help @MathiasRenner to get this working on 15+?
Seems to be a strange regression…

[rullzer]

Not really. Since this is working as advertised on all the instances I have access to. And without a test system there is not really a way to fix this.

Only thing that might be is it that overwriteprotocol in config.php is not set (seems people forget that behind a reverse proxy).

[tobiasKaminsky]

Ok, then I'll close this for now, as I read that the test system is deleted.