Status Update
No update yet.
Comments
sg...@google.com
sg...@google.com
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
ph...@gmail.com
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.
ra...@gmail.com
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.
ap...@google.com
It could also explain why not all lint rules were working from time to time (
Is any public issue created I could follow?
ap...@google.com
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 :-)
ap...@google.com
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?
ap...@google.com
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?
ap...@google.com
To me this is happening on 4.2.0-alpha04 too.
Can someone confirm that this is happening if you have these three conditions met?:
- checkDependencies=true on your app module
- have a custom lint rule using lintChecks on your app module
- have a custom lint rule using lintChecks on your library module
For me the error went away after I removed the lintChecks on the library module.
ap...@google.com
could you clarify exactly what you mean in these?
have a custom lint rule using lintChecks on your app module have a custom lint rule using lintChecks on your library module
By this I mean a declaration in your modules dependency block:
lintChecks project(":features:language_lint")
Description
I started seeing
minifyReleaseWithR8task failure of my Compose project. It fails with some random project library jar, e.g.If I exclude this library from proguard, it'll fail with some next library - it can be both Compose one or any other, looks like message is unrelated to the problem.
By commenting code in the project, I've found out that I can fix the build by replacing one of
@StringRes param: Intin composable function withparam: String. But I still not sure if that's the root case.When trying to reproduce it in a sample project, I was able to reproduce it with even simpler code, that doesn't include int parameter. If I switch from compose-material to compose-material3, it builds fine.
MRE with dependencies is attached.