Logging if applications keeps crashing #42
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Starfish/TinyWeatherForecastGermany#42
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
There seems to be no possibility to read or submit the logs if the applications keeps crashing and one has to wipe the users data. This effectively seems to wipe the logs as well.
It might be helpful to catch the exception fired in this case and offer to send the log report directly.
isRelatedTo: #32
I have added some catch-clauses indeed :-). However, you basically cannot "catch" the whole app and make the data available without compromising privacy.
I guess most apps at the official google app store do it by using Googles Firebase Crashlytics, but that is not an option here. I believe that this really compromises privacy if an app sends crash reports without asking you for consent. (And to ask for consent, you need to open the app sucessfully.)
Will further improve to catch the errors were possible. :-)
Ic. Then we're out of luck here of course. Lesson learend for me: no
/var/log/syslog
Agree. I like your approach.
I think this could be approached via
adb
. If the results in #91 (comment) were usefull, I'd add some instructions on how to do it to the Readme.This is addressed using
adb
as described in the README.mdisRelatedTo: #95