nextcloud / nextcloud/android

No Way to Identify Unsyncable Files With Invalid Filenames

Open
#12,137 4 comments 2 reactions 0 assignees View on GitHub
bug hotspot: device storage hotspot: filename handling stable-3.25
Dominant language
Kotlin
Stars
5.6k
Forks
2k
Avg merge
2d 18h
Merged PRs (30d)
92

Description

### ⚠️ Before posting ⚠️

- [X] This is a **bug**, not a question or an enhancement.
- [X] I've [searched for similar issues](https://github.com/nextcloud/android/issues) and didn't find a duplicate.
- [X] I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
- [X] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/).

### Steps to reproduce

1. Synchronize a remote folder which contains files with "invalid" filename (whatever this may mean - due to this bug I currently cannot find out. ;) As all files were uploaded from Linux and are now downloaded to an Android device's internal flash storage, I'd have expected all filenames to be compatible.)

### 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](https://github.com/nextcloud/android/issues/11241) 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.

![image](https://github.com/nextcloud/android/assets/26199042/85a557ee-f046-4673-b85b-d6190458280a)

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

```bash
No server issue.
```

### 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?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.