You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Android Studio only shows the logcat of the current process by default.
Since the library restarts the process to show the error Activity, and the stacktrace of the crash is logged in the old process, Android Studio doesn't show the stacktrace after a crash. You need to change the filters, or remove them, showing a lot of unwanted verbose information.
So, here's my idea for that problem:
The library could log the info in getStackTraceFromIntent() or getAllErrorDetailsFromIntent() from the error Activity. This way the developer will see it in Android Studio without changing the filter. The info will be duplicated in the full logcat, but I think its an acceptable trade-off.
That's what I've done in our custom error Activity at InfoJobs, but I think it could be a helpful addition to the library itself.
What do you think?
Thanks again for the library @Ereza, you know we're happy users of it :)
The text was updated successfully, but these errors were encountered:
Hi @Sloy, thanks again for the positive feedback! Yes, that's an issue I have faced myself, and I think it would indeed be a nice addition. I'll add it :)
Hi!
Android Studio only shows the logcat of the current process by default.
Since the library restarts the process to show the error Activity, and the stacktrace of the crash is logged in the old process, Android Studio doesn't show the stacktrace after a crash. You need to change the filters, or remove them, showing a lot of unwanted verbose information.
So, here's my idea for that problem:
The library could log the info in
getStackTraceFromIntent
() orgetAllErrorDetailsFromIntent()
from the error Activity. This way the developer will see it in Android Studio without changing the filter. The info will be duplicated in the full logcat, but I think its an acceptable trade-off.That's what I've done in our custom error Activity at InfoJobs, but I think it could be a helpful addition to the library itself.
What do you think?
Thanks again for the library @Ereza, you know we're happy users of it :)
The text was updated successfully, but these errors were encountered: