I've a question.
Given an App that handles a Try Catch, what is the best method to send the Exception in order to see the details?
Crashlytics is only good when the app actually crashes, but if the error is managed and I only want to see what the error was? How can I do...
I have been experimenting with ways to fully clear the B4A log pane between runs of a program (using B4A-Bridge), as it becomes confusing sometimes trying to distinguish where a new Run starts.
Things I have tried, without success:
Simply pressing the "Clear" button at the bottom of the Logs...
So this is a wrapper for the LOGBack - The Generic, Reliable, Fast & Flexible Logging Framework
logback-core and logback-classic can be downloaded...