[BUG] File shown as conflicting after being moved and modified in server
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 4.2k
- Forks
- 3.1k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 7
Description
- In app, download a txt file
- In server, modify the txt file
- In app, move the file to another location
Current: file is shown as conflicted
Expected: file was always remote-modified, no local modification. So, no conflict should happen.
Samsung A51, Android 12
Happens in:
- oCIS
- oC10
Reproducible if the file is synced while picking the destination folder, otherwise it does not happen. Moving the file uses the latest state before moving, so if it is updated by the way, recent changes won't be applied and conflict may appear
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
Reproduce the sequence on Android: download a TXT file, modify it on the server, and move it in the app while syncing during destination selection. Trace the move and sync state handling to determine why a remotely modified file is treated as locally modified; done means the moved file is not reported as conflicted in this scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100