TeamAmaze / TeamAmaze/AmazeFileManager
Update `MediaStore` after APK backup
Open
Nobody has claimed this yet.
Area-AppManager
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
To Reproduce
Steps to reproduce the behavior:
- Go to "App Manager"
- Backup any app
- Check if apk file is there (Amaze's default folder
/storage/emulated/0/app_backup) - Now open Amaze Sidebar> APKs quick access
- It ignores
app_backupfolder apks
Expected behavior
Amaze's APKs quick access should recognize it's own apk files...
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 tracing the App Manager APK backup flow and the Amaze Sidebar APKs quick-access implementation. Reproduce the issue using the default /storage/emulated/0/app_backup folder, then verify that APKs created there are recognized by the APKs quick access.
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
- 45/100