android 🚀 - Android App V3 constantly requiring login details

Same here on SM-T825 after update to Nextcloud Android App V3
Server version Nextcloud 12.0.3 - behaviour didn't change after update to 12.0.4
Devices with previous version of Android App still doing fine.

wschmidhuber on 9 Feb 2018

Confirmed blocking bug on Samsung Galaxy Note 3 (SM-N9005), what a way to get an update, I needed to access some files miles away from home and had this bug happen to me, asked myself what went wrong, opened Google Play, saw Nextcloud as latest updated, acknowledged the source of the problem.

RayOfLight1 on 9 Feb 2018

Confirmed - Blue Vivo 5R running Android 7.0
It keeps redirecting me to the old login method.

rolandixor on 10 Feb 2018

Confirmed - one plus 3T running Android 8.0

matakapo on 10 Feb 2018

Confirming for Android 7.1.1 on Motorola Z Play (XT1635-02), App v3.0.0, Server v12.0.3.

danielb42 on 10 Feb 2018

Confirmed - Samsung Galaxy S8 here.

Bit different though. after the update it contantly gives me the login screen where I only need to fill in the password. After good password submit I get to the usual main folder view, but then after 1,5 second the loging screen comes up again, asking me again for my password. It does see I fill in the correct password, as when I type it wronge it will actually tell me my password is wrong.

Login on windows client, and browser do work normally with same account.

So it is a login loop (or it try's to get authentication for every item in your nextcloud?)
On the PlayStore you see tons of people reporting this bug with a negative review.

This should be fixed ASAP!

acekrystal on 10 Feb 2018

👍4

I use android app v3 RC3 and can successfully login into the server v12.0.5 (with the authentication token)

With the server v13 final, i can't login with the authentication token, the application uses the old authentication method.

Client: Sony Xperia Z5 v7.1.1

mr-bolle on 10 Feb 2018

Confirmed - same error with Xiaomi Redmi Note 3 running MIUI 9.2 connecting to Nextcloud server v10.0.1 plugin on FreeNAS 11.1.

georgep56 on 10 Feb 2018

@georgep56 could you update your server. Nextcloud 10 are out off support.

mr-bolle on 10 Feb 2018

Unfortunately the plugins for FreeNAS 11 are very out of date :-/
I installed the plugin to evaluate nextcloud and I'm building v13 in a
separate jail right now :-)

On 10 February 2018 at 16:17, mr-bolle notifications@github.com wrote:

@georgep56 https://github.com/georgep56 could you update your server.
Nextcloud 10 are out off support.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nextcloud/android/issues/2133#issuecomment-364666999,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABqZKEgDyNJ73LuD_P01C2UVe2avgih7ks5tTcEigaJpZM4SALsD
.

georgep56 on 10 Feb 2018

Confirm that app: 3.0.0 android 7.0 server: 13.0.0 has repeated logon and app is almost unavailable, I hope someone can solve this problem.

dxj728 on 11 Feb 2018

👍2

Confirmed on Pixel 2 Xl, v3.0.0.

Thanks,
-Skyfox

skyfox675 on 11 Feb 2018

Same problem here. Nexus 6 Android 7.1. Server version 12.

EazyDefcon on 11 Feb 2018

I just built a new server instance using 13.0.0 and everything appears to
work OK.

On 11 February 2018 at 17:04, EazyDefcon notifications@github.com wrote:

Same problem here. Nexus 6 Android 7.1. Server version 12.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nextcloud/android/issues/2133#issuecomment-364767561,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABqZKPQvs7QRyMq8MLO9s98wVmpgBjWSks5tTx2EgaJpZM4SALsD
.

georgep56 on 11 Feb 2018

I had this bug with a 12.0.2 Nextcloud server. Upgrading the server to 13 solved the Android bug.

fortytwome on 11 Feb 2018

👍1

Same here with Server 12.0.2 and FP2, Android 6.0.1 (and of course Nextcloud-App 3.0)

Jas2Ma on 11 Feb 2018

This is impacting my Google Pixel on Android 8.1. Server version 12.0.0

user23498723452 on 11 Feb 2018

Same Problem in Galaxy S3 i9300 with Server 12.0.0

ehrenbe4 on 12 Feb 2018

In respect of my closed issue #2147 I want to add:

Confirmed on Motorola G5 with Android 7.0 and Nextcloud-App 3.0 (as well as Passman, Nextcloud/ownCloud News Reader and DAVdroid).

I started with an 12.0.5 and updated to 13.0.0. this morning in hope to relsolve this problem like @georgep56

cpranzl on 12 Feb 2018

@cpranzl thanks for the details. Looking at the fact that all your Android apps are failing to login I'd guess it is a server issue as in problems with urls/routes (apache/nginx config).

AndyScherzinger on 12 Feb 2018

@AndyScherzinger thats what i thought at first, but strangely the Nextcloud Desktop Sync Client on my Laptop is working flawless and i'm also able to connect via browser (Google Chrome 64.0.3282.140, Microsoft Edge 40.15063.674.0, Microsoft IE 11.850.15063.0).

