nextcloud / nextcloud/android

Search result from fulltextsearch does not open if file name contains umlauts

Open
#13,461 0 comments 1 reaction 0 assignees View on GitHub
bug feature: search hotspot: filename handling
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. Have fulltextsearch app installed in Nextcloud and configured to use elasticsearch.
2. Create file "ä.txt" with content of "foobaz" to Nextcloud.
3. Wait until fulltextsearch app has indexed the file.
4. In Nextcloud Android client search for "foobaz" --> you should see "ä.txt" in search results: ![fulltextsearch-results](https://github.com/user-attachments/assets/ab9f12fd-35dd-4c2c-8eaf-396aac9509d4)
5. Tap the found "ä.txt" file to open it.

### Expected behaviour

The file opens.

### Actual behaviour

Rotating load indicator is shown that never completes, endlessly loading the file:
![attempt-to-open-file](https://github.com/user-attachments/assets/2006b080-03a2-4b07-bc7b-365382322411)

### Android version

14

### Device brand and model

Google Pixel 7 Pro

### Stock or custom OS?

Stock

### Nextcloud android app version

3.29.2

### Nextcloud server version

29.0.4

### Using a reverse proxy?

Yes

### Android logs

[logcatOutput.txt](https://github.com/user-attachments/files/16737051/logcatOutput.txt)

### Server error logs

_No response_

### Additional information

If the file name does not have umlauts in name, like for example "a.txt" then opening the search result works fine. Also, if you search for file name instead, that is "ä.txt" and attempt to open search result that does not come from fulltextsearch then the file opens fine as well.

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.