TeamAmaze / TeamAmaze/AmazeFileManager

Can't Delete Files with Same Name to Trash Bin

Open
#4,619 2 comments 0 reactions 1 assignee View on GitHub

@VishnuSanal is already working on this.

Since May 10, 2026.

Area-Trash Issue-Bug Issue-Severe (high)
Dominant language
Kotlin
Stars
6.4k
Forks
1.7k
Avg merge
3d 9h
Merged PRs (30d)
1

Description

Describe the bug

Can't delete files to trash bin if there are existing ones with same name and different content due to trashes are all moved to /storage/emulated/0/.AmazeData/TrashBinFiles.

To Reproduce

Steps to reproduce the behavior:

  1. Create a folder named a (or any other string) in /storage/emulated/0/Download (or any other location).
  2. Create a file a.txt (or any other file) in it.
  3. Delete it to trash bin.
  4. Do step 1 again.
  5. Create a file b.txt (or any other file except a.txt) in it.
  6. Delete it to trash bin. The new a folder now can not be deleted.

Expected behavior

The new a folder should also be deleted to trash bin.

A possible solution is to move trashes to /storage/emulated/0/.AmazeData/TrashBinFiles/<timestamp> where <timestamp> is the UNIX time of the time it's deleted.

Smartphone (please complete the following information):

  • Device: Samsung S24+
  • OS: Android 16
  • Rooted: No
  • Version: 3.11.2

Additional context

I also suggest a minor feature to sync /storage/emulated/0/.AmazeData/metadata.json with the actual files in /storage/emulated/0/.AmazeData/TrashBinFiles when opening trash bin so that when a trash is deleted directly from TrashBinFiles, it'll not be shown in trash bin.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.