Another clue that the problem lies elsewhere is that new Nextcloud-App (3.0) was able to download my login image and displayed it.

cpranzl on 12 Feb 2018

cc @MorrisJobke any ideas?

@cpranzl the windows client might use other urls (don't know that actually) and the browser definitely uses other URLs or might get redirected since the Android client communications via json most of the time.

AndyScherzinger on 12 Feb 2018

@AndyScherzinger - Not only Desktop Clients and Browsers work fine but also Android devices with clients not yet updated to 3.0 don't show any problems here. It all started with 3.0 and there are plenty of similar complaints in Google Playstore Comments on Nextcloud.

wschmidhuber on 12 Feb 2018

Thats what I see in my nextcloud.log:

{"reqId":"3IQ5EdwLIfjsGcmkNrqa","level":2,"time":"2018-02-12T12:01:58+00:00","remoteAddr":"xxx.xxx.xxx.xxx","user":"--","app":"core","method":"HEAD","url":"\/remote.php\/webdav\/Photos\/uploads\/2018\/02\/","message":"Login failed: 'yyyyyy' (Remote IP: 'xxx.xxx.xxx.xxx')","userAgent":"Mozilla\/5.0 (Android) Nextcloud-android\/3.0.0","version":"13.0.0.14"}

cpranzl on 12 Feb 2018

I think this is now fixed. Sorry folks, will be in 3.0.1 - cc @tobiasKaminsky @AndyScherzinger.

https://github.com/nextcloud/android-library/pull/120

mario on 12 Feb 2018

(At least I hope this is it :P)

mario on 12 Feb 2018

❤1

To make really sure this works prior releasing 3.0.1, can some of you create us a test account and send the credentials to android at nextcloud dot com with a reference to this issue?
Please reply that you send it, I guess 2-3 are enough.

tobiasKaminsky on 12 Feb 2018

❤1

I have sent you credentials.

Jas2Ma on 12 Feb 2018

👍1

@Jas2Ma thank you for your credentials.
On a fresh device I installed 2.0.1, logged in, upgraded to 3.0 and there was no login screen.
It is working just fine.

@mario do you have an idea? (as I used stable-3.0.0 tag, I did not have the fix included, but still it works)

tobiasKaminsky on 12 Feb 2018

👍1

@all what kind of devices and which android version do you use?
And please mention if you use external storage:

is the entire app moved to external storage?
is storage path within the app set to external storage?

tobiasKaminsky on 12 Feb 2018

nextcloud 12.0.3, galaxy note 3 with lineageOS 14.1 (7.1.1/7.1.2), using
nextcloud app 3.0.0

2018-02-12 15:43 GMT+01:00 Tobias Kaminsky notifications@github.com:

@ALL https://github.com/all what kind of devices and which android
version do you use?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nextcloud/android/issues/2133#issuecomment-364942512,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANPdUVKCxT37JRGW4wxwOzWsH1phB1CHks5tUE4EgaJpZM4SALsD
.

RayOfLight1 on 12 Feb 2018

@tobiasKaminsky

On a fresh device I installed 2.0.1, logged in, upgraded to 3.0 and there was no login screen.
It is working just fine.

The problem does not occur until the device is rebooted. (Sorry for not mentioning this detail sooner.)

danielb42 on 12 Feb 2018

@tobiasKaminsky

yesterday we uninstalled the App and returned to 2.0.1. Because of your remark I upgraded again and have no problems atm.

@danielb42: Was the same for me, be after reinstalling everything works fine even after reboot.

Jas2Ma on 12 Feb 2018

Confirmed - Pixel 2xl running 8.1.0 NextCloud Android v3

tfbiii on 12 Feb 2018

@tobiasKaminsky

Server: 12.0.4

1) Galaxy Tab S3 SM-T825, Android 7.0, login-loop since update to App 3.0, also when re-installed with default settings,

2) Galaxy S7 SM-G930F, Android 7.0, using external SD memory, still working fine with App 2.0.0

wschmidhuber on 12 Feb 2018

inside nc client,my storage path says /storage/emulated/0

I'm using default storage config for my Google pixel on android 8.1. nc server 12.0.0

user23498723452 on 12 Feb 2018

https://help.nextcloud.com/t/nextcloud-app-3-0-0-cannot-login-to-nextcloud-server-11-0-5-1/27299
Login issues reported via the forum with Nc11 and App v3:

Unfortunately you updated the app to version 3.0.0 and shot all connections to (at least) nextcloud 11. According to logfile the login works:

