Client does not reauthenticate when token becomes invalid
Open
@mpivchev is already working on this.
Since Jan 30, 2025.
bug
- Dominant language
- Swift
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 13
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
- Connect the iOS app to a Nextcloud instance
- Go the security settings and delete the app password of the client
- Continue to use the client
Expected behaviour
The client asks to reauthenticate with login flow or at least show an error.
It should not send more requests to the server
Actual behaviour
The client continues to send requests which fail to authenticate with a 401, this then leads to brute force protection at some point.
Logs
If applicable, you can post the iOS app or server logs (removing any sensitive information).
Reasoning or why should it be changed/implemented?
Environment data
iOS version: 18.2.1
Nextcloud iOS app version: 6.2.3.1
Nextcloud server: daily
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.
Assessment
This issue has not been assessed yet.