TeamAmaze / TeamAmaze/AmazeFileManager
Behavior of compressing folders is wrong
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
A clear and concise description of what the bug is.
When compressing an empty folder using the app and viewing the zip file, the folder is recognized as an apk file.
When compressing a non-empty folder using the app and viewing the zip file, there will be two items in the zip file, one is the normal folder, and an additional apk file with the same name as the folder.
To Reproduce
Steps to reproduce the behavior:
- long-click a random folder
- select compress in the options menu and randomly name the zip file
- click the zip file to view it
Expected behavior
The folder should still be the folder in the zip file, with no extra apk file.
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):
- Device: Google pixel 2
- OS: Android 7.0
- Rooted: No
- Version: v 3.6.0
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 issue on Android 7.0 with AmazeFileManager v3.6.0 by compressing both empty and non-empty folders, then inspect the app's folder-compression flow. Done means the resulting ZIP shows the folder once as a folder, without an additional APK item; the issue names no source file or test.
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