IssueTracker

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

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.

Notes:

I suspect the exceptions are happening now because JetBrains recently changed an assert statement into a hard failure (see 3260e41111).

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.

It could also explain why not all lint rules were working from time to time (https://issuetracker.google.com/issues/149554597). According to Github, this change was done for 1.4-M2, which is considered unstable. Maybe lint runner could use an older but stable version? What else options do I have?

Is any public issue created I could follow?

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 :-)

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?

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 success
• checkDependencies = true, customLintChecks = false = 57% chance of success
• checkDependencies = 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 this issue in 3.6.3, but instead of skipped checks, we got crashes now.

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?

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.

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")

As opposed to lintPublish? Or is that not relevant?