U+2024 instead of Dot in File Provider Domain Display Name

[manmatteo]

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

• This is a bug, not a question or a configuration issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• I agree to follow Nextcloud's Code of Conduct

Bug description

After the update to v33 on macOS, the name of the folder where virtual files are present has been changed, and it now uses unicode U+2024 ONE DOT LEADER instead of ordinary dots.

Steps to reproduce

1 - Configure a remote host with an URL comprising dots
2-

cd ~/Library/CloudStorage/
ls

Expected behavior

The folder name should not have been changed, and it should use FULL STOP (U+002E)

Which files are affected by this bug

...

Operating system

macOS

Which version of the operating system you are running.

macOS 26

Package

Official macOS Virtual files 12+ universal pkg

Nextcloud Server version

26 Winter

Nextcloud Desktop Client version

33

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

Updated to a major version (ex. 3.16.3 to 3.17.0)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

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

Nextcloud Server logs

Additional info

No response

[i2h3]

@manmatteo How did you even notice this? 😄 Can you please explain why this is a problem and how it affects your workflow? What actual problem does it cause? This was an intentional change and workaround to fix the file provider extension in certain use cases. The intention was to achieve the same appearance with a technically different implementation.

• Pull request: Escape dots in file provider domain display names (affects #7979) #9369
• Original problem: [Bug]: Support Account Domains Matching Common Bundle Extensions #7979

In summary: without this workaround, the file provider extension completely breaks for people logging in on Nextcloud servers hosted on certain top-level domains like ".app". This is not under our control. Using the domain as part of the display name will result in a folder being created in the file system with that suffix. With ".app" as an example, macOS then considers the folder to be an application bundle instead of just a folder which breaks the whole interaction on macOS level.

[manmatteo]

I see! In my case, I had some configuration files where the path was included, and they stopped working after the update. I investigated and found out that the directory name had changed after the update.
I guess the biggest downside to the current solution is that you can not type out the actual path with a usual keyboard layout. Other than that, my use case is easily fixed by copy-pasting the path.