Status Update
Comments
se...@candybytes.com <se...@candybytes.com> #2
Lint options:
lintOptions {
lintConfig = file('lint.xml')
abortOnError true
xmlReport true
htmlReport true
checkDependencies true
}
Also, our project has custom lint rules. Failure happens with a dependency of 26.6.3 and 27.0.0.
Is any way to downgrade lint runner? This problem is keeping us from using AGP 4.0
an...@google.com <an...@google.com>
an...@google.com <an...@google.com> #3
Attached slightly different stacktrace for the same problem.
Wonder if disabling some lint rules could help to "fix" this problem, as it is also blocking for us 4.0 AGP upgrade.
ap...@google.com <ap...@google.com> #4
Notes:
I suspect the exceptions are happening now because JetBrains recently changed an assert
statement into a hard failure (see
I.e., it's possible that Lint has been hitting this code path all along, and only now it is causing a problem.
This has been difficult to investigate so far because the failure is nondeterministic and also deep inside the Kotlin compiler. Plus, JetBrains seems to be hitting this code path occasionally too (hence why they changed the assert into a hard failure), so I'm not even sure whether Lint is implicated or not.
na...@google.com <na...@google.com> #5
It could also explain why not all lint rules were working from time to time (
Is any public issue created I could follow?
mi...@gmail.com <mi...@gmail.com> #6
Has anyone tried this with 4.1.0-beta2? We're using a more recent version of UAST and the Kotlin compiler there. It's not clear that it's fixed but -- there's a chance :-)
an...@google.com <an...@google.com> #7
I tried. The same error. I am wondering, is any way to know which lint checks cause failure? I have a few custom lint checks. Or, is any way downgrade compiler for lint checks?
ju...@google.com <ju...@google.com> #8
I did more tests and probably narrow down a cause. I did all tests on 4.1.0-beta2
. Original configuration have enabled checkDependencies
and included custom lint checks. Custom lint checks are compiled using 26.6.3
version:
checkDependencies = true, customLintChecks = true
= 20% chance of successcheckDependencies = true, customLintChecks = false
= 57% chance of successcheckDependencies = false, customLintChecks = true
= 100% chance of success
It is a clear evidence that checkDependencies
feature is not stable. In addition, custom lint checks is not friendly with checkDependencies
and increases the risk of failure. Or maybe just an old lint SDK used is to blame.
It is very similar to
I have a theory, but do not know how to test. Maybe crashes happening because there are some lint checks from libs built upon old lint SDK version?
Description
Jetpack Compose component(s) used: androidxCompose = "1.3.0-rc01" androidxComposeCompiler = "1.3.2" androidxComposeMaterial3 = "1.0.0-alpha13" androidxComposeMaterial = "1.2.1"
Android Studio Build: Build #AI-222.4167.29.2221.9133400, built on October 4, 2022
Kotlin version: kotlin = "1.7.20"
Steps to Reproduce or Code Sample to Reproduce:
I struggle with a "Key" problem since I updated from androidx.compose "1.3.0-beta03" to "1.3.0-rc01".
I use LazyPagingItems for a LazyVerticalGrid and i add items like this in the LazyGridScope:
But since the library update, when I filter the content (so the paging items are updated in the flow), it throws an Exception. This exception wasn't thrown in the beta03 library version.
Because paging data is changing and elements become null while loading I can't supply a unique key, the App crashes. Is this a bug in the library or what exactly is the best practice when using LazyPagingItems that can change over time if you'd like to work with keys in the LazyGrid?
Stack trace (if applicable):