Login loop issue - possible solution (serious serious bug)
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 13
Description
A lot of people seem to be having login loop issues on the latest version of the iOS client.
I think I found out the issue:
If any permission is not "allowed", the iOS client will login loop.
Scenario #1:
I have the external storage mount "/media/mount1" and share the folder "/media/mount1/test" with "usr1" and give them "can create" permission only.
If "usr1" logins using the iOS client and then deletes the "test" folder (they shouldn't even see the delete option in the first place)....the iOS client will immediately go into a login loop.
Scenario #2:
I have the external storage mount "/media/mount1" and share the folder "/media/mount1/test" with "usr1" and give them no permissions (no "can create", "can edit", "can change", "can delete" and thus they should only be able to view the folder).
If "usr1" logins with iOS client, they can see the contents of the "test" folder. If they try to upload files to "test" folder (they shouldn't even see the upload button because there is no permission).....the iOS client will immediately go into a login loop.
Once the iOS client goes into login loop, the only way to get out of it is to uninstall the app and reinstall. There is no way to close the login prompt, if you close it, it will popup immediately again.
It seems the iOS client is not retrieving the "proper" permissions of a file/folder and then tries to execute a action that is not allowed and when it fails it goes into login loop.
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
No files, tests, or entry points are named. Start by reproducing the login loop in the iOS client with denied folder permissions, including failed delete and upload actions, then trace the resulting authentication flow. Done means unauthorized actions are handled without repeatedly showing the login prompt or requiring app reinstallation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- authorization, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100