[FEATURE REQUEST] Log file in debug mode, accesible out of ScSt
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 4.2k
- Forks
- 3.1k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 7
Description
Problem/Context:
When the app crashes in the beginning, it's not posible to open Settings to reach logs and check what's going on.
Suggested solution:
Some way to store the logs file outside of the Scoped Storage, so it's accesible without using Android Studio. Only available in DEBUG variant. Current location:
Is this feasible?? (needs research)
As idea, a new brandable option to create file in a different location (f.ex. Downloads).
TASKS
- Research (if needed)
- Create branch feature/feature_name
- Development tasks
- Implement whatever
- ...
- Code review and apply changes requested
- Design test plan
- QA
- Merge branch feature/feature_name into master
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 investigating the current log location shown in the issue and Android Scoped Storage behavior for the DEBUG variant. Determine a supported external location such as Downloads that remains accessible when the app crashes before Settings can open, then define and test the behavior without Android Studio.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100