TeamAmaze / TeamAmaze/AmazeFileManager
Overwrite button disabled in paste conflict dialog
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
In the paste conflict dialog, the Overwrite button is permanently disabled (grayed out) and cannot be selected.
This prevents the user from overwriting an existing file when pasting into a directory that already contains a file with the same name.
To Reproduce
- Create a file (for example
File1.mp3) - Copy the file
- Paste it into the same directory where the original file still exists
- The paste conflict dialog appears
Actual behavior
The dialog displays three actions:
Skip / Overwrite / Rename
However, Overwrite remains disabled and cannot be selected.
- Skip works normally
- Rename works normally
- Checking or unchecking "Do for all items" does not enable Overwrite
- The dialog cannot be dismissed except by choosing Skip or Rename
Expected behavior
Overwrite should be selectable so the user can replace the existing file.
Screenshots
Smartphone:
Device: Pixel 9 Pro (emulator)
OS: Android 16 / API 36
Rooted: No
Version: Debug build from latest release/4.0
Additional context
This appears related to the paste conflict dialog discussed in issue #4583, but the problem here is that the Overwrite action is never enabled, making it impossible to overwrite the existing file.
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 paste conflict dialog on Android 16/API 36 using the release/4.0 debug build, then trace the dialog behavior and compare it with issue #4583. Done means the Overwrite action is selectable and replaces the existing file when pasting a duplicate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100