{"reqId":"SUml+GU6JIY2QoKjugq3","remoteAddr":"188.193.244.YY","app":"admin_audit","message":"Login successful: \"[email protected]\"","level":1,"time":"2018-02-11T14:02:38+00:00","method":"POST","url":"\/ocs\/v2.php\/apps\/notifications\/api\/v2\/push?format=json&pushTokenHash=9646568dc2c20505b98b317bf3956c76a4d632c1eaa52b4ace3c0959fa40a0758cc6663f6137d39eae090bf8a72ef4e2d5fedf8e8e181092bf3410c78d461c14&devicePublicKey=-----BEGIN%20PUBLIC%20KEY-----%0AMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAiO8R5ovEN6zHs8%2F5phEr%0AwFj%2B03Gq%2BfKR6Yq4V3qNdqxuc%2F5yBClsejTJOaoCxAUbkM5VpitznRSFjwQESHvP%0ArxL3OISZepRBAJZLDq3FWV24WGLcXQFZPoN3m%2BqYIScQK6Q4IYGB%2F3bIvABhiav4%0A2fffGcSyywuiROPn4pjECZd6PPQ8PAqE%2Fl5jZpvibM9JuPGcbe%2F%2Bm1H8TVXAWTUh%0ALfOt8BKI2LdJeaBU9k4MmDtZZ3JCk78nYgV6C3Xw4mSM58C9b8aX6I1xPCJErbsK%0AipA7OG7ixCMAB%2F2pN1FGQzSEC1PSyEb3RSRFKT8VfJJWmBSkzjTFInDR0tA0HKwC%0AGwIDAQAB%0A-----END%20PUBLIC%20KEY-----%0A&proxyServer=https%3A%2F%2Fpush-notifications.nextcloud.com","user":"[email protected]","version":"11.0.5.1"}

But then:

{"reqId":"sghjUlD\/8F\/aFr1yqZA6","remoteAddr":"188.193.244.YY","app":"webdav","message":"Exception: {\"Message\":\"HTTP\\\/1.1 401 CSRF check not passed.\",\"Exception\":\"Sabre\\\\DAV\\\\Exception\\\\NotAuthenticated\",\"Code\":0,\"Trace\":\"#0 \\\/srv\\\/user-local\\\/cloud.default\\\/owncloud\\\/apps\\\/dav\\\/lib\\\/Connector\\\/Sabre\\\/Auth.php(154): OCA\\\\DAV\\\\Connector\\\\Sabre\\\\Auth->auth(Object(Sabre\\\\HTTP\\\\Request), Object(Sabre\\\\HTTP\\\\Response))\\n#1 \\\/srv\\\/user-local\\\/cloud.default\\\/owncloud\\\/3rdparty\\\/sabre\\\/dav\\\/lib\\\/DAV\\\/Auth\\\/Plugin.php(199): OCA\\\\DAV\\\\Connector\\\\Sabre\\\\Auth->check(Object(Sabre\\\\HTTP\\\\Request), Object(Sabre\\\\HTTP\\\\Response))\\n#2 \\\/srv\\\/user-local\\\/cloud.default\\\/owncloud\\\/3rdparty\\\/sabre\\\/dav\\\/lib\\\/DAV\\\/Auth\\\/Plugin.php(150): Sabre\\\\DAV\\\\Auth\\\\Plugin->check(Object(Sabre\\\\HTTP\\\\Request), Object(Sabre\\\\HTTP\\\\Response))\\n#3 [internal function]: Sabre\\\\DAV\\\\Auth\\\\Plugin->beforeMethod(Object(Sabre\\\\HTTP\\\\Request), Object(Sabre\\\\HTTP\\\\Response))\\n#4 \\\/srv\\\/user-local\\\/cloud.default\\\/owncloud\\\/3rdparty\\\/sabre\\\/event\\\/lib\\\/EventEmitterTrait.php(105): call_user_func_array(Array, Array)\\n#5 \\\/srv\\\/user-local\\\/cloud.default\\\/owncloud\\\/3rdparty\\\/sabre\\\/dav\\\/lib\\\/DAV\\\/Server.php(466): Sabre\\\\Event\\\\EventEmitter->emit('beforeMethod', Array)\\n#6 \\\/srv\\\/user-local\\\/cloud.default\\\/owncloud\\\/3rdparty\\\/sabre\\\/dav\\\/lib\\\/DAV\\\/Server.php(254): Sabre\\\\DAV\\\\Server->invokeMethod(Object(Sabre\\\\HTTP\\\\Request), Object(Sabre\\\\HTTP\\\\Response))\\n#7 \\\/srv\\\/user-local\\\/cloud.default\\\/owncloud\\\/apps\\\/dav\\\/appinfo\\\/v1\\\/webdav.php(61): Sabre\\\\DAV\\\\Server->exec()\\n#8 \\\/srv\\\/user-local\\\/cloud.default\\\/owncloud\\\/remote.php(165): require_once('\\\/srv\\\/user-local...')\\n#9 {main}\",\"File\":\"\\\/srv\\\/user-local\\\/cloud.default\\\/owncloud\\\/apps\\\/dav\\\/lib\\\/Connector\\\/Sabre\\\/Auth.php\",\"Line\":220,\"User\":\"[email protected]\"}","level":0,"time":"2018-02-11T14:02:57+00:00","method":"PROPFIND","url":"\/remote.php\/webdav\/","user":"[email protected]","version":"11.0.5.1"}

All from the same IP with the same account, 20 seconds later failed.
Why is that?

AndyScherzinger on 12 Feb 2018

