Status Update
Comments
za...@gmail.com <za...@gmail.com> #2
uc...@google.com <uc...@google.com>
za...@gmail.com <za...@gmail.com> #3
This fails with kotlin 1.4.0-rc that was released today as well
ga...@google.com <ga...@google.com> #4
This is fixed in AGP 4.1.0-beta05, can you try that version? In 4.1 there is no PrepareLintJar
task so you should not hit this issue any more.
Fixed in:
za...@gmail.com <za...@gmail.com> #5
We are using 4.1.0-beta05 🤔
sa...@saket.me <sa...@saket.me> #6
Would adding an explicit compileOnly dependency on kotlin-stdlib be the correct workaround for users on AGP 4.0?
xa...@google.com <xa...@google.com> #7
Comment1: Version of Gradle Plugin: 4.0.1
Comment 5: We are using 4.1.0-beta05
Which is it? :) We are talking about AGP here. The version of Studio does not matter.
za...@gmail.com <za...@gmail.com> #8
Reproducible on both!
xa...@google.com <xa...@google.com> #9
The 4.1 branch does not have a PrepareLintJar
task. it only has PrepareLintJarForPublish
.
zs...@salesforce.com <zs...@salesforce.com> #10
To confirm some updates after further checking with Kotlin 1.4.0
With AGP 4.0.1 - reproduces there
With AGP 4.1.0-rc01 - it logs these warnings but appears to gracefully ignore them
> Task :app:lintExternalRelease
Custom lint rule jar /Users/zsweers/.gradle/caches/modules-2/files-2.1/org.jetbrains/annotations/13.0/919f0dfe192fb4e063e7dacadee7f8bb9a2672a9/annotations-13.0.jar does not contain a valid registry manifest key (Lint-Registry-v2).
Either the custom jar is invalid, or it uses an outdated API not supported this lint client
Custom lint rule jar /Users/zsweers/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-jdk7/1.4.0/9cc187c3dfaf6e4001bdf962e3cdadff7690261b/kotlin-stdlib-jdk7-1.4.0.jar does not contain a valid registry manifest key (Lint-Registry-v2).
Either the custom jar is invalid, or it uses an outdated API not supported this lint client
Custom lint rule jar /Users/zsweers/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-jdk8/1.4.0/e3765b66f0610afc92053ff1a93a87a544fca2b/kotlin-stdlib-jdk8-1.4.0.jar does not contain a valid registry manifest key (Lint-Registry-v2).
Either the custom jar is invalid, or it uses an outdated API not supported this lint client
Custom lint rule jar /Users/zsweers/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.4.0/63e75298e93d4ae0b299bb869cf0c627196f8843/kotlin-stdlib-1.4.0.jar does not contain a valid registry manifest key (Lint-Registry-v2).
Either the custom jar is invalid, or it uses an outdated API not supported this lint client
Custom lint rule jar /Users/zsweers/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-common/1.4.0/1c752cce0ead8d504ccc88a4fed6471fd83ab0dd/kotlin-stdlib-common-1.4.0.jar does not contain a valid registry manifest key (Lint-Registry-v2).
Either the custom jar is invalid, or it uses an outdated API not supported this lint client
It does appear that this is an unfortunate combination of the Kotlin gradle plugin automatically adding stdlib dependencies. This can be disabled by setting this gradle property (ideally just for your lint project): kotlin.stdlib.default.dependency=false
zs...@salesforce.com <zs...@salesforce.com> #11
Separately, there appears to be another lint issue with 1.4 when using member references that I've filed here:
za...@gmail.com <za...@gmail.com> #12
Confirmed that setting kotlin.stdlib.default.dependency=false
works 👍
gh...@google.com <gh...@google.com> #13
Closing as stale; let me know if there is something more to fix here.
Description
Steps to Reproduce:
1.4.0-rc-189
from maven repomaven("https://dl.bintray.com/kotlin/kotlin-dev")
. This is slightly newer than 1.4-M3prepareLintJar
gradle task in an application project with a local lint project as alintChecks(...)
dependency