Lint Report

Check performed at Wed Nov 02 17:59:38 UTC 2016.
1 errors and 62 warnings found:

Correctness
61Warning Assert: Assertions
1Error NewApi: Calling new methods on older versions
Usability:Icons
1Warning IconLocation: Image defined in density-independent drawable folder
Disabled Checks (17)

Correctness
Assert: Assertions
../../src/main/java/gov/nasa/worldwind/util/glu/tessellator/GLUtessellatorImpl.java:250: Assertions are unreliable. Use BuildConfig.DEBUG conditional checks instead.
 247         switch (which) {
 248             case GLU.GLU_TESS_TOLERANCE:
 249 /* tolerance should be in range [0..1] */
 250                 assert (0.0 <= relTolerance && relTolerance <= 1.0);
 251                 value[value_offset] = relTolerance;
 252                 break;
../../src/main/java/gov/nasa/worldwind/util/glu/tessellator/GLUtessellatorImpl.java:254: Assertions are unreliable. Use BuildConfig.DEBUG conditional checks instead.
 251                 value[value_offset] = relTolerance;
 252                 break;
 253             case GLU.GLU_TESS_WINDING_RULE:
 254                 assert (windingRule == GLU.GLU_TESS_WINDING_ODD ||
 255                         windingRule == GLU.GLU_TESS_WINDING_NONZERO ||
 256                         windingRule == GLU.GLU_TESS_WINDING_POSITIVE ||
../../src/main/java/gov/nasa/worldwind/util/glu/tessellator/GLUtessellatorImpl.java:262: Assertions are unreliable. Use BuildConfig.DEBUG conditional checks instead.
 259                 value[value_offset] = windingRule;
 260                 break;
 261             case GLU.GLU_TESS_BOUNDARY_ONLY:
 262                 assert (boundaryOnly == true || boundaryOnly == false);
 263                 value[value_offset] = boundaryOnly ? 1 : 0;
 264                 break;
../../src/main/java/gov/nasa/worldwind/util/glu/tessellator/Geom.java:72: Assertions are unreliable. Use BuildConfig.DEBUG conditional checks instead.
  69     static double EdgeEval(GLUvertex u, GLUvertex v, GLUvertex w) {
  70         double gapL, gapR;
  71 
  72         assert (VertLeq(u, v) && VertLeq(v, w));
  73 
  74         gapL = v.s - u.s;
../../src/main/java/gov/nasa/worldwind/util/glu/tessellator/Geom.java:91: Assertions are unreliable. Use BuildConfig.DEBUG conditional checks instead.
  88     static double EdgeSign(GLUvertex u, GLUvertex v, GLUvertex w) {
  89         double gapL, gapR;
  90 
  91         assert (VertLeq(u, v) && VertLeq(v, w));
  92 
  93         gapL = v.s - u.s;
Priority: 6 / 10
Category: Correctness
Severity: Warning
Explanation: Assertions.
Assertions are not checked at runtime. There are ways to request that they be used by Dalvik (adb shell setprop debug.assert 1), but the property is ignored in many places and can not be relied upon. Instead, perform conditional checking inside if (BuildConfig.DEBUG) { } blocks. That constant is a static final boolean which is true in debug builds and false in release builds, and the Java compiler completely removes all code inside the if-body from the app.

For example, you can replace assert speed > 0 with if (BuildConfig.DEBUG && !(speed > 0)) { throw new AssertionError() }.

(Note: This lint check does not flag assertions purely asserting nullness or non-nullness; these are typically more intended for tools usage than runtime checks.)

More info: https://code.google.com/p/android/issues/detail?id=65183

To suppress this error, use the issue id "Assert" as explained in the Suppressing Warnings and Errors section.
NewApi: Calling new methods on older versions
../../../worldwind: The SDK platform-tools version (23.0.1) is too old to check APIs compiled with API 24; please update
Note: This issue has an associated quickfix operation in Android Studio/IntelliJ & Eclipse/ADT
Priority: 6 / 10
Category: Correctness
Severity: Error
Explanation: Calling new methods on older versions.
This check scans through all the Android API calls in the application and warns about any calls that are not available on all versions targeted by this application (according to its minimum SDK attribute in the manifest).

If you really want to use this API and don't need to support older devices just set the minSdkVersion in your build.gradle or AndroidManifest.xml files.

If your code is deliberately accessing newer APIs, and you have ensured (e.g. with conditional execution) that this code will only ever be called on a supported platform, then you can annotate your class or method with the @TargetApi annotation specifying the local minimum SDK to apply, such as @TargetApi(11), such that this check considers 11 rather than your manifest file's minimum SDK as the required API level.

If you are deliberately setting android: attributes in style definitions, make sure you place this in a values-vNN folder in order to avoid running into runtime conflicts on certain devices where manufacturers have added custom attributes whose ids conflict with the new ones on later platforms.

Similarly, you can use tools:targetApi="11" in an XML file to indicate that the element will only be inflated in an adequate context.

More info:

To suppress this error, use the issue id "NewApi" as explained in the Suppressing Warnings and Errors section.
Usability:Icons
IconLocation: Image defined in density-independent drawable folder
../../src/main/res/drawable/gov_nasa_worldwind_worldtopobathy2004053.png: Found bitmap drawable res/drawable/gov_nasa_worldwind_worldtopobathy2004053.png in densityless folder
Priority: 5 / 10
Category: Usability:Icons
Severity: Warning
Explanation: Image defined in density-independent drawable folder.
The res/drawable folder is intended for density-independent graphics such as shapes defined in XML. For bitmaps, move it to drawable-mdpi and consider providing higher and lower resolution versions in drawable-ldpi, drawable-hdpi and drawable-xhdpi. If the icon really is density independent (for example a solid color) you can place it in drawable-nodpi.

More info: http://developer.android.com/guide/practices/screens_support.html

To suppress this error, use the issue id "IconLocation" as explained in the Suppressing Warnings and Errors section.
Disabled Checks
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.

AppLinksAutoVerifyError
Disabled By: Default
Priority: 5 / 10
Category: Correctness
Severity: Error
Explanation: App Links Auto Verification Failure.
Ensures that app links are correctly set and associated with website.

More info: https://g.co/appindexing/applinks

To suppress this error, use the issue id "AppLinksAutoVerifyError" as explained in the Suppressing Warnings and Errors section.
AppLinksAutoVerifyWarning
Disabled By: Default
Priority: 5 / 10
Category: Correctness
Severity: Warning
Explanation: Potential App Links Auto Verification Failure.
Ensures that app links are correctly set and associated with website.

More info: https://g.co/appindexing/applinks

To suppress this error, use the issue id "AppLinksAutoVerifyWarning" as explained in the Suppressing Warnings and Errors section.
BackButton
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.

More info: http://developer.android.com/design/patterns/pure-android.html

To suppress this error, use the issue id "BackButton" as explained in the Suppressing Warnings and Errors section.
EasterEgg
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.
FieldGetter
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.

More info: http://developer.android.com/guide/practices/design/performance.html#internal_get_set

To suppress this error, use the issue id "FieldGetter" as explained in the Suppressing Warnings and Errors section.
GoogleAppIndexingApiWarning
Note: This issue has an associated quickfix operation in Android Studio/IntelliJ
Disabled By: Default
Priority: 5 / 10
Category: Usability
Severity: Warning
Explanation: Missing support for Google App Indexing Api.
Adds URLs to get your app into the Google index, to get installs and traffic to your app from Google Search.

More info: https://g.co/AppIndexing/AndroidStudio

To suppress this error, use the issue id "GoogleAppIndexingApiWarning" as explained in the Suppressing Warnings and Errors section.
GradleDependency
Note: This issue has an associated quickfix operation in Android Studio/IntelliJ
Disabled By: Command line flag
Priority: 4 / 10
Category: Correctness
Severity: Warning
Explanation: Obsolete Gradle Dependency.
This detector looks for usages of libraries where the version you are using is not the current stable release. Using older versions is fine, and there are cases where you deliberately want to stick with an older version. However, you may simply not be aware that a more recent version is available, and that is what this lint check helps find.

More info:

To suppress this error, use the issue id "GradleDependency" as explained in the Suppressing Warnings and Errors section.
IconExpectedSize
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.

More info: http://developer.android.com/design/style/iconography.html

To suppress this error, use the issue id "IconExpectedSize" as explained in the Suppressing Warnings and Errors section.
LogConditional
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.
MangledCRLF
Note: This issue has an associated quickfix operation in Eclipse/ADT
Disabled By: Default
Priority: 2 / 10
Category: Correctness
Severity: Error
Explanation: Mangled file line endings.
On Windows, line endings are typically recorded as carriage return plus newline: \r\n.

This detector looks for invalid line endings with repeated carriage return characters (without newlines). Previous versions of the ADT plugin could accidentally introduce these into the file, and when editing the file, the editor could produce confusing visual artifacts.

More info: https://bugs.eclipse.org/bugs/show_bug.cgi?id=375421

To suppress this error, use the issue id "MangledCRLF" as explained in the Suppressing Warnings and Errors section.
MissingRegistered
Disabled By: Default
Priority: 8 / 10
Category: Correctness
Severity: Error
Explanation: Missing registered class.
If a class is referenced in the manifest or in a layout file, it must also exist in the project (or in one of the libraries included by the project. This check helps uncover typos in registration names, or attempts to rename or move classes without updating the manifest file properly.

More info: http://developer.android.com/guide/topics/manifest/manifest-intro.html

To suppress this error, use the issue id "MissingRegistered" as explained in the Suppressing Warnings and Errors section.
NegativeMargin
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.
NewerVersionAvailable
Note: This issue has an associated quickfix operation in Android Studio/IntelliJ
Disabled By: Default
Priority: 4 / 10
Category: Correctness
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.
SelectableText
Note: This issue has an associated quickfix operation in Android Studio/IntelliJ
Disabled By: Default
Priority: 7 / 10
Category: Usability
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.
StopShip
Note: This issue has an associated quickfix operation in Android Studio/IntelliJ
Disabled By: Default
Priority: 10 / 10
Category: Correctness
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.
TypographyQuotes
Note: This issue has an associated quickfix operation in Android Studio/IntelliJ & Eclipse/ADT
Disabled By: Default
Priority: 5 / 10
Category: Usability:Typography
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.)

More info: http://en.wikipedia.org/wiki/Quotation_mark

To suppress this error, use the issue id "TypographyQuotes" as explained in the Suppressing Warnings and Errors section.
UnusedIds
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://g.co/androidstudio/suppressing-lint-warnings