TeamAmaze / TeamAmaze/AmazeFileManager
Unexpected behaviours after a screen orientation change (reported by activity)
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
I developed an automatic test case generation tool and it detected these problems in your app.
I would like to know if you consider them as failures and, if not, why. Thanks for your collaboration.
- MainActivity, when I change the orientation of the device screen, loses its state and different widgets disappear. Below there are two examples: the images are the screenshots taken before and after a double orientation change.
--- first case ---
The options inside the dialog are different after the orientation change.
--- second case ---
The "search" dialog disappears.
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 in MainActivity and reproduce the reported orientation changes using the screenshots and the two cases described: changed dialog options and a disappearing search dialog. Trace how the activity and its dialogs handle orientation changes; done means the dialog state, options, and search dialog remain consistent after rotating the screen.
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
- 35/100