👍1

Confirmed on Samsung Galaxy S8, Nextcloud 12. Same pattern.

etaijoverlap on 12 Feb 2018

I seem to find some clues that whenever I log in to a connection with a domain name, it keeps flashing back in, but when I log in using IP, it seems to be all right

dxj728 on 13 Feb 2018

I suspect that you the cause of this is
01-09 14:33:02.028 1155 2923 W AccountManagerService: insertAccountIntoDatabase: Account {[email protected], type=nextcloud}, skipping since the account already exists
Logging in with IP address instead of server url will create a new account.
The main questions still remains why is login popping up at all: why does android app think you need to re-authenticate.

Can you provide us additional infos via logcat? Maybe we see there a reason for this
https://github.com/nextcloud/android/blob/master/README.md#getting-debug-info-via-logcat

tobiasKaminsky on 13 Feb 2018

Can some of you try to update to latest stable 12.0.5?

tobiasKaminsky on 13 Feb 2018

Background of this is, that due to a bug, we send a "wrong"/too new user agent, which will lead the server to refuse it.
This is fixed with 12.0.5 release, which allows both user agents.

In parallel android client 3.0.1 will restore the old behaviour, but to narrow down the issue and to verify that the user agent is the only problem, we need some users to upgrade 12.0.5.

tobiasKaminsky on 13 Feb 2018

I have updated android app from 2.0.1 to 3.0.0 with nc 12.0.5. No problems I don't have to reauthenticity the login.

Micha-Btz on 13 Feb 2018

@tobiasKaminsky This could be somehow related to #1531: After an update even v3.0.0 can reside in the external storage with the complications described in #1531. I was able to reproduce this by updating from v2.0.1 (installed on adopted storage) to v3.0.0.
_Edit: I mentioned the Android PackageHelper before, but I noticed that it somehow doesn't fit to my observation._

At least the following comment sounds like this problem:

The problem does not occur until the device is rebooted.

To determine if that is the problem for some of the users here, it would be helpful to know if they see the Nextcloud app in Android Settings -> Accounts.

bastei on 13 Feb 2018

On my Galaxy Tab S3 SM-T825, Android 7.0, where the login-loop occurs since update to App 3.0 the App is shown in Accounts (but can't synchronize). I uninstalled and reinstalled App 3.0 so all settings should be default. And I didn't reboot the device before the login-loop occurred first.

wschmidhuber on 13 Feb 2018

I updated nextcloud from 12.0.3 to 13.0.0 and as of now, everything is
working back again with nextcloud-android 3.0.0

2018-02-13 12:46 GMT+01:00 wschmidhuber notifications@github.com:

On my Galaxy Tab S3 SM-T825, Android 7.0, where the login-loop occurs
since update to App 3.0 the App is shown in Accounts (but can't
synchronize). I uninstalled and reinstalled App 3.0 so all settings should
be default. And I didn't reboot the device before the login-loop occurred
first.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nextcloud/android/issues/2133#issuecomment-365243564,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANPdUQRLKGf-uCS8OpilPQDuCp4Tz68bks5tUXYggaJpZM4SALsD
.

RayOfLight1 on 13 Feb 2018

@bastei which device do you use?
To prevent this, we even introduced https://github.com/nextcloud/android/blob/stable-3.0.0/src/main/AndroidManifest.xml#L76 which should in fact be not necessary as the default is to have it installed only internal.

tobiasKaminsky on 13 Feb 2018

The login loop on the Android client prompted me to update my server instance to v13. Instead of a constant loop I now only have to reauthenticate every time a periodic sync fails :s

I'm on a Oneplus One running Lineage OS 14.1, Android 7.1.2

If it helps, see attached screendump of the log.
nextcloud_log

Hoping v3.0.1 will be pushed to F-droid as fast as possible!

haverholm on 13 Feb 2018

Solved here. For my Galaxy Tab S3 SM-T825, Android 7.0, where the login-loop occured since update to App 3.0, updating from Server 12.0.4 to 12.0.5 solved the problem.

wschmidhuber on 13 Feb 2018

@haverholm Can you create us a test account and send the credentials to android at nextcloud dot com with a reference to this issue?

@wschmidhuber thank you for confirming that upgrading to 12.0.5 fixes it.

tobiasKaminsky on 13 Feb 2018

@tobiasKaminsky Done, check your inbox.

haverholm on 13 Feb 2018

I have the same problem
Android client 3.0.0
Wileyfox Spark+
Android 7.0

I'm pretty sure the app is not on external storage on the phone.
Settings->Apps->Nextcloud says 505MB used in internal storage, of which App is 26MB and data 479MB.
Likewise the storage path is /storage/7369-B726/Android/data/com.nextcloud.client/files which I think means it is on internal storage on the phone.

I'm connecting to Nextcloud 11.0.3 running on a Raspberry Pi2.
I tried updating this to 12.0.5 but after the update I was not able to access Nextcloud from the web interface at all so I had to revert back to the pre-upgrade backup.

This is only my home server, so not mission critical and I will try to update the server when I can, but it would be nice to get the android app working, or temporarily disable it trying to auto-upload photos and backups. Calender and contact syncing using WebDav seems unaffected.

DAveShillito on 13 Feb 2018

@tobiasKaminsky I do see nextcloud in the list of accounts on my Google pixel.

user23498723452 on 13 Feb 2018

@tobiasKaminsky Found a possible fix! my nextcloud is hosted at home and I saw the issue when trying to access the site using a public dns name WHILE AT HOME. which works fine from a routing perspective. the nc website is being nated to an internal ip, the nc cert refers to the public dns name.

I've just tested for the first time from the internet, and I was prompted to enter my username/password as needed.

it appears to have worked. I'll update if login prompts continue.

user23498723452 on 13 Feb 2018

@DAveShillito a "random" storage name is often the external sdcard, whereas the internal storage is referenced as /storage/emulated/(0)
As mentioned, we will provide 3.0.1 soon. Or 12.0.5 will fix it also. Maybe it is worth to investigate the problem of 12.0.5.

@user23498723452 I think this is another problem. I discussed it earlier this day on IRC. The web browser on android could also access the NC website, but not android client.
As this is not reproducable in every scenario, I could not provide a fix :-/

tobiasKaminsky on 13 Feb 2018

@tobiasKaminsky Thanks for the quick reply.
The "random" storage name initially made me think it was SD storage, but I was confused that Settings->Apps->Nextcloud says 505MB used in internal storage.
Not that it matters, I only mentioned it in case it helped your diagnosis.

As I said I'm not mission critical so I can wait for 3.0.1.
I will definitely be looking at getting 12.0.5 working (or even jumping to 13) but that looks to be a bigger issue for me to fix with a manual update, or starting my server from scratch again. I just tried to do it quickly using the updater app to see if it fixed the login issue.

Thanks to everyone working on this.
Generally my experience with Nextcloud and the Android client has been flawless over the many years I've been using it, unfortunately these minor hiccups occur, but you are all obviously on them.
Thanks again. :)

