TeamAmaze / TeamAmaze/AmazeFileManager
Fix saving the state for Settings Activity
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Currently the activity for the settings contains android:configChanges="orientation|screenSize":
Which fixes issues with rotation, but creates issues when the activity is destroyed and recreated, like selecting "Do not keep Activities" in dev settings and going to settings, going to another app then returning to Amaze.
The line android:configChanges="orientation|screenSize" should be removed and all resulting glitches/bugs fixes.
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 Settings Activity entry in app/src/main/AndroidManifest.xml at the linked lines and reproduce the reported cases: rotation, “Do not keep Activities,” and returning from another app. Trace how the activity is recreated and identify the resulting state glitches. Done means removing android:configChanges="orientation|screenSize" while preserving settings state and avoiding the reported bugs.
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
- Mostly clear
- Newbie friendliness
- 42/100