Lint Report
Check performed at Wed Apr 01 15:02:38 CEST 2015.
0 errors and 5 warnings found:
../../src/main/AndroidManifest.xml:25:
This minSdkVersion
value (9
) is not used; it is always overridden by the value specified in the Gradle build script (9
)
22 <!-- GCM requires Android SDK version 2.2 (API level 8) or above. -->
23 <!-- The targetSdkVersion is optional, but it's always a good practice
24 to target higher versions. -->
25 <uses-sdk android:minSdkVersion="9" android:targetSdkVersion="21"/>
26
27 <!-- GCM connects to Google Services. -->
../../src/main/AndroidManifest.xml:25:
This targetSdkVersion
value (21
) is not used; it is always overridden by the value specified in the Gradle build script (21
)
22 <!-- GCM requires Android SDK version 2.2 (API level 8) or above. -->
23 <!-- The targetSdkVersion is optional, but it's always a good practice
24 to target higher versions. -->
25 <uses-sdk android:minSdkVersion="9" android:targetSdkVersion="21"/>
26
27 <!-- GCM connects to Google Services. -->
Priority: 4 / 10
Category: Correctness
Severity:
Warning
Explanation: Value overridden by Gradle build script.
The value of (for example) minSdkVersion
is only used if it is not specified in the build.gradle
build scripts. When specified in the Gradle build scripts, the manifest value is ignored and can be misleading, so should be removed to avoid ambiguity.
More info:
To suppress this error, use the issue id "GradleOverrides" as explained in the
Suppressing Warnings and Errors section.
../../src/main/res/values/strings.xml:20:
The resource R.string.send
appears to be unused
17 <resources>
18
19 <string name="app_name">GCM Demo</string>
20 <string name="send">Send</string>
21 <string name="clear">Clear</string>
22
../../src/main/res/values/strings.xml:21:
The resource R.string.clear
appears to be unused
18
19 <string name="app_name">GCM Demo</string>
20 <string name="send">Send</string>
21 <string name="clear">Clear</string>
22
23 </resources>
Priority: 3 / 10
Category: Performance
Severity:
Warning
Explanation: Unused resources.
Unused resources make applications larger and slow down builds.
More info:
To suppress this error, use the issue id "UnusedResources" as explained in the
Suppressing Warnings and Errors section.
../../src/main/res:
Missing density variation folders in src/main/res
: drawable-xxhdpi, drawable-xxxhdpi
Priority: 3 / 10
Category: Usability:Icons
Severity:
Warning
Explanation: Missing density folder.
Icons will look best if a custom version is provided for each of the major screen density classes (low, medium, high, extra-high, extra-extra-high). This lint check identifies folders which are missing, such as
drawable-hdpi
.
Low density is not really used much anymore, so this check ignores the ldpi density. To force lint to include it, set the environment variable
ANDROID_LINT_INCLUDE_LDPI=true
. For more information on current density usage, see
http://developer.android.com/resources/dashboard/screens.html
To suppress this error, use the issue id "IconMissingDensityFolder" as explained in the
Suppressing Warnings and Errors section.
The following issues were not run by lint, either because the check is not enabled by default, or because it was disabled with a command line flag or via one or more lint.xml configuration files in the project directories.
Disabled By: Default
Priority: 6 / 10
Category: Usability
Severity:
Warning
Explanation: Back button.
According to the Android Design Guide,
"Other platforms use an explicit back button with label to allow the user to navigate up the application's hierarchy. Instead, Android uses the main action bar's app icon for hierarchical navigation and the navigation bar's back button for temporal navigation."
This check is not very sophisticated (it just looks for buttons with the label "Back"), so it is disabled by default to not trigger on common scenarios like pairs of Back/Next buttons to paginate through screens.
To suppress this error, use the issue id "BackButton" as explained in the
Suppressing Warnings and Errors section.
Disabled By: Default
Priority: 6 / 10
Category: Security
Severity:
Warning
Explanation: Code contains easter egg.
An "easter egg" is code deliberately hidden in the code, both from potential users and even from other developers. This lint check looks for code which looks like it may be hidden from sight.
More info:
To suppress this error, use the issue id "EasterEgg" as explained in the
Suppressing Warnings and Errors section.
Disabled By: Default
Priority: 4 / 10
Category: Performance
Severity:
Warning
Explanation: Using getter instead of field.
Accessing a field within the class that defines a getter for that field is at least 3 times faster than calling the getter. For simple getters that do nothing other than return the field, you might want to just reference the local field directly instead.
NOTE: As of Android 2.3 (Gingerbread), this optimization is performed automatically by Dalvik, so there is no need to change your code; this is only relevant if you are targeting older versions of Android.
To suppress this error, use the issue id "FieldGetter" as explained in the
Suppressing Warnings and Errors section.
Disabled By: Default
Priority: 5 / 10
Category: Usability:Icons
Severity:
Warning
Explanation: Icon has incorrect size.
There are predefined sizes (for each density) for launcher icons. You should follow these conventions to make sure your icons fit in with the overall look of the platform.
To suppress this error, use the issue id "IconExpectedSize" as explained in the
Suppressing Warnings and Errors section.
Disabled By: Default
Priority: 5 / 10
Category: Performance
Severity:
Warning
Explanation: Unconditional Logging Calls.
The BuildConfig class (available in Tools 17) provides a constant, "DEBUG", which indicates whether the code is being built in release mode or in debug mode. In release mode, you typically want to strip out all the logging calls. Since the compiler will automatically remove all code which is inside a "if (false)" check, surrounding your logging calls with a check for BuildConfig.DEBUG is a good idea.
If you really intend for the logging to be present in release mode, you can suppress this warning with a @SuppressLint annotation for the intentional logging calls.
More info:
To suppress this error, use the issue id "LogConditional" as explained in the
Suppressing Warnings and Errors section.
Disabled By: Default
Priority: 4 / 10
Category: Usability
Severity:
Warning
Explanation: Negative Margins.
Margin values should be positive. Negative values are generally a sign that you are making assumptions about views surrounding the current one, or may be tempted to turn off child clipping to allow a view to escape its parent. Turning off child clipping to do this not only leads to poor graphical performance, it also results in wrong touch event handling since touch events are based strictly on a chain of parent-rect hit tests. Finally, making assumptions about the size of strings can lead to localization problems.
More info:
To suppress this error, use the issue id "NegativeMargin" as explained in the
Suppressing Warnings and Errors section.
Severity:
Warning
Explanation: Newer Library Versions Available.
This detector checks with a central repository to see if there are newer versions available for the dependencies used by this project.
This is similar to the GradleDependency
check, which checks for newer versions available in the Android SDK tools and libraries, but this works with any MavenCentral dependency, and connects to the library every time, which makes it more flexible but also much slower.
More info:
To suppress this error, use the issue id "NewerVersionAvailable" as explained in the
Suppressing Warnings and Errors section.
Severity:
Warning
Explanation: Dynamic text should probably be selectable.
If a <TextView>
is used to display data, the user might want to copy that data and paste it elsewhere. To allow this, the <TextView>
should specify android:textIsSelectable="true"
.
This lint check looks for TextViews which are likely to be displaying data: views whose text is set dynamically. This value will be ignored on platforms older than API 11, so it is okay to set it regardless of your minSdkVersion
.
More info:
To suppress this error, use the issue id "SelectableText" as explained in the
Suppressing Warnings and Errors section.
Severity:
Warning
Explanation: Code contains STOPSHIP
marker.
Using the comment // STOPSHIP
can be used to flag code that is incomplete but checked in. This comment marker can be used to indicate that the code should not be shipped until the issue is addressed, and lint will look for these.
More info:
To suppress this error, use the issue id "StopShip" as explained in the
Suppressing Warnings and Errors section.
Severity:
Warning
Explanation: Straight quotes can be replaced with curvy quotes.
Straight single quotes and double quotes, when used as a pair, can be replaced by "curvy quotes" (or directional quotes). This can make the text more readable.
Note that you should never use grave accents and apostrophes to quote, `like this'.
(Also note that you should not use curvy quotes for code fragments.)
To suppress this error, use the issue id "TypographyQuotes" as explained in the
Suppressing Warnings and Errors section.
Disabled By: Default
Priority: 1 / 10
Category: Performance
Severity:
Warning
Explanation: Unused id.
This resource id definition appears not to be needed since it is not referenced from anywhere. Having id definitions, even if unused, is not necessarily a bad idea since they make working on layouts and menus easier, so there is not a strong reason to delete these.
More info:
To suppress this error, use the issue id "UnusedIds" as explained in the
Suppressing Warnings and Errors section.
Suppressing Warnings and Errors
Lint errors can be suppressed in a variety of ways:
1. With a @SuppressLint
annotation in the Java code
2. With a tools:ignore
attribute in the XML file
3. With ignore flags specified in the build.gradle
file, as explained below
4. With a lint.xml
configuration file in the project
5. With a lint.xml
configuration file passed to lint via the --config flag
6. With the --ignore flag passed to lint.
To suppress a lint warning with an annotation, add a @SuppressLint("id")
annotation on the class, method or variable declaration closest to the warning instance you want to disable. The id can be one or more issue id's, such as "UnusedResources"
or {"UnusedResources","UnusedIds"}
, or it can be "all"
to suppress all lint warnings in the given scope.
To suppress a lint warning in an XML file, add a tools:ignore="id"
attribute on the element containing the error, or one of its surrounding elements. You also need to define the namespace for the tools prefix on the root element in your document, next to the xmlns:android
declaration:
xmlns:tools="http://schemas.android.com/tools"
To suppress a lint warning in a build.gradle
file, add a section like this:
android {
lintOptions {
disable 'TypographyFractions','TypographyQuotes'
}
}
Here we specify a comma separated list of issue id's after the disable command. You can also use warning
or error
instead of disable
to change the severity of issues.
To suppress lint warnings with a configuration XML file, create a file named lint.xml
and place it at the root directory of the project in which it applies.
The format of the lint.xml
file is something like the following:
<?xml version="1.0" encoding="UTF-8"?>
<lint>
<!-- Disable this given check in this project -->
<issue id="IconMissingDensityFolder" severity="ignore" />
<!-- Ignore the ObsoleteLayoutParam issue in the given files -->
<issue id="ObsoleteLayoutParam">
<ignore path="res/layout/activation.xml" />
<ignore path="res/layout-xlarge/activation.xml" />
</issue>
<!-- Ignore the UselessLeaf issue in the given file -->
<issue id="UselessLeaf">
<ignore path="res/layout/main.xml" />
</issue>
<!-- Change the severity of hardcoded strings to "error" -->
<issue id="HardcodedText" severity="error" />
</lint>
To suppress lint checks from the command line, pass the --ignore flag with a comma separated list of ids to be suppressed, such as:
$ lint --ignore UnusedResources,UselessLeaf /my/project/path
For more information, see http://tools.android.com/tips/lint/suppressing-lint-warnings