A logger with a small, extensible API which provides utility on top of Android's normal Log class.

When running the lint task with AGP 7.0.0-alpha13 it will fail with the following error:

The lint detector
timber.lint.WrongTimberUsageDetector
called context.getMainProject() during module analysis.

This does not work correctly when running in cli.

In particular, there may be false positives or false negatives because
the lint check may be using the minSdkVersion or manifest information
from the library instead of any consuming app module.

Contact the vendor of the lint issue to get it fixed/updated (if
known, listed below), and in the meantime you can try to work around
this by disabling the following issues:

"LogNotTimber","StringFormatInTimber","ThrowableNotAtBeginning","BinaryOperationInTimber","TimberArgCount","TimberArgTypes","TimberTagLength","TimberExceptionLogging"

Issue Vendors:
Identifier: timber-4.7.1

Call stack: Context.getMainProject(Context.kt:117)
←WrongTimberUsageDetector.visitMethod(WrongTimberUsageDetector.java:80)
←Detector.visitMethodCall(Detector.kt:551)
←UElementVisitor$DelegatingPsiVisitor.visitMethodCallExpression(UElementVisitor.kt:1095)
←UElementVisitor$DelegatingPsiVisitor.visitCallExpression(UElementVisitor.kt:1075)
←KotlinUFunctionCallExpression.accept(KotlinUFunctionCallExpression.kt:186)
←UQualifiedReferenceExpression$DefaultImpls.accept(UQualifiedReferenceExpression.kt:34)
←KotlinUQualifiedReferenceExpression.accept(KotlinUQualifiedReferenceExpression.kt:29)
←UQualifiedReferenceExpression$DefaultImpls.accept(UQualifiedReferenceExpression.kt:33)
←KotlinUQualifiedReferenceExpression.accept(KotlinUQualifiedReferenceExpression.kt:29)
←ImplementationUtilsKt.acceptList(implementationUtils.kt:23)
←UBlockExpression$DefaultImpls.accept(UBlockExpression.kt:21)
←KotlinUBlockExpression.accept(KotlinUBlockExpression.kt:24)
←ULambdaExpression$DefaultImpls.accept(ULambdaExpression.kt:33)
←KotlinULambdaExpression.accept(KotlinULambdaExpression.kt:29)
←ImplementationUtilsKt.acceptList(implementationUtils.kt:23)
←KotlinUFunctionCallExpression.accept(KotlinUFunctionCallExpression.kt:190)
←UQualifiedReferenceExpression$DefaultImpls.accept(UQualifiedReferenceExpression.kt:33)
←KotlinUQualifiedReferenceExpression.accept(KotlinUQualifiedReferenceExpression.kt:29)
←ImplementationUtilsKt.acceptList(implementationUtils.kt:23)

Everything works fine when using AGP 7.0.0-alpha12. Disabling the issues obviously works as a temporary workaround.

Hi Jake!

Few days ago I opened issue #62 asking about the possibility of removing android.Log from Timber class so it can be a pure Java logger. You closed it as a dupe of #29, which asks for making Timber dependent of slf4j-api. I'm not sure these two are asking for the same.

In order to make my issue more clear I have created this PR as an "illustrative" solution. I know it may not be the best, mainly because it breaks the chain of compatibility for older versions because in favor of a new namespace for DebugTree (timber.log.android.DebugTree). But, at least, I hope that you can get a better picture of the goal that I want to achieve.

Look forward to your feedback.

Thanks!

