-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE REQUEST] Log file in debug mode, accesible out of ScSt #4146
Comments
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: #4155 |
Proposal: make logs folder visible in doc. provider through a branding variable. Will work on it if oCIS: logs folder in space level |
Hello, was this ever realized, or was there no decission made until now? |
ftm no decision, not prioritized yet. |
@DeepDiver1975 do we have a decision here? |
Crash reporting is done via google play console - why is this not an option here? |
Because the app is provided via the customers Play Store. |
In any case, their IT admin could get these crash logs from their Play Console account and send them to us, that would help us a lot and make this issue (reachable logs out of scoped storage) less prior |
I think their IT Admin is another legal department... Not sure if we can get this |
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
The text was updated successfully, but these errors were encountered: