Skip to content

[Bug]: renaming files in nextcloud causes issue #8298

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
5 of 8 tasks
JL710 opened this issue May 24, 2025 · 4 comments
Open
5 of 8 tasks

[Bug]: renaming files in nextcloud causes issue #8298

JL710 opened this issue May 24, 2025 · 4 comments

Comments

@JL710
Copy link

JL710 commented May 24, 2025

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

Bug description

When a synced directory is renamed in the nextcloud there is a sync issue that can not be resolved.

Steps to reproduce

  1. sync a directory
  2. rename it in the web interface
  3. look at the desktop client and the caused issue

Expected behavior

When changing the name I either expect it to automatically adapt that or to give me an option to reselect the nextcloud dir without having to do a complete resync.

Operating system

Debian and Windows (both have the issue)

Package

Official Windows MSI or app image

Nextcloud Server version

30.x.x

Nextcloud Desktop Client version

3.16.4

Is this bug present after an update or on a fresh install?

Fresh desktop client install

Are you using the Nextcloud Server Encryption module?

Encryption is Enabled

Are you using an external user-backend?

  • Default internal user-backend
  • LDAP/ Active Directory
  • SSO - SAML
  • Other
@Mika-6-9
Copy link

Maybe related : #8179 (comment)

@Rello
Copy link
Contributor

Rello commented May 27, 2025

Hello,

do you have more details?
Screenshots? normal folder or readonly or group folder or share?

@nilsding
Copy link
Member

I could reproduce it:

  1. create a new folder anywhere (named mine Sync folder to rename)
  2. add a new Folder Sync Connection for the new folder
  3. rename that folder e.g. via the web interface (new name: Sync folder that has been renamed)
  4. the next sync will still try to use the old folder name, discovery fails with 404:
2025-05-27 11:06:09:010 [ info nextcloud.sync.networkjob.lscol /home/jyrki/src/nextcloud/desktop/src/libsync/networkjobs.cpp:377 ]:     LSCOL of QUrl("https://nextcloud.local/remote.php/dav/files/Testuser/Sync folder to rename/") FINISHED WITH STATUS "ContentNotFoundError Server replied \"404 Not Found\" to \"PROPFIND https://nextcloud.local/remote.php/dav/files/Testuser/Sync folder to rename/\""

@Mika-6-9
Copy link

There are two of us testing version 3.16.4, and the other person just reported the problem to me.
I'm not having any problems, but I'm an admin, so that might be why.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants