Disabling Enforce Windows Compatibility removes only Windows-specific restrictions on forbidden file names and characters. However, the server does not expose a boolean flag for this setting, requiring iOS and Android to rely on the presence of forbidden_filename_characters and forbidden_filename_extensions.
Since these values are never empty, clients continues enforcing filename restrictions, causing AutoRename to always be applied even when Enforce Windows Compatibility is disabled. This will lead to unexpected filename related issues.
e.g.
nextcloud/android#14672
@susnux @tobiasKaminsky @mpivchev @mgallien
Disabling Enforce Windows Compatibility removes only Windows-specific restrictions on forbidden file names and characters. However, the server does not expose a boolean flag for this setting, requiring iOS and Android to rely on the presence of
forbidden_filename_charactersandforbidden_filename_extensions.Since these values are never empty, clients continues enforcing filename restrictions, causing AutoRename to always be applied even when Enforce Windows Compatibility is disabled. This will lead to unexpected filename related issues.
e.g.
nextcloud/android#14672
@susnux @tobiasKaminsky @mpivchev @mgallien