Permission Dispatcher VS timber

I liked https://github.com/bluelinelabs/LoganSquare for example, but annotation processors are hard to maintain. Look at libraries like Mortar-Architect https://github.com/lukaspili/Mortar-architect or Blade https://github.com/FrantisekGazo/Blade or even better Permissions-Dispatcher https://github.com/permissions-dispatcher/PermissionsDispatcher/issues/775 which actually breaks builds after certain Kotlin versions.

Permissions are generally a pain, but I've used PermissionsDispatcher, EasyPermissions, and RxPermissions at various times

To try and fix this problem fast I knew I needed some sort of logging and that is when I discovered Timber and Firebase Crashlynics. I then used THIS video to set both of them up and to create a decent crash reporting system.

Timber

Do you still use the Android Timber lib? The only real pro I see is that you don't need to declare the Tag, other than that that "pro" where each call checks if debug or not I wonder why you would like to have that, I mean what I want is all debug-only logs to get stripped out from the code, and instead of calling if(BuildConfig.Debug) on each Timer.xy() call why not create an extra Application class under the debug folder where logs are activated? Just trying to figure out of this lib that actually started like 9 years ago is still needed or not really anymore. https://github.com/JakeWharton/timber

One of the options could be to setup logging to the file within the app and sync it with backend once necessary or required. This could be achieved by using library, such as Timber and setting up local file. Depending on your constraints, such as file size, you might want to include a file rotation strategy, e.g. start a new file and remove the old one.

Timber for logging

Same as in Timber