react-native-fetch-calendar-events

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Lint Report</title> <link rel="stylesheet" type="text/css" href="http://fonts.googleapis.com/css?family=Roboto" /> <link rel="stylesheet" type="text/css" href="lint-results-debug_files/hololike.css" /> <script language="javascript" type="text/javascript">  </script> </head> <body> <h1>Lint Report</h1> <div class="titleSeparator"></div> Check performed at Wed Nov 30 23:17:32 EET 2016.<br/> 0 errors and 7 warnings found:<br/><br/> <table class="overview"> <tr><td></td><td class="categoryColumn"><a href="#Correctness">Correctness</a> </td></tr> <tr> <td class="countColumn">1</td><td class="issueColumn"><img border="0" align="top" src="lint-results-debug_files/lint-warning.png" alt="Warning" /> <a href="#InvalidPackage">InvalidPackage: Package not included in Android</a> </td></tr> <tr> <td class="countColumn">1</td><td class="issueColumn"><img border="0" align="top" src="lint-results-debug_files/lint-warning.png" alt="Warning" /> <a href="#OldTargetApi">OldTargetApi: Target SDK attribute is not targeting latest version</a> </td></tr> <tr> <td class="countColumn">2</td><td class="issueColumn"><img border="0" align="top" src="lint-results-debug_files/lint-warning.png" alt="Warning" /> <a href="#SimpleDateFormat">SimpleDateFormat: Implied locale in date format</a> </td></tr> <tr> <td class="countColumn">1</td><td class="issueColumn"><img border="0" align="top" src="lint-results-debug_files/lint-warning.png" alt="Warning" /> <a href="#GradleDependency">GradleDependency: Obsolete Gradle Dependency</a> </td></tr> <tr> <td class="countColumn">1</td><td class="issueColumn"><img border="0" align="top" src="lint-results-debug_files/lint-warning.png" alt="Warning" /> <a href="#GradleDynamicVersion">GradleDynamicVersion: Gradle Dynamic Version</a> </td></tr> <tr><td></td><td class="categoryColumn"><a href="#Performance">Performance</a> </td></tr> <tr> <td class="countColumn">1</td><td class="issueColumn"><img border="0" align="top" src="lint-results-debug_files/lint-warning.png" alt="Warning" /> <a href="#Recycle">Recycle: Missing <code>recycle()</code> calls</a> </td></tr> <tr><td></td><td class="categoryColumn"><a href="#MissingIssues">Disabled Checks (15)</a> </td></tr></table> <br/> <a name="Correctness"></a> <div class="category"><a href="#" title="Return to top">Correctness</a><div class="categorySeparator"></div> </div> <a name="InvalidPackage"></a> <div class="issue"> <div class="id"><a href="#" title="Return to top">InvalidPackage: Package not included in Android</a><div class="issueSeparator"></div> </div> <div class="warningslist"> <span class="location"><a href="../../../../../../.gradle/caches/modules-2/files-2.1/com.squareup.okio/okio/1.6.0/98476622f10715998eacf9240d6b479f12c66143/okio-1.6.0.jar">../../../../../../.gradle/caches/modules-2/files-2.1/com.squareup.okio/okio/1.6.0/98476622f10715998eacf9240d6b479f12c66143/okio-1.6.0.jar</a></span>: <span class="message">Invalid package reference in library; not included in Android: <code>java.nio.file</code>. Referenced from <code>okio.Okio</code>.</span><br /> </div> <div class="metadata">Priority: 6 / 10<br/> Category: Correctness</div> Severity: <span class="warning">Warning</span><div class="summary"> Explanation: Package not included in Android.</div> <div class="explanation"> This check scans through libraries looking for calls to APIs that are not included in Android.<br/> <br/> When you create Android projects, the classpath is set up such that you can only access classes in the API packages that are included in Android. However, if you add other projects to your libs/ folder, there is no guarantee that those .jar files were built with an Android specific classpath, and in particular, they could be accessing unsupported APIs such as java.applet.<br/> <br/> This check scans through library jars and looks for references to API packages that are not included in Android and flags these. This is only an error if your code calls one of the library classes which wind up referencing the unsupported package. </div> <br/><div class="moreinfo">More info: </div><br/>To suppress this error, use the issue id "InvalidPackage" as explained in the <a href="#SuppressInfo">Suppressing Warnings and Errors</a> section.<br/> </div> <a name="OldTargetApi"></a> <div class="issue"> <div class="id"><a href="#" title="Return to top">OldTargetApi: Target SDK attribute is not targeting latest version</a><div class="issueSeparator"></div> </div> <div class="warningslist"> <span class="location"><a href="../../build.gradle">../../build.gradle</a>:24</span>: <span class="message">Not targeting the latest versions of Android; compatibility modes apply. Consider testing and updating this version. Consult the android.os.Build.VERSION_CODES javadoc for details.</span><br /><pre class="errorlines"> <span class="lineno"> 21</span> <span class="lineno"> 22</span> defaultConfig { <span class="lineno"> 23</span> minSdkVersion 16 <span class="lineno"> 24</span> <span class="errorspan">targetSdkVersion 22</span> <span class="lineno"> 25</span> versionCode 1 <span class="lineno"> 26</span> versionName "1.0" </pre> </div> <div class="metadata">Note: This issue has an associated quickfix operation in Android Studio/IntelliJ <img alt="Fix" border="0" align="top" src="lint-results-debug_files/lint-run.png" /> <br> Priority: 6 / 10<br/> Category: Correctness</div> Severity: <span class="warning">Warning</span><div class="summary"> Explanation: Target SDK attribute is not targeting latest version.</div> <div class="explanation"> When your application runs on a version of Android that is more recent than your <code>targetSdkVersion</code> specifies that it has been tested with, various compatibility modes kick in. This ensures that your application continues to work, but it may look out of place. For example, if the <code>targetSdkVersion</code> is less than 14, your app may get an option button in the UI.<br/> <br/> To fix this issue, set the <code>targetSdkVersion</code> to the highest available value. Then test your app to make sure everything works correctly. You may want to consult the compatibility notes to see what changes apply to each version you are adding support for: <a href="http://developer.android.com/reference/android/os/Build.VERSION_CODES.html">http://developer.android.com/reference/android/os/Build.VERSION_CODES.html</a> </div> <br/><div class="moreinfo">More info: <a href="http://developer.android.com/reference/android/os/Build.VERSION_CODES.html">http://developer.android.com/reference/android/os/Build.VERSION_CODES.html</a> </div><br/>To suppress this error, use the issue id "OldTargetApi" as explained in the <a href="#SuppressInfo">Suppressing Warnings and Errors</a> section.<br/> </div> <a name="SimpleDateFormat"></a> <div class="issue"> <div class="id"><a href="#" title="Return to top">SimpleDateFormat: Implied locale in date format</a><div class="issueSeparator"></div> </div> <div class="warningslist"> <span class="location"><a href="../../src/main/java/com/calendarevents/CalendarEvents.java">../../src/main/java/com/calendarevents/CalendarEvents.java</a>:99</span>: <span class="message">To get local formatting use <code>getDateInstance()</code>, <code>getDateTimeInstance()</code>, or <code>getTimeInstance()</code>, or use <code>new SimpleDateFormat(String template, Locale locale)</code> with for example <code>Locale.US</code> for ASCII dates.</span><br /><pre class="errorlines"> <span class="lineno"> 96</span> //region Event Accessors <span class="lineno"> 97</span> public WritableMap addEvent(String title, ReadableMap details) throws ParseException { <span class="lineno"> 98</span> String dateFormat = "yyyy-MM-dd'T'HH:mm:ss.SSS'Z'"; <span class="lineno"> 99</span> SimpleDateFormat sdf = <span class="errorspan">new SimpleDateFormat(dateFormat);</span> <span class="lineno"> 100</span> sdf.setTimeZone(TimeZone.getTimeZone("GMT")); <span class="lineno"> 101</span> </pre> <span class="location"><a href="../../src/main/java/com/calendarevents/Utility.java">../../src/main/java/com/calendarevents/Utility.java</a>:45</span>: <span class="message">To get local formatting use <code>getDateInstance()</code>, <code>getDateTimeInstance()</code>, or <code>getTimeInstance()</code>, or use <code>new SimpleDateFormat(String template, Locale locale)</code> with for example <code>Locale.US</code> for ASCII dates.</span><br /><pre class="errorlines"> <span class="lineno"> 42</span> } <span class="lineno"> 43</span> <span class="lineno"> 44</span> public static String getDate(long milliSeconds) { <span class="lineno"> 45</span> SimpleDateFormat formatter = <span class="errorspan">new SimpleDateFormat(</span> <span class="lineno"> 46</span> "dd/MM/yyyy hh:mm:ss a"); <span class="lineno"> 47</span> Calendar calendar = Calendar.getInstance(); </pre> </div> <div class="metadata">Priority: 6 / 10<br/> Category: Correctness</div> Severity: <span class="warning">Warning</span><div class="summary"> Explanation: Implied locale in date format.</div> <div class="explanation"> Almost all callers should use <code>getDateInstance()</code>, <code>getDateTimeInstance()</code>, or <code>getTimeInstance()</code> to get a ready-made instance of SimpleDateFormat suitable for the user's locale. The main reason you'd create an instance this class directly is because you need to format/parse a specific machine-readable format, in which case you almost certainly want to explicitly ask for US to ensure that you get ASCII digits (rather than, say, Arabic digits).<br/> <br/> Therefore, you should either use the form of the SimpleDateFormat constructor where you pass in an explicit locale, such as Locale.US, or use one of the get instance methods, or suppress this error if really know what you are doing. </div> <br/><div class="moreinfo">More info: <a href="http://developer.android.com/reference/java/text/SimpleDateFormat.html">http://developer.android.com/reference/java/text/SimpleDateFormat.html</a> </div><br/>To suppress this error, use the issue id "SimpleDateFormat" as explained in the <a href="#SuppressInfo">Suppressing Warnings and Errors</a> section.<br/> </div> <a name="GradleDependency"></a> <div class="issue"> <div class="id"><a href="#" title="Return to top">GradleDependency: Obsolete Gradle Dependency</a><div class="issueSeparator"></div> </div> <div class="warningslist"> <span class="location"><a href="../../build.gradle">../../build.gradle</a>:20</span>: <span class="message">Old buildToolsVersion 23.0.1; recommended version is 23.0.3 or later</span><br /><pre class="errorlines"> <span class="lineno"> 17</span> <span class="lineno"> 18</span> android { <span class="lineno"> 19</span> compileSdkVersion 23 <span class="lineno"> 20</span> <span class="errorspan">buildToolsVersion "23.0.1"</span> <span class="lineno"> 21</span> <span class="lineno"> 22</span> defaultConfig { </pre> </div> <div class="metadata">Note: This issue has an associated quickfix operation in Android Studio/IntelliJ <img alt="Fix" border="0" align="top" src="lint-results-debug_files/lint-run.png" /> <br> Priority: 4 / 10<br/> Category: Correctness</div> Severity: <span class="warning">Warning</span><div class="summary"> Explanation: Obsolete Gradle Dependency.</div> <div class="explanation"> 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. </div> <br/><div class="moreinfo">More info: </div><br/>To suppress this error, use the issue id "GradleDependency" as explained in the <a href="#SuppressInfo">Suppressing Warnings and Errors</a> section.<br/> </div> <a name="GradleDynamicVersion"></a> <div class="issue"> <div class="id"><a href="#" title="Return to top">GradleDynamicVersion: Gradle Dynamic Version</a><div class="issueSeparator"></div> </div> <div class="warningslist"> <span class="location"><a href="../../build.gradle">../../build.gradle</a>:35</span>: <span class="message">Avoid using + in version numbers; can lead to unpredictable and unrepeatable builds (com.facebook.react:react-native:+)</span><br /><pre class="errorlines"> <span class="lineno"> 32</span> } <span class="lineno"> 33</span> <span class="lineno"> 34</span> dependencies { <span class="lineno"> 35</span> <span class="errorspan">compile 'com.facebook.react:react-native:+'</span> <span class="lineno"> 36</span> } <span class="lineno"> 37</span> </pre> </div> <div class="metadata">Note: This issue has an associated quickfix operation in Android Studio/IntelliJ <img alt="Fix" border="0" align="top" src="lint-results-debug_files/lint-run.png" /> <br> Priority: 4 / 10<br/> Category: Correctness</div> Severity: <span class="warning">Warning</span><div class="summary"> Explanation: Gradle Dynamic Version.</div> <div class="explanation"> Using <code>+</code> in dependencies lets you automatically pick up the latest available version rather than a specific, named version. However, this is not recommended; your builds are not repeatable; you may have tested with a slightly different version than what the build server used. (Using a dynamic version as the major version number is more problematic than using it in the minor version position.) </div> <br/><div class="moreinfo">More info: </div><br/>To suppress this error, use the issue id "GradleDynamicVersion" as explained in the <a href="#SuppressInfo">Suppressing Warnings and Errors</a> section.<br/> </div> <a name="Performance"></a> <div class="category"><a href="#" title="Return to top">Performance</a><div class="categorySeparator"></div> </div> <a name="Recycle"></a> <div class="issue"> <div class="id"><a href="#" title="Return to top">Recycle: Missing <code>recycle()</code> calls</a><div class="issueSeparator"></div> </div> <div class="warningslist"> <span class="location"><a href="../../src/main/java/com/calendarevents/Utility.java">../../src/main/java/com/calendarevents/Utility.java</a>:20</span>: <span class="message">This <code>Cursor</code> should be freed up after use with <code>#close()</code></span><br /><pre class="errorlines"> <span class="lineno"> 17</span> public static WritableArray readCalendarEvent(Context context) { <span class="lineno"> 18</span> WritableArray events = Arguments.createArray(); <span class="lineno"> 19</span> Cursor cursor = context.getContentResolver() <span class="lineno"> 20</span> .<span class="errorspan">query(</span> <span class="lineno"> 21</span> Uri.parse("content://com.android.calendar/events"), <span class="lineno"> 22</span> new String[] { "calendar_id", "title", "description", </pre> </div> <div class="metadata">Priority: 7 / 10<br/> Category: Performance</div> Severity: <span class="warning">Warning</span><div class="summary"> Explanation: Missing <code>recycle()</code> calls.</div> <div class="explanation"> Many resources, such as TypedArrays, VelocityTrackers, etc., should be recycled (with a <code>recycle()</code> call) after use. This lint check looks for missing <code>recycle()</code> calls. </div> <br/><div class="moreinfo">More info: </div><br/>To suppress this error, use the issue id "Recycle" as explained in the <a href="#SuppressInfo">Suppressing Warnings and Errors</a> section.<br/> </div> <a name="MissingIssues"></a> <div class="category">Disabled Checks<div class="categorySeparator"></div> </div> 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. <br/><br/> <a name="AppLinksAutoVerifyError"></a> <div class="issue"> <div class="id">AppLinksAutoVerifyError<div class="issueSeparator"></div> </div> <div class="metadata">Disabled By: Default<br/> Priority: 5 / 10<br/> Category: Correctness</div> Severity: <span class="error">Error</span><div class="summary"> Explanation: App Links Auto Verification Failure.</div> <div class="explanation"> Ensures that app links are correctly set and associated with website. </div> <br/><div class="moreinfo">More info: <a href="https://g.co/appindexing/applinks">https://g.co/appindexing/applinks</a> </div><br/>To suppress this error, use the issue id "AppLinksAutoVerifyError" as explained in the <a href="#SuppressInfo">Suppressing Warnings and Errors</a> section.<br/> </div> <a name="AppLinksAutoVerifyWarning"></a> <div class="issue"> <div class="id">AppLinksAutoVerifyWarning<div class="issueSeparator"></div> </div> <div class="metadata">Disabled By: Default<br/> Priority: 5 / 10<br/> Category: Correctness</div> Severity: <span class="warning">Warning</span><div class="summary"> Explanation: Potential App Links Auto Verification Failure.</div> <div class="explanation"> Ensures that app links are correctly set and associated with website. </div> <br/><div class="moreinfo">More info: <a href="https://g.co/appindexing/applinks">https://g.co/appindexing/applinks</a> </div><br/>To suppress this error, use the issue id "AppLinksAutoVerifyWarning" as explained in the <a href="#SuppressInfo">Suppressing Warnings and Errors</a> section.<br/> </div> <a name="BackButton"></a> <div class="issue"> <div class="id">BackButton<div class="issueSeparator"></div> </div> <div class="metadata">Disabled By: Default<br/> Priority: 6 / 10<br/> Category: Usability</div> Severity: <span class="warning">Warning</span><div class="summary"> Explanation: Back button.</div> <div class="explanation"> According to the Android Design Guide,<br/> <br/> "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."<br/> 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. </div> <br/><div class="moreinfo">More info: <a href="http://developer.android.com/design/patterns/pure-android.html">http://developer.android.com/design/patterns/pure-android.html</a> </div><br/>To suppress this error, use the issue id "BackButton" as explained in the <a href="#SuppressInfo">Suppressing Warnings and Errors</a> section.<br/> </div> <a name="EasterEgg"></a> <div class="issue"> <div class="id">EasterEgg<div class="issueSeparator"></div> </div> <div class="metadata">Disabled By: Default<br/> Priority: 6 / 10<br/> Category: Security</div> Severity: <span class="warning">Warning</span><div class="summary"> Explanation: Code contains easter egg.</div> <div class="explanation"> 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. </div> <br/><div class="moreinfo">More info: </div><br/>To suppress this error, use the issue id "EasterEgg" as explained in the <a href="#SuppressInfo">Suppressing Warnings and Errors</a> section.<br/> </div> <a name="FieldGetter"></a> <div class="issue"> <div class="id">FieldGetter<div class="issueSeparator"></div> </div> <div class="metadata">Disabled By: Default<br/> Priority: 4 / 10<br/> Category: Performance</div> Severity: <span class="warning">Warning</span><div class="summary"> Explanation: Using getter instead of field.</div> <div class="explanation"> 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.<br/> <br/> <b>NOTE</b>: 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. </div> <br/><div class="moreinfo">More info: <a href="http://developer.android.com/guide/practices/design/performance.html#internal_get_set">http://developer.android.com/guide/practices/design/performance.html#internal_get_set</a> </div><br/>To suppress this error, use the issue id "FieldGetter" as explained in the <a href="#SuppressInfo">Suppressing Warnings and Errors</a> section.<br/> </div> <a name="GoogleAppIndexingApiWarning"></a> <div class="issue"> <div class="id">GoogleAppIndexingApiWarning<div class="issueSeparator"></div> </div> <div class="metadata">Note: This issue has an associated quickfix operation in Android Studio/IntelliJ <img alt="Fix" border="0" align="top" src="lint-results-debug_files/lint-run.png" /> <br> Disabled By: Default<br/> Priority: 5 / 10<br/> Category: Usability</div> Severity: <span class="warning">Warning</span><div class="summary"> Explanation: Missing support for Google App Indexing Api.</div> <div class="explanation"> Adds URLs to get your app into the Google index, to get installs and traffic to your app from Google Search. </div> <br/><div class="moreinfo">More info: <a href="https://g.co/AppIndexing/AndroidStudio">https://g.co/AppIndexing/AndroidStudio</a> </div><br/>To suppress this error, use the issue id "GoogleAppIndexingApiWarning" as explained in the <a href="#SuppressInfo">Suppressing Warnings and Errors</a> section.<br/> </div> <a name="IconExpectedSize"></a> <div class="issue"> <div class="id">IconExpectedSize<div class="issueSeparator"></div> </div> <div class="metadata">Disabled By: Default<br/> Priority: 5 / 10<br/> Category: Usability:Icons</div> Severity: <span class="warning">Warning</span><div class="summary"> Explanation: Icon has incorrect size.</div> <div class="explanation"> 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. </div> <br/><div class="moreinfo">More info: <a href="http://developer.android.com/design/style/iconography.html">http://developer.android.com/design/style/iconography.html</a> </div><br/>To suppress this error, use the issue id "IconExpectedSize" as explained in the <a href="#SuppressInfo">Suppressing Warnings and Errors</a> section.<br/> </div> <a name="LogConditional"></a> <div class="issue"> <div class="id">LogConditional<div class="issueSeparator"></div> </div> <div class="metadata">Disabled By: Default<br/> Priority: 5 / 10<br/> Category: Performance</div> Severity: <span class="warning">Warning</span><div class="summary"> Explanation: Unconditional Logging Calls.</div> <div class="explanation"> 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.<br/> <br/> If you <b>really</b> intend for the logging to be present in release mode, you can suppress this warning with a @SuppressLint annotation for the intentional logging calls. </div> <br/><div class="moreinfo">More info: </div><br/>To suppress this error, use the issue id "LogConditional" as explained in the <a href="#SuppressInfo">Suppressing Warnings and Errors</a> section.<br/> </div> <a name="MangledCRLF"></a> <div class="issue"> <div class="id">MangledCRLF<div class="issueSeparator"></div> </div> <div class="metadata">Note: This issue has an associated quickfix operation in Eclipse/ADT <img alt="Fix" border="0" align="top" src="lint-results-debug_files/lint-run.png" /> <br> Disabled By: Default<br/> Priority: 2 / 10<br/> Category: Correctness</div> Severity: <span class="error">Error</span><div class="summary"> Explanation: Mangled file line endings.</div> <div class="explanation"> On Windows, line endings are typically recorded as carriage return plus newline: \r\n.<br/> <br/> 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. </div> <br/><div class="moreinfo">More info: <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=375421">https://bugs.eclipse.org/bugs/show_bug.cgi?id=375421</a> </div><br/>To suppress this error, use the issue id "MangledCRLF" as explained in the <a href="#SuppressInfo">Suppressing Warnings and Errors</a> section.<br/> </div> <a name="NegativeMargin"></a> <div class="issue"> <div class="id">NegativeMargin<div class="issueSeparator"></div> </div> <div class="metadata">Disabled By: Default<br/> Priority: 4 / 10<br/> Category: Usability</div> Severity: <span class="warning">Warning</span><div class="summary"> Explanation: Negative Margins.</div> <div class="explanation"> 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. </div> <br/><div class="moreinfo">More info: </div><br/>To suppress this error, use the issue id "NegativeMargin" as explained in the <a href="#SuppressInfo">Suppressing Warnings and Errors</a> section.<br/> </div> <a name="NewerVersionAvailable"></a> <div class="issue"> <div class="id">NewerVersionAvailable<div class="issueSeparator"></div> </div> <div class="metadata">Note: This issue has an associated quickfix operation in Android Studio/IntelliJ <img alt="Fix" border="0" align="top" src="lint-results-debug_files/lint-run.png" /> <br> Disabled By: Default<br/> Priority: 4 / 10<br/> Category: Correctness</div> Severity: <span class="warning">Warning</span><div class="summary"> Explanation: Newer Library Versions Available.</div> <div class="explanation"> 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 <code>GradleDependency</code> 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 <b>much</b> slower. </div> <br/><div class="moreinfo">More info: </div><br/>To suppress this error, use the issue id "NewerVersionAvailable" as explained in the <a href="#SuppressInfo">Suppressing Warnings and Errors</a> section.<br/> </div> <a name="SelectableText"></a> <div class="issue"> <div class="id">SelectableText<div class="issueSeparator"></div> </div> <div class="metadata">Note: This issue has an associated quickfix operation in Android Studio/IntelliJ <img alt="Fix" border="0" align="top" src="lint-results-debug_files/lint-run.png" /> <br> Disabled By: Default<br/> Priority: 7 / 10<br/> Category: Usability</div> Severity: <span class="warning">Warning</span><div class="summary"> Explanation: Dynamic text should probably be selectable.</div> <div class="explanation"> If a <code><TextView></code> is used to display data, the user might want to copy that data and paste it elsewhere. To allow this, the <code><TextView></code> should specify <code>android:textIsSelectable="true"</code>.<br/> <br/> 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 <code>minSdkVersion</code>. </div> <br/><div class="moreinfo">More info: </div><br/>To suppress this error, use the issue id "SelectableText" as explained in the <a href="#SuppressInfo">Suppressing Warnings and Errors</a> section.<br/> </div> <a name="StopShip"></a> <div class="issue"> <div class="id">StopShip<div class="issueSeparator"></div> </div> <div class="metadata">Note: This issue has an associated quickfix operation in Android Studio/IntelliJ <img alt="Fix" border="0" align="top" src="lint-results-debug_files/lint-run.png" /> <br> Disabled By: Default<br/> Priority: 10 / 10<br/> Category: Correctness</div> Severity: <span class="warning">Warning</span><div class="summary"> Explanation: Code contains <code>STOPSHIP</code> marker.</div> <div class="explanation"> Using the comment <code>// STOPSHIP</code> 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. </div> <br/><div class="moreinfo">More info: </div><br/>To suppress this error, use the issue id "StopShip" as explained in the <a href="#SuppressInfo">Suppressing Warnings and Errors</a> section.<br/> </div> <a name="TypographyQuotes"></a> <div class="issue"> <div class="id">TypographyQuotes<div class="issueSeparator"></div> </div> <div class="metadata">Note: This issue has an associated quickfix operation in Android Studio/IntelliJ & Eclipse/ADT <img alt="Fix" border="0" align="top" src="lint-results-debug_files/lint-run.png" /> <br> Disabled By: Default<br/> Priority: 5 / 10<br/> Category: Usability:Typography</div> Severity: <span class="warning">Warning</span><div class="summary"> Explanation: Straight quotes can be replaced with curvy quotes.</div> <div class="explanation"> 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.<br/> <br/> Note that you should never use grave accents and apostrophes to quote, `like this'.<br/> <br/> (Also note that you should not use curvy quotes for code fragments.) </div> <br/><div class="moreinfo">More info: <a href="http://en.wikipedia.org/wiki/Quotation_mark">http://en.wikipedia.org/wiki/Quotation_mark</a> </div><br/>To suppress this error, use the issue id "TypographyQuotes" as explained in the <a href="#SuppressInfo">Suppressing Warnings and Errors</a> section.<br/> </div> <a name="UnusedIds"></a> <div class="issue"> <div class="id">UnusedIds<div class="issueSeparator"></div> </div> <div class="metadata">Disabled By: Default<br/> Priority: 1 / 10<br/> Category: Performance</div> Severity: <span class="warning">Warning</span><div class="summary"> Explanation: Unused id.</div> <div class="explanation"> 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. </div> <br/><div class="moreinfo">More info: </div><br/>To suppress this error, use the issue id "UnusedIds" as explained in the <a href="#SuppressInfo">Suppressing Warnings and Errors</a> section.<br/> </div> <a name="SuppressInfo"></a> <div class="category">Suppressing Warnings and Errors<div class="categorySeparator"></div> </div> Lint errors can be suppressed in a variety of ways:<br/> <br/> 1. With a <code>@SuppressLint</code> annotation in the Java code<br/> 2. With a <code>tools:ignore</code> attribute in the XML file<br/> 3. With ignore flags specified in the <code>build.gradle</code> file, as explained below<br/> 4. With a <code>lint.xml</code> configuration file in the project<br/> 5. With a <code>lint.xml</code> configuration file passed to lint via the --config flag<br/> 6. With the --ignore flag passed to lint.<br/> <br/> To suppress a lint warning with an annotation, add a <code>@SuppressLint("id")</code> 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 <code>"UnusedResources"</code> or <code>{"UnusedResources","UnusedIds"}</code>, or it can be <code>"all"</code> to suppress all lint warnings in the given scope.<br/> <br/> To suppress a lint warning in an XML file, add a <code>tools:ignore="id"</code> 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 <code>xmlns:android</code> declaration:<br/> <code>xmlns:tools="http://schemas.android.com/tools"</code><br/> <br/> To suppress a lint warning in a <code>build.gradle</code> file, add a section like this:<br/> <br/> android {<br/>     lintOptions {<br/>         disable 'TypographyFractions','TypographyQuotes'<br/>     }<br/> }<br/> <br/> Here we specify a comma separated list of issue id's after the disable command. You can also use <code>warning</code> or <code>error</code> instead of <code>disable</code> to change the severity of issues.<br/> <br/> To suppress lint warnings with a configuration XML file, create a file named <code>lint.xml</code> and place it at the root directory of the project in which it applies.<br/> <br/> The format of the <code>lint.xml</code> file is something like the following:<br/> <br/> <?xml version="1.0" encoding="UTF-8"?><br/> <lint><br/>     <br/>     <issue id="IconMissingDensityFolder" severity="ignore" /><br/> <br/>     <br/>     <issue id="ObsoleteLayoutParam"><br/>         <ignore path="res/layout/activation.xml" /><br/>         <ignore path="res/layout-xlarge/activation.xml" /><br/>     </issue><br/> <br/>     <br/>     <issue id="UselessLeaf"><br/>         <ignore path="res/layout/main.xml" /><br/>     </issue><br/> <br/>     <br/>     <issue id="HardcodedText" severity="error" /><br/> </lint><br/> <br/> To suppress lint checks from the command line, pass the --ignore flag with a comma separated list of ids to be suppressed, such as:<br/> <code>$ lint --ignore UnusedResources,UselessLeaf /my/project/path</code><br/> <br/> For more information, see <a href="http://g.co/androidstudio/suppressing-lint-warnings">http://g.co/androidstudio/suppressing-lint-warnings</a><br/> </body> </html>