TeamAmaze / TeamAmaze/AmazeFileManager
No storages in WSA
Open
Nobody has claimed this yet.
Environment-Windows
Issue-Bug
Issue-Task (low)
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Originally posted by @richardnassour in https://github.com/TeamAmaze/AmazeFileManager/issues/2969#issuecomment-955660388
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 with the attached reproduction video and the original discussion in issue #2969; the payload names no files, tests, or entry points. Reproduce the missing-storage behavior in WSA, then identify the affected area and verify that storages appear there without regressing other Android environments.
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
- 20/100