What About Supporting .wtf (Documentation: http://developer.android.com/reference/android/util/Log.html#wtf(java.lang.String, java.lang.Throwable) ) Log Levels.

Pull DebugTree.CALL_STACK_INDEX into a protected getLoggingDepth() method. This is useful for apps that wrap Timber and don't want every tag to be "TimberWrapper" or whatever. Does not affect default behavior for users who don't want/need this.

After updating to 4.6.0 Lint fails with:

:app:lintPlayReleaseUnexpected failure during lint analysis of null (this is a bug in lint or one of the libraries it depends on)

`NoClassDefFoundError:PermissionRequirement.getAnnotationStringValue(PermissionRequirement.java:244)←PermissionRequirement.create(PermissionRequirement.java:111)←SupportAnnotationDetector.checkAnnotations(SupportAnnotationDetector.java:502)←SupportAnnotationDetector.access$100(SupportAnnotationDetector.java:178)←SupportAnnotationDetector$CallVisitor.checkCall(SupportAnnotationDetector.java:2772)←SupportAnnotationDetector$CallVisitor.visitCallExpression(SupportAnnotationDetector.java:2671)←UElementVisitor$DispatchPsiVisitor.visitCallExpression(UElementVisitor.java:520)←UElementVisitor$DelegatingPsiVisitor.visitCallExpression(UElementVisitor.java:1041)`

You can set environment variable `LINT_PRINT_STACKTRACE=true` to dump a full stacktrace to stdout.
java.lang.NoClassDefFoundError: lombok/ast/Node

I am using: Gradle: 4.2.1 'com.android.tools.build:gradle:3.0.0' buildToolsVersion "27.0.0"

Hi,

I cannot use Timber on API 14. Is there a specific reason that minSdkVersion=15 is required?

https://github.com/JakeWharton/timber/blob/master/build.gradle#L17

Thank you,

Jan

• Android Studio version: Android Studio Bumblebee | 2021.1.1 Patch 1 (Build #AI-211.7628.21.2111.8139111)
• Timber version: com.jakewharton.timber:timber:5.0.1

Reproduction steps:

1. Simply add the above dependency to an Android project (ensuring to use Android Studio Bumblebee+)
2. Observe the Cannot resolve method 'plant(timber.log.Timber.DebugTree)' Lint error message:

Additional notes:

• Didn't seem to occur on prior version of Android Studio (Arctic Fox and prior).
• Does seem to affect Android Studio Bumblebee (Stable), Chipmunk (Beta) and Dolphin (Canary).
• Doesn't appear to occur with pre-5.0.0 versions of Timber.
• Loosely related to this issue.
• Could be an Android Studio bug rather than a bug with Timber, though I figured best to report it here as it doesn't seem to affect pre-5.0.0 versions of Timber as mentioned previously.
• In case the issue is in fact with Android Studio, @gmk57 has reported it on Android Studio bug tracker.

Is it possible that latest AGP is triggering #284 again? On com.android.tools.build:gradle:3.3.0-alpha04:

timber-4.7.1.aar/.../lint.jar: Lint found an issue registry (timber.lint.TimberIssueRegistry) which is older than the current API level; these checks may not work correctly.

Let's image that we don't want to use Timber directly in our applications, but we have a custom interface for logging that use a Timber delegate as its implementation. Let's call that interface "Logger". So in the debug log we want to print the line when Logger.d() was called, not Timber.d() (we already know this line, it's always inside our "Logger"). The aim of this change is to make possible to customize which line from the calling stack trace should be printed by the DebugTree.

When I extend Timber.Tree and override the log method I get passed a null tag:

@Override
protected void log(int priority, String tag, String message, Throwable t) {
   if (priority == Log.VERBOSE || priority == Log.DEBUG || priority == Log.INFO) {
      return;
   }
   // tag is null
   Log.println(priority, tag, message);
}

Quoting my comment https://github.com/JakeWharton/timber/issues/196#issuecomment-464646466

Log doesn't care at all how long the tags are.

The only thing where is an issue is that Log.isLoggable checks a system property. And system property keys were until API 24 limited in length to 31 characters. And "log.tag.".size + 23 equals 31.

Source:

• https://android.googlesource.com/platform/frameworks/base/+/kitkat-release/core/jni/android_util_Log.cpp
• https://android.googlesource.com/platform/frameworks/base/+/oreo-release/core/jni/android_util_Log.cpp

Going forward LogcatTree could

• drop this limitation entirely or
• enforce it for one or both of checking and printing just when withCompliantLogging() is used.

In a custom tree it may make sense to adjust tags with tree specific data. In timber v4 this was easily possible, not in v5 it isn't anymore.

Is this project still active? If so, please make Tree::tag at least protected so that sub classes can access, it does not make much sense to hide it from a derived class imho.. and this limits functionality of sub tree currently...

https://github.com/JakeWharton/timber/blob/9954d94abbaea9d003243be5b69f8ae0ffc0c99d/timber/src/main/java/timber/log/Timber.kt#L25

Hi , when im trying to build release im getting this error.

Could not load custom lint check jar file C:\Users\me.gradle\caches\transforms-3\282411d3028f415e7f15eb7525ee01bd\transformed\jetified-timber-5.0.1\jars\lint.jar java.lang.NoClassDefFoundError: com/android/tools/lint/client/api/Vendor at timber.lint.TimberIssueRegistry.(TimberIssueRegistry.kt:25)

Using com.android.tools.build:gradle:4.2.2 , i think thats the problem.

More info here:

https://github.com/doublesymmetry/react-native-track-player/issues/1776

I am using file logging library getting parse error for date and log tag in console.

expected: Date [ClassName:LineNumber method]: Log What I am getting is: %PARSER_ERROR[d] [p92:1 z]: log

Hello, I just wanted to print a simple line like "10% space", no parameters. Just an example.

If I use Log like this there are no problems: Log.e("test", "10% space")

But if I use Timber it says I'm missing a parameter: Timber.e("10% space")

I tried escaping the symbol in several ways but with no luck:

"10\\% space" -> prints "10\% space"
"10%% space" -> prints "10%% space"

Am i missing something? Thanks

I added more details on the existing documentation file , focusing on the set up process of Timber once the dependencies have been downloaded.

In the documentation of Timber it was not clear on the implementation process in the application in Kotlin, like described in this Fixes #466 https://github.com/JakeWharton/timber/issues/466#issue-1206198186.

To fix that, I added the procedure to implement it programmatically in the users code base. It being a documentation update, the necessity of a test was not in mind.

I added the following under the Set Up section.I updated documentation but i can roll back if needed

Step 1 : Create an Application class that inherits from Application class .

open class MyProjectApplication : Application() {
}

Step 2 : import the application package

import android.app.Application

Step 3 : override the onCreate() method and initialize the Timber class

override the onCreate() method in your Application class

open class MyProjectApplication : Application() {
    if (BuildConfig.DEBUG) {
      Timber.plant(new DebugTree());
    } else {
      Timber.plant(new CrashReportingTree());
    }
  ##}

Step 4 : Define it in your Android Manifest , Application tag

In your application tag, add it as a name attribute :

<application  
       ....
       android:name=".MyProjectApplication"
       android:theme="@style/AppTheme"
      .... >