TeamAmaze / TeamAmaze/AmazeFileManager
Trash displays folder sizes incorrectly
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
The confirmation dialog shows size as 0 B, inconsistent with the 3.45 kB listed in the Trash Bin.
To Reproduce
Steps to reproduce the behavior:
- Go to 'Hamburger' menu
- Click on 'Trash Bin'
- Select an item in 'Trash Bin'
- Attempt to restore the item
- Observe the confirmation dialog details
Expected behavior
File sizes in confirmation should match the actual sizes listed previously.
Screen Recording
https://github.com/user-attachments/assets/f2e69f44-994d-4c84-92e8-ce54a6a7ec43
Smartphone (please complete the following information):
- Device: [Google Pixel 5]
- OS: [Android 14]
- Rooted: [No]
- Version: [3.10]
Additional context
The issue also occurs with incorrect file size representation in the Delete confirmation dialog.
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
Start by reproducing the issue from the Trash Bin, then compare the restore and Delete confirmation dialogs with the size shown in the Trash Bin. The work is done when both dialogs display the correct file size instead of 0 B, including for the Android 14 and version 3.10 scenario described.
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
- 42/100