Case Clash on Windows 11 Client

Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • Nextcloud Hub 25 Autumn (32.0.6)
  • Operating system and version (e.g., Ubuntu 24.04):
    • Kubuntu 24.04
  • Web server and version (e.g, Apache 2.4.25):
    • SNAP
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • N/A
  • PHP version (e.g, 8.3):
    • SNAP
  • Is this the first time you’ve seen this error? (Yes / No):
    • No
  • When did this problem seem to first start?
    • Unsure, a couple of months
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • SNAP
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • No

Summary of the issue you are facing:

I use the Canon app to sync files from my Canon DSLR to my Android phone. I have the folder on the Android phone monitored by the NextCloud app to sync it as a photo/media folder back to my NextCloud server.

The sync works fine. There are some errors during the sync I believe caused by file locks caused by the ongoing upload from the camera to the phone.

Once completed, I go to my Windows 11 laptop and it syncs the files down. Once the Windows 11 client has completed the sync it then starts to bring up Case Conflict errors for all the new images. The cause of the conflict appears to be “.jpg” vs “.JPG” in the filename. The originals all have lower case jpg.

For these I have just been adding a “zz” to the end of the filename then deleting them all once completed as they are effectively duplicates. I don’t recall the issue prior to the mobile app release that implemented the fix for missing upload files a couple of months ago, but that may be coincidental.

As a note, files uploaded from the separate media upload folder for the android camera app do not appear to cause this issue.

I have looked through the forum and GitHub and I cannot see anything recent relating to this so I was wondering if anyone had come across anything similar.

This is not an urgent issue as I have a simple workaround and other options if needs be.

Note, I have not down the path of digging through log files as yet.

Thankyou very much.

I think I have found a workaround.

I changed the setting on the NextCloud Android app for the DSLR folder to only upload on unmetered WiFi. I have only done one test but this appeared to solve all the issues.

  1. DSLR media sync from Android to NextCloud no longer generate errors as the files are no in use (being written) at the time
  2. Sync from NextCloud to Windows 11 worked seamlessly, no errors or filename clashes.

My assumption from this is that possibly there was some kind of artifact created from the failed upload.

Time will tell if this is an actual fix, or sheer luck. Either way, I’ll call it solved for now and leave it here in case someone else has a similar issue.

No, that was not a solution or workaround. It turns out the issue is intermittent.

Tough luck. This has been reported all the way back in 2022, it has been requested to be fixed multiple times over. The issue always gets closed, but never fixed. Welcome to Nextcloud … That’s how it is here ..

and the proof of your claim is where exactly?
I mean why not linking the issue here?

well ya, you seem to be an expert to Nextcloud since this seems to be your very first posting. So thanks for the nice impression of yourself you left here. A real dooropener, I think.
Thanks for this wonderful posting. It really helps everyone on here and solves every problem.

1 Like

alright. here we go. Allow syncing file with case clash names · Issue #5099 · nextcloud/desktop · GitHub marked closed. Issue obviously persists.

well this one was marked “solved” by the original poster.

And it was worked on a lot as the issue-history shows.

So this new problem here might look alike but it’s probably something different.

no. the underlying issue is still the same. case clash on windows. solution is quite simple. on existing files skip sync or force case on the server side to propagate to clients. results in no folder duplication like the current approach.

reported back in 2016. user gave up on windows client and switched to linux …. might be closed, but surely not resolved. still the same issue.

And again in 2023. same issue. no resolution.

Can we now agree the issue exists, persists, is known and is not being resolved?

well you linked different kinds of bugs/featurerequests/enhancements. all closed (only one for being stale for more than a year).

one of the links you posted even provided a clear hint to the manual

if that doesn’t help you please open a new issue there, describe your setup and the error in detail and then see if dev’s would accept that as a bug or not.

So far you found a lot of issues but they are not neccessarily adressing the same problem. They might address a similar one. But that’s not the same.