Fixed
Status Update
Comments
uc...@google.com <uc...@google.com> #2
Reproduced in
Android Studio 3.1 Canary 9
Build #AI-173.4559767, built on January 22, 2018
JRE: 1.8.0_152-release-1024-b01 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.9.0-5-amd64
Android Studio 3.1 Canary 9
Build #AI-173.4559767, built on January 22, 2018
JRE: 1.8.0_152-release-1024-b01 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.9.0-5-amd64
tn...@google.com <tn...@google.com> #3
(1) is intentional; when you use a library, that library can provide checks that should be run against client code of the library. That's what's happening here: timber ships with lint rules that makes sure you're using the library correctly.
But (2) is a bug: Fixed by Change-Id: I4d2b8ddecaa64b6e42ccfb3a106b627a62d5d069 for 3.2 canary3 3. Thanks for the report!
But (2) is a bug: Fixed by Change-Id: I4d2b8ddecaa64b6e42ccfb3a106b627a62d5d069 for 3.2 canary3 3. Thanks for the report!
bo...@gmail.com <bo...@gmail.com> #4
inmiyor !!!!!!!!!!!!!!!!
güncellemeler daha sonra inme yapıyor, hemen anlık inmiyor.
güncellemeler daha sonra inme yapıyor, hemen anlık inmiyor.
Description
AGP: 3.1.0-alpha09
Gradle: 4.5
There are two bugs here:
1) Lint reports an `ObsoleteLintCustomCheck` warning for checks that come from third party libs (e.g. butterknife or timber)
2) Lint doesn't honor the exclusions in `lint.xml`, meaning that it will flag the `ObsoleteLintCustomCheck` even if its severity is set as ignored.
I have attached a project that reproduces this bug.
You can test it by running `./gradlew :app:lintDebug`