TeamAmaze / TeamAmaze/AmazeFileManager
If directory is changed while out of the app, app doesn't reflect
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Open a directory, exit app, change directory (it may be an automated action by another app in the background), open app, directory is as before, reload dir, now changes can be seen.
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 listed steps in the Android app: open a directory, exit, change it externally, and reopen the app. Trace the directory refresh and app-resume entry points; done means external changes appear when the app is reopened without manually reloading the directory.
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