[FEATURE REQUEST] Log file in debug mode, accesible out of ScSt
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
Some way to store the logs file outside of the Scoped Storage, so it's accesible without using Android Studio. Only available in
DEBUGvariant. Current location:
Is this feasible?? (needs research)
Regular device, not connected to Android Studio, but a special debug APK we can provide when requested?
Regular device, not connected to Android Studio, but a special debug APK we can provide when requested?
oB provides debug builds. In case this feature is feasible, it will be available for every debug build. But, needs research first.
Follow up: https://github.com/owncloud/android/issues/4155
Proposal: make logs folder visible in doc. provider through a branding variable. Will work on it
if oCIS: logs folder in space level if oC10: in root
