nextcloud / nextcloud/desktop

AppImage deletes user credentials if a not found response is recieved from the server.

Open
#10,035 2 comments 0 reactions 0 assignees View on GitHub
1. to develop bug
Dominant language
C++
Stars
3.9k
Forks
1k
Avg merge
1d 17h
Merged PRs (30d)
123

Description

### ⚠️ Before submitting, please verify the following: ⚠️

- [x] This is a **bug**, not a question or a configuration issue.
- [x] This issue is **not** already reported on Github (I have searched for it).
- [x] Nextcloud Server and Desktop Client are **up to date**. See [Server Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) and [Desktop Releases](https://nextcloud.com/install/#install-clients) for supported versions.
- [x] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/)

### Bug description

While connected to a Nextcloud server running version 33.0.2.2, the 33.0.4 AppImage client will delete it's stored user credentials if it receives a 404 - Not found response from the remote wipe check endpoint. This occurs after the user's current session token expires server-side and the client needs to login again using it's cached credentials.

As a result, the user is forced to reauth the next time that the AppImage is started. (Usually after the next reboot of their machine.) Only for this bug to occur again once the session token expires. Resulting in a reauth loop occurring once every day, and very annoyed end users.

_Obviously_, the Nextcloud Server should be updated, but this behavior still shouldn't occur. The lack of an endpoint on the server, after successful authentication, shouldn't result in an endless reauth loop for end users who have no control over what version of the server is running.

### Steps to reproduce

1. Authenticate the client to a Nextcloud Server running 33.0.2.2.
2. Wait for the session token to expire.
3. Reboot the client.

### Expected behavior

As this missing endpoint doesn't prevent initial sync, or login from working, it should keep it's valid credentials and not demand a reauth.

### Which files are affected by this bug

N/A - Affects all use of the client.

### Operating system

Linux

### Which version of the operating system you are running.

Debian 13

### Installation method

Official Linux AppImage

### Nextcloud Server version

33.0.2.2

### Nextcloud Desktop Client version

33.0.4

### Did this occur after an update or on a clean installation?

Major version update (i.e. 4.0.0 → 33.0.0)

### Are you using the Nextcloud Server Encryption module?

No

### Are you using an external user-backend?

- [x] Default internal user-backend
- [x] LDAP or Active Directory
- [x] SSO - SAML
- [ ] Other

### Nextcloud Server logs

```shell

```

### Additional info

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.