Skip to content

Uploading to a folder with unicode symbols (that use a ZWJ) creates a new folder without the ZWJ #14672

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

Open
4 tasks done
KopfKrieg opened this issue Mar 14, 2025 · 3 comments · May be fixed by #14680
Open
4 tasks done

Comments

@KopfKrieg
Copy link

⚠️ Before posting ⚠️

  • This is a bug, not a question or an enhancement.
  • I've searched for similar issues and didn't find a duplicate.
  • I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
  • I agree to follow Nextcloud's Code of Conduct.

Steps to reproduce

  1. Create a folder on the server that uses a unicode symbol that uses a ZWJ (Zero Width Joiner), like "Testfolder 🏳️‍⚧️"
  2. Use the Android App to upload (doesn't matter if you're using the share menu from a file or using the Nextcloud Apps upload function) to upload any file into that folder
  3. The Android App will create a new folder, using the unicode symbol, but stripping the ZWJ (in my example a folder called "Testfolder 🏳️⚧️" is created)

Expected behaviour

The Android app shouldn't create a new folder, it should use the folder I selected. This also worked before, not sure what changed in the last (or last few?) versions.

Actual behaviour

See above.

Android version

15

Device brand and model

Google Pixel 6a

Stock or custom OS?

Stock

Nextcloud android app version

v3.31.0

Nextcloud server version

Nextcloud Hub 9 (30.0.6)

Using a reverse proxy?

Yes

Android logs

Server error logs

-

Additional information

@KopfKrieg KopfKrieg changed the title Folder with unicode symbols that use a ZWJ creates a new folder without the ZWJ Uploading to a folder with unicode symbols (that use a ZWJ) creates a new folder without the ZWJ Mar 14, 2025
@alperozturk96 alperozturk96 self-assigned this Mar 14, 2025
@alperozturk96 alperozturk96 linked a pull request Mar 14, 2025 that will close this issue
1 task
@alperozturk96
Copy link
Collaborator

Hello

Thank you for the report.

Could you try with this version: #14677 (comment) ?

@KopfKrieg
Copy link
Author

Tried it, and can confirm it fixes the problem :)

@alperozturk96 alperozturk96 removed a link to a pull request Mar 14, 2025
1 task
@alperozturk96 alperozturk96 linked a pull request Mar 14, 2025 that will close this issue
1 task
@alperozturk96
Copy link
Collaborator

alperozturk96 commented Mar 14, 2025

The test version only removes the control characters, which resolves the issue, but it affects Windows filename compatibility.

Is the "Enforce Windows Compatibility" setting enabled in the Basic settings on the web? If it is not, the proper solution would be to skip the AutoRename logic.

I will discuss this with the team, and we will provide a solution for both cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants