Creating or renaming duplicate file/folder throws inappropriate message [M]
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 13
Description
Step to reproduce
- Launch the NextCloud app
- Create two folder with the name " Folder A" and "Folder B"
- Now rename Folder B to Folder A-"that is already exists"
- Create two new text document file and rename the file which is already exist
- Also create the duplicate folder or file name- which is already exists
Actual result
For renaming the already existing file/folder name- it throws a message "412: The server does not meet one of the precondition that the requester"
For Creating the already existing file/folder name- it throws "File conflict" dialog for file. For folder it will create by adding number increasing order
ex. if there is folder "test" and create the folder again with the same name so it will be created named as "test 1"
Expected result
It should throw a message like- "file already exists" in English in both the case
attached ss
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the duplicate-file and duplicate-folder rename and creation flows in the Nextcloud iOS app, then trace the handling of the 412 response, file-conflict dialog, and automatic folder naming. Done means duplicate files and folders consistently show an English “file already exists” message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100