You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, sorry to bother you again, but I noticed that with the latest version even though Classic Login was in general fixed (Tested against Nextcloud 16) attempting to Log In with classic Login against a Nextcloud 14 installation fails.
Expected behaviour
Credentials should be accepted, and the user taken to the main view
Actual behaviour
An alert is shown with a 404 error. This appears to be caused by the lack of login flow support on NC14
Steps to reproduce
Attempt to Login with classic Login against a Nextcloud 14 server.
Reasoning or why should it be changed/implemented?
Either the server version check should show a warning for incompatible server versions (if this is the policy), or the legacy login approach should be kept available.
iOS version
13.3.1
App version
Testflight 2.26.0
Nextcloud version: (see Nextcloud admin page)
Nextcloud 14.0.8.2
The text was updated successfully, but these errors were encountered:
Hi, sorry to bother you again, but I noticed that with the latest version even though Classic Login was in general fixed (Tested against Nextcloud 16) attempting to Log In with classic Login against a Nextcloud 14 installation fails.
Expected behaviour
Credentials should be accepted, and the user taken to the main view
Actual behaviour
An alert is shown with a 404 error. This appears to be caused by the lack of login flow support on NC14
Steps to reproduce
Attempt to Login with classic Login against a Nextcloud 14 server.
Reasoning or why should it be changed/implemented?
Either the server version check should show a warning for incompatible server versions (if this is the policy), or the legacy login approach should be kept available.
iOS version
13.3.1
App version
Testflight 2.26.0
Nextcloud version: (see Nextcloud admin page)
Nextcloud 14.0.8.2
The text was updated successfully, but these errors were encountered: