Status Update
No update yet.
Comments
ku...@google.com
gh...@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
gh...@google.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.
xo...@google.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.
gh...@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?
Description
AI-213.7172.25.2113.9123335, JRE 11.0.13+0-b1751.21-8125866x64 JetBrains s.r.o., OS Linux(amd64) v5.17.0-1020-oem, screens 1920.0x1080.0, 2560.0x1440.0
AS: Dolphin | 2021.3.1 Patch 1
Kotlin plugin: 213-1.7.20-release-for-android-studio-AS6777.52
Android Gradle Plugin: 7.3.1
Gradle: 7.4
Gradle JDK: version 11.0.13
NDK: from local.properties: (not specified), latest from SDK: (not found)
CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)
IMPORTANT: Please read
In my build.grade file, I have specified a number of dependencies. In order to ensure that builds don't break when transitive dependencies change, I'm pinning the version of packages to build with. For example, I have:
"implementation 'androidx.appcompat:appcompat:1.5.1!!'"
What is strange is that Android Studio highlights this statement stating:
"A newer version of androidx.appcompat:appcompat than 1.5.1!! is available: 1.5.1"
It appears that the UI is doing a textual string comparison rather than a semantic version comparison. The pinned version is the latest available and should not be highlighted for action.