DAveShillito on 13 Feb 2018

@bastei which device do you use?

I use an (unofficial) LineageOS 14.1 (7.1.2) installation. I left a note at the other ticket concerning the app location after updates. Seems that this is not the main culprit of the problems discussed here, but I wanted to make you aware that this could lead to similar problems.

bastei on 13 Feb 2018

@tobiasKaminsky not sure what you mean. I'm testing this issue from home again and it has returned. I did reboot the phone to be sure. it seemed to be working before I rebooted it.

user23498723452 on 13 Feb 2018

@haverholm I could not reproduce it. I could sync, download/upload files and even left the device on for ~2 hours, but never got a log out :-/

tobiasKaminsky on 14 Feb 2018

@tobiasKaminsky And in the meantime the loop has ceased here, too. I did a LineageOS system update, but surely that isn't what fixed it? smh

haverholm on 14 Feb 2018

I only had this one time during testing and there the error message in logcat was:

AccountManagerService: insertAccountIntoDatabase: Account {[email protected], type=nextcloud}, skipping since the account already exists

So maybe this was resolved / cleaned via the system upgrade.

tobiasKaminsky on 14 Feb 2018

3.0.1 is now released.
Please test and report back if it is working for you

tobiasKaminsky on 14 Feb 2018

👍1

@tobiasKaminsky I just downloaded the 3.0.1 update and all seems good.
My previously stalled auto uploads have completed, and I can browse files without the login screen popping up.
Thanks to everyone for the quick fix :)

DAveShillito on 14 Feb 2018

🎉2 👍2

@tobiasKaminsky where I could download the latest apk version? On f-droid and Google play I find only the 3.0.0

mr-bolle on 14 Feb 2018

with Lineageos 7.1.2 on NC 11.0.1 and 3.0.1 android app it won't work.
In login window "Secured connection established" is shown. Then I input the password and after connect button Message "Couldn't found host" is shown. Both here in german, means translation could not exact the same.

Siggi0904 on 14 Feb 2018

@mr-bolle you should see it on GPlay while f-droid will likely need some days to build and publish.

AndyScherzinger on 14 Feb 2018

@Siggi0904 this seems to be another problem.
Please open up a new issue.

tobiasKaminsky on 15 Feb 2018

Since @DAveShillito tested the new version successfully and @Siggi0904 has got -I think- another error (I guess dns settings, so please open a new one), we can close the issue. Just feel free to reopen if someone got some errors.

xXSTrikeXx on 15 Feb 2018

I'm still on app version 3.0.0 but it started working for me just now while getting some other problems fixed. Nextcloud version 12.0.5.

The 2 things I did different was :

I cleaned my Database Table "oc_bruteforce_attempts" as X-Forward seems to not work yet and it caused my login to be really slow (40sec+). So It could actually have been a time out on the app side.
I got a login screen on the nextcloud app where I had a little check box to "stay signed in". I used that for a change, and for now it suddenly started working.

Hope this might give some directions.
Will try the app 3.0.1 soon too, but since I saw I was still on 3.0.0 I thought it might be worth sharing.

