TeamAmaze / TeamAmaze/AmazeFileManager
Decrypting a file ended up 0 bytes.
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
I encrypted a 2 MB file with amaze file manager uploaded it to the cloud(google drive) for later use. Downloaded and I can't decrypt it anymore. The file ends up creating 0 bytes file . I don't know if its the filename or extensions bcs I changed them several times. Later changed it to .aes to decrypt and it didn't decrypt. And I'm sure I gave the correct password. Also I couldn't decrypt the file using the apps that are recommended on AESCrypts website.
Expected behavior
Encrypt and decrypt successfully.
Smartphone (please complete the following information):
- OS: Android 9
- Rooted: No
- Version: 3.7.0(108) play store.
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 workflow in Amaze File Manager 3.7.0 (108) on Android 9: encrypt a 2 MB file, upload and download it through Google Drive, then attempt AES decryption with the original password. Compare the downloaded encrypted file and decrypted output with the local originals; done means decryption succeeds and produces the expected non-empty file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100