lumpiluk
commented
10 months ago This is especially interesting as I don't experience this behavior with the same files on my old Android 10 device, but I do on Android 13 (same device as yours actually).
Syncing an entire folder is not even necessary to trigger this error message. I usually encounter the problem when I try to download or export a single file.
File names for which the problem occurs are of the form: 2023-11-10_event_myname_0001.JPG. I suspect that the problem is not the file name but the name of the parent folders, which include '*', '@', and spaces.
⚠️ Before posting ⚠️
Steps to reproduce
Expected behaviour
In case a file with an "invalid" filename is encountered, the error notification should indicate which file was affected, so the user has a way to identify and adjust the offending file(name).
(The most convenient solution would probably be to transparently "adjust" the filename and continue successfully, but that's a different issue is not directly related to this issue here.)
Actual behaviour
An error notification is generated which only says "Invalid filename for local file" but does not provide any information regarding which file was actually affected, and why the filename was "invalid".
See screenshot.
I ended up with a dozend or so of these notifications - how am I supposed to fix this?
Android version
13
Device brand and model
FairPhone 5
Stock or custom OS?
Stock
Nextcloud android app version
3.25
Nextcloud server version
27.1.3
Using a reverse proxy?
Yes
Android logs
No response
Server error logs
Additional information
I don't have Android development tools installed and no dev mode active, so cannot easily access the client's logs.
Why don't you make these accessible in the GUI directly?