acekrystal on 16 Feb 2018

3.0.1 appears to have fixed the issue. I've given it a couple of days to be sure.

user23498723452 on 16 Feb 2018

3.0.1 fixes one issue that led to the recurring logins which only happens in that scenario when the server version is < 12.0.5. So 3.0.0 won't have the issue in case the server is up-to-date.

AndyScherzinger on 16 Feb 2018

To be clear, this was the most frustrating bug as it preventing me from accessing or syncing my files.

Not only could I not use the app, but I couldn't fix the issue as there is no way to roll back on a Google Play store apk. Sure, one could install an untrusted apk, but that isn't acceptable for many. I'm unaware of any supported copies of all the actual APKs released through the play store.

While I appreciate the efforts of the NC dev team, it seems this points out some failure to robustly test all of your supported versions. Only testing the latest version is not acceptable and I hope that NC learns the importance of this.

Personally, I'm putting this app back on to the list of apps requiring manual update approval. I cannot go days without being able to sync my files. Please consider sharing ways clients can roll back to older versions of the Google Play store apk.

user23498723452 on 16 Feb 2018

👍1

@AndyScherzinger now I get the update over f-droid, on GPlay this version isn't available for me (Android 7.1.1 Sony Xperia Z5 Stock ROM)

maybe it would be possible to upload this application on https://download.nextcloud.com/

mr-bolle on 16 Feb 2018

@mr-bolle @user23498723452 all GPlay releases are available via direct download @ https://download.nextcloud.com/android/ so this way you can manually downgrade since GPlay doesn't provide such an mechanism itself. These apks are signed so they are the same apks as the ones published on GPlay.

While I appreciate the efforts of the NC dev team, it seems this points out some failure to robustly test all of your supported versions. Only testing the latest version is not acceptable and I hope that NC learns the importance of this.

We didn't just test the latest version. Nc server Life Cycle is support for the last 2 major versions which would have been at the time of publishing Nc 13.0.0 and Nc12.0.5, so we did test the supported versions, while I agree that this issue shouldn't have made it to production. On the other hand there were over 5730 testers via the beta program who ran this release against their servers without reporting login issues. So that would mean they didn't report it or all of them ran 12.0.5+.

AndyScherzinger on 16 Feb 2018

@tobiasKaminsky can you publish the latest 3.0.1 on the download site please :)

AndyScherzinger on 16 Feb 2018

Im in beta channel, too. I've upgraded few days before publishing stable to nc 13.0.0 and I havent got any time a login loop. So well, in todays time every producer have got their own os of a customization from android. For example huawei with emui. Then differents android versions and so on. So in my opinion feel free to get in the beta team, to improve beta. Then you could be able to compare open source with closed source, for example dropbox or microsoft.

xXSTrikeXx on 16 Feb 2018

Here these bug still exists.
With 3.0.2 the login windows still occours.

Please reopen these bug and check what happend there.

Siggi0904 on 28 Feb 2018

@Siggi0904
Please check your table of bruteforce attempts. Maybe this results the behavior. What happens when you use a different device?

xXSTrikeXx on 28 Feb 2018

Brute force table cleaned. Same behavior.

Siggi0904 on 28 Feb 2018

I have this behaviour too. The 3.0.2 update fixed the "could not find host" error but now I constantly get the login box. Put password in and hit OK, logs in, but as soon as I touch any button it goes back to login box.

ownCloud server v10.0.4
NextCloud Android app 3.0.2
Android version 7.0
Samsung Galaxy S7

I can provide a test account. Please let me know where to send the details

janipewter on 28 Feb 2018

If I undestand @tobiasKaminsky correctly ownCLoud 10 will keep failing. The reason is that with the introduction of E2EE the Android client now uses a different (Nextcloud) user agent within the server requests and the ownCloud server will block them because ownCloud's firewall (like Nextcloud's) will check the user agent and since it is not "ownCloud-Useragent" anymore it'll deny the requests.

But we are still working on finding a solution for that, not sure though if and when we might have one.

AndyScherzinger on 28 Feb 2018

I have migrated to Nextcloud server instead. No idea why I wasn't using it in the first place, but now everything works perfectly.

Thanks

janipewter on 2 Mar 2018

👍1

After the 3.0.2 upgrade this problem has returned for me as well.

Android client 3.0.2
Wileyfox Spark+
Android 7.0

I'm connecting to Nextcloud 11.0.3 running on a Raspberry Pi2.
I do intend to update to Nextcloud 13 when possible, but when I tried updating to 12.0.5 I was not able to access Nextcloud from the web interface at all so I had to revert back to the pre-upgrade backup.

DAveShillito on 3 Mar 2018

I can confirm that I had this issue as well with the 3.0.2 nextcloud client for android (with 12.0.x as server). After upgrading to nextcloud 13.0 serverside the issue is gone.

sukosevato on 4 Mar 2018

I also have this issue with a Motorola Moto Z (Android 7.1.1) and Nextcloud app 3.0.3. Server version is 11.02.

