[Bug]: Non-existent file with leading spaces still trying to sync

[davidc]

⚠️ 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've searched it).
• [X] Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• [X] I agree to follow Nextcloud's Code of Conduct

Bug description

After upgrading to the latest version (3.6.0) from a version that was probably a year old, I was informed of a file with leading spaces. Instead of renaming it, since I did not want it, I removed it from the filesystem. I also removed it from the Nextcloud web UI.

However every time it syncs, I am still told that the file contains a leading space. If I try to deal with this 'conflict' by renaming it in the desktop client, it fails: "Could not rename local file. Source file does not exist.". Even if I exclude the parent directory, I get this conflict on every sync, there does not seem to be a way to get past this, not even a restart!

This appears to be related to the fix for #4164

Steps to reproduce

1. Have a file with a leading space
2. Don't rename it when you see the conflict, just delete it

Expected behavior

It should not keep trying to sync files that no longer exist on either the client or server.

Which files are affected by this bug

 {{ thumb }}.jpg

Operating system

Windows

Which version of the operating system you are running.

Windows 10

Package

Other

Nextcloud Server version

24.0.5

Nextcloud Desktop Client version

3.6.0

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

Updated to a major version (ex. 3.3.6 to 3.4.0)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

• [X] Default internal user-backend
• [ ] LDAP/ Active Directory
• [ ] SSO - SAML
• [ ] Other

Nextcloud Server logs

Nothing relating to this file appears in the server log as it does not exist and is not actually trying to sync.

Additional info

No response

[davidc]

[TomW80]

I have the same problem.

[alvarq]

Same issue here with an url-file:

The file has been deleted online and offline. But it keeps to appear as an error with the client.

Is there a way to remove this error message?

Nextcloud Desktop Client Version 3.6.6 (Windows).

[being-peace]

Same here. If I create a file with the wrong name, I can rename it successfully, but the conflict still continues reappear. The file was there for a longer time. The problem surfaced after upgrading the windows nextcloud app to 3.7.

What worked for me, was to put the full filename on the ignorelist (Desktop App -> Settings -> Folder -> Ignore List).

[falcongoat]

The bug description of @davidc exactly describes the behavior on my system.

Windows 10 22H2 Nextcloud Client 3.8.1

[gschenck]

I have the same problem.

Windows 10 22H2 Nextcloud Client 3.8.1

[x86dev]

Same here, with a file name containing ":" on a Windows host. Nextcloud Desktop 3.13.0.