-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhance error message when failing to sync file due to illegal filename #2711
Comments
Correct, we can enhance the error message, but the underlying error we cannot change… |
:
in name can not be synced
This request did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you! |
Hi, I bumped into this issue and I think it should be reopened. The logcat is:
|
To do
|
is probably better. Just for future reference. Anyway, I totally agree. QOL improvements like that are what make people choose certain software. I know that without that, my family wouldn't understand the problem nor how to remediate it. I'm merely lucky that thus far they've only used ASCII characters for filenames. |
I accidentally had a directory in my nextcloud which contained a colon in its filename, e.g.
tro:lol
. Btw, this is totally legal in unix and I think in OSX, aswell.When trying to sync the folder (to the fat32 sdcard) with the android client, i get an error message.
Actual behaviour
In case a directory contains a colon, the dir including it's content does not sync.
In case a file contains the colon, the file is not synced.
Expected behaviour
:
is a reserved char. The error message should be more specific, e.g.:Steps to reproduce
mkdir tro:lol; cd tro:lol; touch 1 2 3
tro:lol
entry and selectSync
.Environment data
Android version: 7.1.2
Device model: Samsung S5 (klte)
Stock or customized system: LineageOs (microg)
Nextcloud app version: 3.1.0
Nextcloud server version: 13.0.2-1
The text was updated successfully, but these errors were encountered: