Folders with trailing space seems to be invisible for the desktop client

[dartcafe]

Expected behaviour

All subfolders of a groupfolder should be syncronisable

Actual behaviour

• I have a subfolder with a trailing space in a groupfolder
• The list with folders from the server does not contain these folders (they are somehow missing in the settings)
• Renaming the folder via the web frontend (removed the trailing space) solved the problem; subfolder is visible and synchronisation can be activated.
• No errors before and after renaming

Client version:
3.0.3

Operating system:
Windows

OS language:
German

Installation path of client:
Programs folder

Server configuration

Nextcloud version:
19.0.3

Group folders version:
7.1.1

Storage backend (external storage):
local filesystem

Logs

I assume not necessary

[deajan]

I second this error report.
I have made a couple of tests for this error, and found out the following:

When having subfolder names like "SOME FOLDER " (notice the trailing slash) in a group folder, they appear correct in the Nextcloud web interface (trying to rename them shows the ending slash), but will not appear in the syncable folder list of a windows client.

Only the windows client seems affected.
The MacOS client syncs files with trailing space characters without any problems.

I've checked Nextcloud clients 3.0.0 > 3.0.3 (and Owncloud client 2.6.5), they all seem affected on Windows.

[EDIT]
I've also checked with nextloud client 3.1.0-rc1.
[/EDIT]

Having a subfolder with a trailing space which is not in a groupfolder doesn't seem to be problematic.

Please find below an example of subfolders in a groupfolder, where the folder '04' and '06' are missing in the client due to them finishing with a trailing space:

Environment:
Server: CentOS 8.2 x64, PHP 7.4.11
Nextcloud verison: 19.0.4, and 19.0.5
Group folders version: 7.1.0 and 7.1.1
Client: OS Win 10 x64 2004, Clients 3.0.0, 3.0.1, 3.0.2 and 3.0.3
Locale: French

I've checked nextcloud.log, httpd logs as well as client logs, none seem to show any relevant error messages.

[EDIT 2]
Of course, I ran occ files:scan --all, groupfolders:scan <folderID> and occ maintenance:repair --include-expensive while trying to find the root cause.
[/EDIT 2]

[deajan]

Could one of the team members tell us if this issue should be reported for the client or for group folders module ?

[er-vin]

I suspect this is client side. Also IIRC Windows doesn't like file names (or folder names) ending with a space, so even if that'd appear you'd have other issues down the line I think.

[k9t9]

Reported a similar problem ( trailing DOT - e.g. ". " a bout a year ago - but was reported on server repo

nextcloud/server#18066

At the moment I installed the latest release yesturday - and now have also problem with HASH symbol - e.g. #
A folder name like #SYNCH# created on the server will be synched like SYNCH ( hash characters stripped ) and if created or existing on local - will be ignored . ( win 10 - client 3.1.1-x64 )

Another related / linked open issues can be found at #464 and #707 and some others,
Maybe some team member can unite them or cross reference because it seems they are all originated from the same bug ?

[er-vin]

Duplicate of #707