Open nekohayo opened 3 weeks ago
Apparently, uploading folders with such characters in their filenames also fails with similar errors even if the containing folder has no special characters, but I'm not sure what to do about files. It would still be desirable to have something more descriptive than "Connection reset by peer", if possible...
If you are trying to put files on your SD card and your file/folder name contains special characters like :
, that will fail due to stricter FAT32 file name enforcement on new Android versions. See also https://github.com/google/adb-sync/issues/34 .
Maybe Material Files can provide a better error message, but Material Files shouldn't translate the file name for you because there's no canonical way to do that. You need to transform the file name properly with your own copy mechanism.
Hi !
With the latest version available in f-droid (1.7.4) on Android 14, I've been trying to upload a bunch of music album folders but they end up causing a bunch of incomprehensible errors in Nautilus and FileZilla when they try to copy the actual files in those folders, when the folder names have characters such as
:
or>
in them.The weird thing is that in the Material Files interface, and through FTP, it is quite possible to create, rename, view such folders even with special characters. It only fails to upload files to them.
For example, if I create a folder called
blah :
in the Music folder, and try to upload to it, for each file FileZilla reports:Nautilus / GVFS reports:
If you try to create a file in such a folder (instead of just copying), Nautilus' error is slightly different:
Given that two different types of FTP clients are choking on this in different ways, I am wondering if there is something Material Files can do to translate the paths+filenames when receiving (or creating, modifying etc.) files through FTP specifically? Otherwise, is there a way for Material Files to raise a more descriptive error for the FTP clients? Or prevent the creation of those faulty folders (instead of later failing on the files within)?