gruhland on 9 Mar 2018

Hi, problem still exists. No solution possible?
Where can I test a NC 12 or NC 13 server with these app?

Siggi0904 on 18 Mar 2018

@Siggi0904 https://demo.nextcloud.com It´s build for a hour ;)

xXSTrikeXx on 18 Mar 2018

@gruhland
Nextcloud Server 11.02 will be EOL:
https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule

I suggest to update with the last update (https://help.nextcloud.com/t/nextcloud-13-0-1-12-0-6-and-11-0-8-available-with-improved-password-protection/28970) to 11.0.8 or directly to 13 😉

xXSTrikeXx on 18 Mar 2018

🎉1 👍1

Admin says, it's much work to upgrade from 11 to 12 or thirteen. :-)
Many manual work to and after upgrade.
Hope he will upgrade next time to 13. I'll be in contact with him.

Siggi0904 on 18 Mar 2018

😄1

@Siggi0904 Every update will also enhance the security 😉
It´s like Microsoft XP. You can continue to use it, but you won´t get updates, especially security patches for it, since it´s EOL. So it´s a risk on your own security. When you stay at one version, you need also to stay on one version with other components. In this case the android app. You updated it now and now the server is out of date while using the latest version of android client. Thats dangerous. I think the easiest way is to backup all and update atleast to version 12.x.x. Thats not such a big step and work with the webupdater. He doesn´t need to program (& testing) anything, so it´s not so much work 😁

xXSTrikeXx on 19 Mar 2018

@xXSTrikeXx the problem is that my 11.x installation do not show me the update for 12 on the stable channel

c33s on 19 Mar 2018

the problem is that my 11.x installation do not show me the update for 12 on the stable channel

Any idea @MorrisJobke ?

AndyScherzinger on 19 Mar 2018

Any idea @MorrisJobke ?

We put 11.0.8 to the stable channel last Monday to get maybe more people at least to a stable 11 release, because 12.0.x was served before that since autumn last year. We will soon move this to a stable12 release again (within 1 or 2 weeks). If you want to update now: use the beta channel as there are no betas out right now and this will just give you 12.0.6 ;)

MorrisJobke on 19 Mar 2018

👍1

I created a test version, which can be installed as an upgrade to the existing app.
Can someone with at least Android 5.1 (Lollipop) can test it?

Please do this steps:

verify that with current 3.1 version the problem still occurs
install test version
try it again

Link to download test version: https://cloud.nextcloud.com/s/fazWbsg8LoAKCtE
(it is signed by us and will replace 3.1 version with 3.1.1, so it will not interfere with upcoming 3.2. You have to enable "allow installation from unknown sources").

tobiasKaminsky on 25 May 2018

I will test this behavior the next day. Possible Android Release 6, 7.1 and 8.0

Edit: with the current v3.1. and Server v13.0.2 i don't have this issue. More tests with other devices i start tomorrow

mr-bolle on 25 May 2018

❤1 👍1

Hi,
I am using the Android Nextcloud 3.1.0, Server v11.0.2 and Android 6 and I have exactly the same problem commented here. @mr-bolle, is it a client bug or do I need to update the server? Thanks

yolanda93 on 27 May 2018

Hi, @yolanda93 since some hours i try to find the reason to reproduce the problem. I would suggest to upgrade the Server. It is recommended to use the latest stable release 13.0.2.

To you use docker for your nextcloud Server or you run this directly on your host server?

mr-bolle on 27 May 2018

Please don't let the guys upgrade the server. It should be fixed with older versions too.
Many installation are at older versions like 11 or 12 and these version should be work too.

It is an android app authentication problem, not a server side problem.

Siggi0904 on 27 May 2018

@Siggi0904 please remember that the Server v11 are out of support. >> Maintenance and Release Schedule

I try different server, on some the authentication works, on some not. (especially with App Token)

mr-bolle on 27 May 2018

Please don't let the guys upgrade the server. It should be fixed with older versions too.
Many installation are at older versions like 11 or 12 and these version should be work too.

It is an android app authentication problem, not a server side problem.

@Siggi0904 this isn't true, well true in some scenarios what will never work again is anything below 11.0.8 same goes for Nc12 if it is on an old patch level for a simple reason: The Android client uses a new user agent string due to the e2ee feature and will thus be blocked by user agent string on older server so it is a server issue and like @mr-bolle said even Nc11 is out of support so these servers will never work again with the Android client (no matter the reason being it client or server).

It is correct to some extend since the client now also changes its Android requirements so it has to be installed on the internal memory for upgraded Android clients that formerly installed it on the sd card this can lead to issues with the client finding the account again (not found in the database) while after a successful re-login the saving of the account fails in the same database since it is already in there (which is then a client issue, yes).
A way to workaround this issue is to either put a / at the end of the URL or change to upper/lowercase writing of the username. For users with rotted phone another (more complex) way is to remove the account manually from the account database but like I said that is more complex and needs technical know-how.

So the solutions is simply and might well be frustrating. If you lock yourself to a certain server version (which is a security risk!) you also lock yourself to a specific client release, for Android that be v2.

