TeamAmaze / TeamAmaze/AmazeFileManager
Preserve permissions on copying when possible
Open
Nobody has claimed this yet.
Issue-Bug
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
I attempted to copy an apk file from /data/app to another dir on /data partition. The file got copied but the permission was set to 600 and I wasn't able to read/install file anymore(not until I set the proper 644 permission maually)
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 copying an APK from /data/app to another directory on the /data partition, then trace the file-copy entry point that handles its permissions. Done means permissions are preserved when possible so the copied APK remains readable and installable without manually changing them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100