Tutorial by Examples

The attribute tools:ignore can be used in xml files to dismiss lint warnings. BUT dismissing lint warnings with this technique is most of the time the wrong way to proceed. A lint warning must be understood and fixed... it can be ignored if and only if you have a full understanding of it's meaning...

Using the Android API 23 or higher, very often such situation can be seen: This situation is caused by the structural change of the Android API regarding getting the resources. Now the function: public int getColor(@ColorRes int id, @Nullable Theme theme) throws NotFoundException should ...

You can configure lint by adding a lintOptions section in the build.gradle file: android { //..... lintOptions { // turn off checking the given issue id's disable 'TypographyFractions','TypographyQuotes' // turn on the given issue id's enable 'Rtl...

You can specify your Lint checking preferences in the lint.xml file. If you are creating this file manually, place it in the root directory of your Android project. If you are configuring Lint preferences in Android Studio, the lint.xml file is automatically created and added to your Android project...

You can disable Lint checking from your Java and XML source files. Configuring lint checking in Java To disable Lint checking specifically for a Java class or method in your Android project, add the @SuppressLint annotation to that Java code. Example: @SuppressLint("NewApi") @Override...

It's good practice to mark some warnings in your code. For example, some deprecated methods is need for your testing, or old support version. But Lint checking will mark that code with warnings. For avoiding this problem, you need use annotation @SuppressWarnings. For example, add ignoring to warni...