When running Lint on a project that uses SqlBrite 3.2.0:
Warning: Lint found an issue registry (com.squareup.sqlbrite3.BriteIssueRegistry) which did not specify the Lint API version it was compiled with.
This means that the lint checks are likely not compatible.
If you are the author of this lint check, make your lint IssueRegistry class contain
override val api: Int = com.android.tools.lint.detector.api.CURRENT_API
or from Java,
@Override public int getApi() { return com.android.tools.lint.detector.api.ApiKt.CURRENT_API; }
If you are just using lint checks from a third party library you have no control over, you can disable these lint checks (if they misbehave) like this:
Explanation for issues of type "ObsoleteLintCustomCheck":
Lint can be extended with "custom checks": additional checks implemented by
developers and libraries to for example enforce specific API usages
required by a library or a company coding style guideline.
The Lint APIs are not yet stable, so these checks may either cause a
performance, degradation, or stop working, or provide wrong results.
This warning flags custom lint checks that are found to be using obsolete
APIs and will need to be updated to run in the current lint environment.
It may also flag issues found to be using a newer version of the API,
meaning that you need to use a newer version of lint (or Android Studio or
Gradle plugin etc) to work with these checks.
Unfortunately, disabling 'SqlBriteArgCount' as shown above results in the following error:
Error: Unknown issue id "SqlBriteArgCount" [LintError]
disable "SqlBriteArgCount"
When running Lint on a project that uses SqlBrite 3.2.0:
Unfortunately, disabling 'SqlBriteArgCount' as shown above results in the following error: