CODEWITHSUNDEEP
androidandroid-studiogradleandroid-gradle-pluginlint
user1033552
user1033552

Reputation: 1529

Default release lint vs. gradle lint task

By default lint is enabled for release builds in gradle. Without the 

abortOnError false

option this aborts a build.

My release build executes successfully (without lint warnings), but when I call the lintRelease task via gradle it fails with 3 errors and 222 warnings.

Further more, if I use the "Analyse"-"Inspect code..." functionality from the Android Studio menu I even get a different result.

Why do these approaches behave differently and whats the difference between them?

Upvotes: 1

Views: 659

Answers (1)

koto
koto

Reputation: 740

'Inspect code', as an IDE feature, uses not only android lint to perform a code checkup, but also many other custom actions (searching for infinite loops, code styling, suggesting replacing anonymous types with lambdas etc.).

From experience, mine and many other developers', it is almost impossible to deploy a production app without lint warnings.

Upvotes: 1

Related Questions