Login Flow unavailability treated as error against NC 14
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 13
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing classic Login against a Nextcloud 14.0.8.2 server and inspect the app's login-flow and server-version handling. Done means credentials are accepted and the main view opens, or an explicit incompatibility warning is shown while a supported legacy login path remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100