TeamAmaze / TeamAmaze/AmazeFileManager
Bug on paste-override feature
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Describe the bug
Bug on copy/cut and paste-override feature. Keep original file size and data.
To Reproduce
Steps to reproduce the behavior:
- File to copy and paste have smaller size than original file size. They have same name.
- After overrided, file size keep in previous file size.
- Some extra (old) data would be remain, not removed.
Expected behavior
New file size need to be update. And old data would be delete.
Screenshots
Click to see
Data:
File size:
Paste process:
Keep old file size after pasted and force-refresh:
Bug found!
Smartphone:
- Device: Samsung Gaplaxy A7 2018 (A750GN)
- OS: Android 10
- Rooted: No
- Version: 3.6.1
Additional context
Ruin user data (text, image, video,...).
Advance user can fix this, but normal user can't.
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
No source file or test is named. Start by reproducing the copy/paste overwrite on Android 10 with Amaze File Manager 3.6.1, using a smaller same-name file, then trace the paste-override flow. Done means the destination size matches the replacement and no trailing data from the original remains.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100