TeamAmaze / TeamAmaze/AmazeFileManager

Image thumbnails show deleted image when renamed

Open
#4,269 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Area-UIUX Issue-Easy (good first issue) Issue-Glitch
Dominant language
Kotlin
Stars
6.4k
Forks
1.7k
Avg merge
3d 9h
Merged PRs (30d)
1

Description

Describe the bug
Image thumbnails show as deleted image rather than current image if current image is given the same filename

To Reproduce
Steps to reproduce the behavior:

  1. Place two different image files (Image 1 and Image 2) in same folder (tested with PNG and JPG)
  2. Delete Image 1 (either to trash bin or permanently, same behavior either way)
  3. Rename Image 2 to Image 1
  4. Thumbnail reverts to original Image 1 thumbnail rather than remaining consistent with file content
  5. (Optional/Intermittent) Open newly renamed Image 1 using "Amaze Image Viewer (Dialog)"
  6. Image may appear as deleted Image 1 rather than renamed Image 1.

Expected behavior
Image 2 thumbnail will remain the same when renamed to Image 1 and accurately show file contents. Opening the file in the Amaze Image Viewer will always display expected image as well.

Smartphone (please complete the following information):

  • Device: Samsung Galaxy Z Fold 4
  • OS: Android 15
  • Rooted: No
  • Version: 3.10

Additional context
Other image viewers or apps that use the image will show the correct image, so the file operations are happening as expected. Amaze just displays the old deleted file.

I have tried clearing app cache, force stopping the app, running Samsung's Device Care optimization (clears caches and force closes background apps), and rebooting phone. Images still display incorrectly.

Deleting app data will make images display as expected, but that's not an ideal solution

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.

Research direction

No source file, test, or entry point is named in the report. First reproduce the rename sequence on Android, then trace thumbnail and image-viewer handling for deleted and renamed files; done means the renamed file consistently shows its current contents without clearing app data.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.