On "clean", fresh phones a fresh installation of the app should definitely work with v3 for Nc 11,12,13 them being on their respective, latest patch level.

AndyScherzinger on 27 May 2018

I have upgrade the server to 12.0.7 and with this version seems to work fine.

yolanda93 on 27 May 2018

👍2 ❤1

Glad to hear that @yolanda93 :heart:

AndyScherzinger on 27 May 2018

Hi,

now i try several differen Server with the last App and the Login Alpha (i use Docker Container - Link to docker-compose into Server Column)
Often i have Problems to login with App-Token Screenshot

_Note_: Now i found out that the User Name with Password Access is not Case sensitive, and Login with the App Token is Case Sensitive, That's why i get so often the Error 401 during Login with App Token :neckbeard:

mr-bolle on 27 May 2018

Note: Now i found out that the User Name with Password Access is not Case sensitive, and Login with the App Token is Case Sensitive, That's why i get so often the Error 401 during Login with App Token

🙈 @rullzer @blizzz Could you confirm this?

MorrisJobke on 27 May 2018

@MorrisJobke it is user_id vs loginname fun. (Which on the main backend are somewhat interconnected).

Anyway as far as I know @tobiasKaminsky has patches that will fetch the user_id on login and use that when required.

rullzer on 27 May 2018

👍1

@mr-bolle thank you for testing, so it seems that the approach does not work.

@rullzer afaik we fetch & use user_id only for dav related stuff, so this is independent from login.
Can you open up a new issue, assign it to me, with reproducible stable? <3

tobiasKaminsky on 28 May 2018

with reproducible stable? <3

I guess he means "reproducible steps" 😉

MorrisJobke on 28 May 2018

👍1

Now that I have an affected device, I spent several hours in debugging and trying to understand the problem.
As always there are so many different combinations, that there may be several causes, but one of it is a bug that does not entirely remove a custom account when uninstalling the app.
Also the move from internal to external storage (and vice vera) can cause this.
This also affects other apps, e.g. Dropbox.

Some technical background:
Androids own account manager has a stale account in its database. When querying if a given account exists, our app gets none back, assuming that we have to add it.
This then will fail as the account manager cannot add an account twice with the same name.
Also programatically removing the old account will not work.
But the stored account name is case sensitive and this is our chance.

The internal account's name is built from the username and server address, e.g "tobias" and "cloud.server.com" --> [email protected].
The username is the name that the admin gave the user when creating the account.
The login flow returns always the username, e.g. if you enter your email address as login, we will internally build the account with the returned username.
However it seems that the login flow is returning the username exactly as entered.

So if you have an account [email protected] and this is causing the login loop, you can try to login with "TOBI" or "TOBI " or "ToBi" and all should allow you to login.
Please note that due to androids bug all older account names are burnt and will not work, so if you have done this multiple times, it may be that no suitable combination is left.

TL;DR: It is a bug in Androids Account Manager system, which we cannot solve, but only try to circumvent: login with uppercase username or append a whitespace.

tobiasKaminsky on 13 Jun 2018

TL;DR: It is a bug in Androids Account Manager system, which we cannot solve, but only try to circumvent: login with uppercase username or append a whitespace.

How about reporting this upstream? 😉

MorrisJobke on 13 Jun 2018

This is already known by android and already fixed with Nougat, according to their bug tracker.
But with the heterogeneous versions, not all devices will get Nougat. And some companies patch their systems very heavily, and even sometime ignore bug fixing patches…

tobiasKaminsky on 13 Jun 2018

🎉1

So I read that there is no manual way to remove the stale accounts from the phone? (I've got Android 7.0).
The issue seems to be the case because changing different upper/lower case variants worked for some time, but I think i used them all (very short account name, unfortunately)

McAviti on 19 Jul 2018

So I read that there is no manual way to remove the stale accounts from the phone?

You should be able to see the Nextcloud account within Android's settings -> Accounts and shold be able to remove it/them from there + (not sure!) also clear the data of the Nextcloud app via Android's settings -> Apps

AndyScherzinger on 19 Jul 2018

👍1

Thanx, Andy!

In the account settings there was none for nextcloud, but I deleted the app's data and then login worked immideately.

~klemens

McAviti on 19 Jul 2018

🎉1

I had this problem, but was able to fix it by creating the account from the Android account manager.

After having the problem, I opened account manager, then removed the failing account, then created a new account - which loaded the NextCloud login page - and after logging in that way, it worked fine.

Earl-Brown on 20 Jul 2018

👍2

The issue is showing on app version 3.3 android version 8.1 (on one+ 5T) together with server version 13.0. 5 , as well as 13.0.6 and 14.0.0. no stale account inside the phone. multiple fresh installs. normal login works but gets forgotten, app password shows i should login first, if i remove all sessions it just reverts back to 'connect your account' screen, no warning or info pallette. i also observed the 'revert to old login method' is always there, even when allready logged in with normal login. (all methods tried with normal,camelcased and capital username )I hope someone can help with the info provided,