Login fails with error: "Current user is not logged in"
Nobody has claimed this yet.
- 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
- Start Nextcloud app
- Proceed login either with password, app password or qr-code
Expected behaviour
I am getting logged in
Actual behaviour
Login fails with error.
However, device is visible in the nextcloud backend which would indicate that some sort of succesfull authentication has taken place.
Logs
{"reqId":"lNk23DJtwa98xTASrmMy","level":2,"time":"2025-07-06T10:27:30+00:00","remoteAddr":"192.168.188.11","user":"--","app":"no app in context","method":"POST","url":"/index.php/login","message":"Login failed: andi (Remote IP: 192.168.188.11)","userAgent":"Mozilla/5.0 (iOS) Nextcloud-iOS/7.0.0","version":"31.0.6.2","data":[]}
Environment data
iOS version: iOS 18.6
Nextcloud iOS app version: 7.0.0
Server operating system: Arch Linux Arm
Web server: Apache
Database: MariaDB
PHP version: 8.4.10
Nextcloud version: 31.0.6.2
Screens
Screencast iOS App:
https://github.com/user-attachments/assets/7cf280f7-a366-4546-8561-d424f449cd78
Screenshot Webb App:
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 login in the Nextcloud iOS app 7.0.0 against the stated environment, testing password, app-password, and QR-code flows. Review the supplied server log alongside the app behavior; done means login succeeds without the “Current user is not logged in” error and the device remains correctly registered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100