+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Overview
+
+
+
+
+ | Correctness:Messages + | |
| 5 | error +MissingTranslation: Incomplete translation |
| Disabled Checks (279) + |
+
+
+
+
+
+ Incomplete translation
+
+
+
+
+
+
+../../src/main/res/values/arrays.xml:20: "
+format_for_exported_note" is not translated in "zh-CN" (Chinese: China), "zh-TW" (Chinese: Taiwan)+ 17 + 18 <resources> + 19 <!-- Backup format --> + 20 <string-array name="format_for_exported_note"> + 21 <item>-%s</item> <!-- format_folder_name --> + 22 <item>--%s</item> <!-- format_folder_note_date --> + 23 <item>--%s</item> <!-- format_note_date -->+ +../../src/main/res/values/strings.xml:39: "
file_path" is not translated in "zh-CN" (Chinese: China), "zh-TW" (Chinese: Taiwan)+ 36 <string name="note_link_web">Browse web</string> + 37 <string name="note_link_other">Open map</string> + 38 <!-- Text export file information --> + 39 <string name="file_path">/MIUI/notes/</string> + 40 <string name="file_name_txt_format">notes_%s.txt</string> + 41 <!-- notes list string --> + 42 <string name="format_folder_files_count">(%d)</string>+ +../../src/main/res/values/strings.xml:40: "
file_name_txt_format" is not translated in "zh-CN" (Chinese: China), "zh-TW" (Chinese: Taiwan)+ 37 <string name="note_link_other">Open map</string> + 38 <!-- Text export file information --> + 39 <string name="file_path">/MIUI/notes/</string> + 40 <string name="file_name_txt_format">notes_%s.txt</string> + 41 <!-- notes list string --> + 42 <string name="format_folder_files_count">(%d)</string> + 43 <string name="menu_create_folder">New Folder</string>+ +../../src/main/res/values/strings.xml:42: "
format_folder_files_count" is not translated in "zh-CN" (Chinese: China), "zh-TW" (Chinese: Taiwan)+ 39 <string name="file_path">/MIUI/notes/</string> + 40 <string name="file_name_txt_format">notes_%s.txt</string> + 41 <!-- notes list string --> + 42 <string name="format_folder_files_count">(%d)</string> + 43 <string name="menu_create_folder">New Folder</string> + 44 <string name="menu_export_text">Export text</string> + 45 <string name="menu_sync">Sync</string>+ +../../src/main/res/values/strings.xml:104: "
preferences_last_sync_time_format" is not translated in "zh-CN" (Chinese: China), "zh-TW" (Chinese: Taiwan)+ 101 <string name="preferences_account_title">Sync account</string> + 102 <string name="preferences_account_summary">Sync notes with google task</string> + 103 <string name="preferences_last_sync_time">Last sync time %1$s</string> + 104 <string name="preferences_last_sync_time_format">yyyy-MM-dd hh:mm:ss</string> + 105 <string name="preferences_add_account">Add account</string> + 106 <string name="preferences_menu_change_account">Change sync account</string> + 107 <string name="preferences_menu_remove_account">Remove sync account</string>+ +
+If an application has more than one locale, then all the strings declared in one language should also be translated in all other languages.
+
+If the string should not be translated, you can add the attribute
+
+By default this detector allows regions of a language to just provide a subset of the strings and fall back to the standard language strings. You can require all regions to provide a full translation by setting the environment variable
+
+You can tell lint (and other tools) which language is the default language in your
To suppress this error, use the issue id "MissingTranslation" as explained in the Suppressing Warnings and Errors section.
+
++
+If the string should not be translated, you can add the attribute
translatable="false" on the <string> element, or you can define all your non-translatable strings in a resource file called donottranslate.xml. Or, you can ignore the issue with a tools:ignore="MissingTranslation" attribute.+
+By default this detector allows regions of a language to just provide a subset of the strings and fall back to the standard language strings. You can require all regions to provide a full translation by setting the environment variable
ANDROID_LINT_COMPLETE_REGIONS.+
+You can tell lint (and other tools) which language is the default language in your
res/values/ folder by specifying tools:locale="languageCode" for the root <resources> element in your resource file. (The tools prefix refers to the namespace declaration http://schemas.android.com/tools.)To suppress this error, use the issue id "MissingTranslation" as explained in the Suppressing Warnings and Errors section.
+
+
+ MissingTranslation
+
+
+ Messages
+
+
+ Correctness
+
+
+ Fatal
+
+
+ Priority 8/10
+
+
+
+
+
+
+
+
+ Disabled Checks
+
+One or more 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.
+
+
+AccidentalOctal
+
+Disabled By: Project lint.xml file
+
++
+In Groovy, an integer literal that starts with a leading 0 will be interpreted as an octal number. That is usually (always?) an accident and can lead to subtle bugs, for example when used in the
To suppress this error, use the issue id "AccidentalOctal" as explained in the Suppressing Warnings and Errors section.
+
+versionCode of an app.To suppress this error, use the issue id "AccidentalOctal" as explained in the Suppressing Warnings and Errors section.
+
+
+AdapterViewChildren
+
+Disabled By: Project lint.xml file
+
++
+AdapterViews such as ListViews must be configured with data from Java code, such as a ListAdapter.
To suppress this error, use the issue id "AdapterViewChildren" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "AdapterViewChildren" as explained in the Suppressing Warnings and Errors section.
+
+
+AddJavascriptInterface
+
+Disabled By: Project lint.xml file
+
++
+For applications built for API levels below 17,
+
+WebView#addJavascriptInterface presents a security hazard as JavaScript on the target web page has the ability to use reflection to access the injected object's public fields and thus manipulate the host application in unintended ways.More info: https://labs.mwrinfosecurity.com/blog/2013/09/24/webview-addjavascriptinterface-remote-code-execution/
+
To suppress this error, use the issue id "AddJavascriptInterface" as explained in the Suppressing Warnings and Errors section.+
+
+AllCaps
+
+Disabled By: Project lint.xml file
+
++
+The textAllCaps text transform will end up calling
To suppress this error, use the issue id "AllCaps" as explained in the Suppressing Warnings and Errors section.
+
+toString on the CharSequence, which has the net effect of removing any markup such as <b>. This check looks for usages of strings containing markup that also specify textAllCaps=true.To suppress this error, use the issue id "AllCaps" as explained in the Suppressing Warnings and Errors section.
+
+
+AllowAllHostnameVerifier
+
+Disabled By: Project lint.xml file
+
++
+This check looks for use of HostnameVerifier implementations whose
To suppress this error, use the issue id "AllowAllHostnameVerifier" as explained in the Suppressing Warnings and Errors section.
+
+verify method always returns true (thus trusting any hostname) which could result in insecure network traffic caused by trusting arbitrary hostnames in TLS/SSL certificates presented by peers.To suppress this error, use the issue id "AllowAllHostnameVerifier" as explained in the Suppressing Warnings and Errors section.
+
+
+AllowBackup
+
+Disabled By: Project lint.xml file
+
++
+The
+
+By default, this flag is set to
+
+This may have security consequences for an application.
+
+Setting
+
+To fix this warning, decide whether your application should support backup, and explicitly set
+
+If not set to false, and if targeting API 23 or later, lint will also warn that you should set
+To suppress this error, use the issue id "AllowBackup" as explained in the Suppressing Warnings and Errors section.
+
+allowBackup attribute determines if an application's data can be backed up and restored. It is documented at http://developer.android.com/reference/android/R.attr.html#allowBackup+
+By default, this flag is set to
true. When this flag is set to true, application data can be backed up and restored by the user using adb backup and adb restore.+
+This may have security consequences for an application.
adb backup allows users who have enabled USB debugging to copy application data off of the device. Once backed up, all application data can be read by the user. adb restore allows creation of application data from a source specified by the user. Following a restore, applications should not assume that the data, file permissions, and directory permissions were created by the application itself.+
+Setting
allowBackup="false" opts an application out of both backup and restore.+
+To fix this warning, decide whether your application should support backup, and explicitly set
android:allowBackup=(true|false)".+
+If not set to false, and if targeting API 23 or later, lint will also warn that you should set
android:fullBackupContent to configure auto backup.More info:
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.+To suppress this error, use the issue id "AllowBackup" as explained in the Suppressing Warnings and Errors section.
+
+
+AlwaysShowAction
+
+Disabled By: Project lint.xml file
+
++
+Using
+
+If
+
+This check looks for menu XML files that contain more than two
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "AlwaysShowAction" as explained in the Suppressing Warnings and Errors section.
+
+showAsAction="always" in menu XML, or MenuItem.SHOW_AS_ACTION_ALWAYS in Java code is usually a deviation from the user interface style guide.Use ifRoom or the corresponding MenuItem.SHOW_AS_ACTION_IF_ROOM instead.+
+If
always is used sparingly there are usually no problems and behavior is roughly equivalent to ifRoom but with preference over other ifRoom items. Using it more than twice in the same menu is a bad idea.+
+This check looks for menu XML files that contain more than two
always actions, or some always actions and no ifRoom actions. In Java code, it looks for projects that contain references to MenuItem.SHOW_AS_ACTION_ALWAYS and no references to MenuItem.SHOW_AS_ACTION_IF_ROOM.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "AlwaysShowAction" as explained in the Suppressing Warnings and Errors section.
+
+
+AnimatorKeep
+
+Disabled By: Project lint.xml file
+
++
+When you use property animators, properties can be accessed via reflection. Those methods should be annotated with @Keep to ensure that during release builds, the methods are not potentially treated as unused and removed, or treated as internal only and get renamed to something shorter.
+
+This check will also flag other potential reflection problems it encounters, such as a missing property, wrong argument types, etc.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "AnimatorKeep" as explained in the Suppressing Warnings and Errors section.
+
++
+This check will also flag other potential reflection problems it encounters, such as a missing property, wrong argument types, etc.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "AnimatorKeep" as explained in the Suppressing Warnings and Errors section.
+
+
+AppCompatCustomView
+
+Disabled By: Project lint.xml file
+
++
+In order to support features such as tinting, the appcompat library will automatically load special appcompat replacements for the builtin widgets. However, this does not work for your own custom views.
+
+Instead of extending the
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "AppCompatCustomView" as explained in the Suppressing Warnings and Errors section.
+
++
+Instead of extending the
android.widget classes directly, you should instead extend one of the delegate classes in android.support.v7.widget.AppCompat.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "AppCompatCustomView" as explained in the Suppressing Warnings and Errors section.
+
+
+AppCompatMethod
+
+Disabled By: Project lint.xml file
+
++
+When using the appcompat library, there are some methods you should be calling instead of the normal ones; for example,
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "AppCompatMethod" as explained in the Suppressing Warnings and Errors section.
+
+getSupportActionBar() instead of getActionBar(). This lint check looks for calls to the wrong method.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "AppCompatMethod" as explained in the Suppressing Warnings and Errors section.
+
+
+AppCompatResource
+
+Disabled By: Project lint.xml file
+
++
+When using the appcompat library, menu resources should refer to the
+
+Similarly, when not using the appcompat library, you should be using the
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "AppCompatResource" as explained in the Suppressing Warnings and Errors section.
+
+showAsAction (or actionViewClass, or actionProviderClass) in the app: namespace, not the android: namespace.+
+Similarly, when not using the appcompat library, you should be using the
android:showAsAction (or actionViewClass, or actionProviderClass) attribute.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "AppCompatResource" as explained in the Suppressing Warnings and Errors section.
+
+
+AppIndexingService
+
+Disabled By: Project lint.xml file
+
++
+Apps targeting Android 8.0 or higher can no longer rely on background services while listening for updates to the on-device index. Use a
+
+BroadcastReceiver for the UPDATE_INDEX intent to continue supporting indexing in your app.More info: https://firebase.google.com/docs/app-indexing/android/personal-content#add-a-broadcast-receiver-to-your-app
+
To suppress this error, use the issue id "AppIndexingService" as explained in the Suppressing Warnings and Errors section.+
+
+AppLinkUrlError
+
+Disabled By: Project lint.xml file
+
++
+Ensure the URL is supported by your app, to get installs and traffic to your app from Google Search.
+To suppress this error, use the issue id "AppLinkUrlError" as explained in the Suppressing Warnings and Errors section.
+
+More info: https://g.co/AppIndexing/AndroidStudio
+
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.+To suppress this error, use the issue id "AppLinkUrlError" as explained in the Suppressing Warnings and Errors section.
+
+
+AppLinksAutoVerifyError
+
+Disabled By: Default
+
++
+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
+
++
+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.+
+
+ApplySharedPref
+
+Disabled By: Project lint.xml file
+
++
+Consider using
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ApplySharedPref" as explained in the Suppressing Warnings and Errors section.
+
+apply() instead of commit on shared preferences. Whereas commit blocks and writes its data to persistent storage immediately, apply will handle it in the background.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ApplySharedPref" as explained in the Suppressing Warnings and Errors section.
+
+
+Assert
+
+Disabled By: Project lint.xml file
+
++
+Assertions are not checked at runtime. There are ways to request that they be used by Dalvik (
+
+For example, you can replace
+
+(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.)
To suppress this error, use the issue id "Assert" as explained in the Suppressing Warnings and Errors section.
+
+adb shell setprop debug.assert 1), but note that this is not implemented in ART (the newer runtime), and even in Dalvik 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.)
To suppress this error, use the issue id "Assert" as explained in the Suppressing Warnings and Errors section.
+
+
+AuthLeak
+
+Disabled By: Project lint.xml file
+
++
+Strings in java apps can be discovered by decompiling apps, this lint check looks for code which looks like it may contain an url with a username and password
To suppress this error, use the issue id "AuthLeak" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "AuthLeak" as explained in the Suppressing Warnings and Errors section.
+
+
+BackButton
+
+Disabled By: Default
+
++
+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.
+
++
+"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.
+
+
+BadHostnameVerifier
+
+Disabled By: Project lint.xml file
+
++
+This check looks for implementations of
To suppress this error, use the issue id "BadHostnameVerifier" as explained in the Suppressing Warnings and Errors section.
+
+HostnameVerifier whose verify method always returns true (thus trusting any hostname) which could result in insecure network traffic caused by trusting arbitrary hostnames in TLS/SSL certificates presented by peers.To suppress this error, use the issue id "BadHostnameVerifier" as explained in the Suppressing Warnings and Errors section.
+
+
+BatteryLife
+
+Disabled By: Project lint.xml file
+
++
+This issue flags code that either
+* negatively affects battery life, or
+* uses APIs that have recently changed behavior to prevent background tasks from consuming memory and battery excessively.
+
+Generally, you should be using
+
+For more details on how to update your code, please seehttp://developer.android.com/preview/features/background-optimization.html
To suppress this error, use the issue id "BatteryLife" as explained in the Suppressing Warnings and Errors section.
+
++* negatively affects battery life, or
+* uses APIs that have recently changed behavior to prevent background tasks from consuming memory and battery excessively.
+
+Generally, you should be using
JobScheduler or GcmNetworkManager instead.+
+For more details on how to update your code, please seehttp://developer.android.com/preview/features/background-optimization.html
To suppress this error, use the issue id "BatteryLife" as explained in the Suppressing Warnings and Errors section.
+
+
+ButtonCase
+
+Disabled By: Project lint.xml file
+
++
+The standard capitalization for OK/Cancel dialogs is "OK" and "Cancel". To ensure that your dialogs use the standard strings, you can use the resource strings @android:string/ok and @android:string/cancel.
To suppress this error, use the issue id "ButtonCase" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "ButtonCase" as explained in the Suppressing Warnings and Errors section.
+
+
+ButtonOrder
+
+Disabled By: Project lint.xml file
+
++
+According to the Android Design Guide,
+
+"Action buttons are typically Cancel and/or OK, with OK indicating the preferred or most likely action. However, if the options consist of specific actions such as Close or Wait rather than a confirmation or cancellation of the action described in the content, then all the buttons should be active verbs. As a rule, the dismissive action of a dialog is always on the left whereas the affirmative actions are on the right."
+
+This check looks for button bars and buttons which look like cancel buttons, and makes sure that these are on the left.
To suppress this error, use the issue id "ButtonOrder" as explained in the Suppressing Warnings and Errors section.
+
++
+"Action buttons are typically Cancel and/or OK, with OK indicating the preferred or most likely action. However, if the options consist of specific actions such as Close or Wait rather than a confirmation or cancellation of the action described in the content, then all the buttons should be active verbs. As a rule, the dismissive action of a dialog is always on the left whereas the affirmative actions are on the right."
+
+This check looks for button bars and buttons which look like cancel buttons, and makes sure that these are on the left.
To suppress this error, use the issue id "ButtonOrder" as explained in the Suppressing Warnings and Errors section.
+
+
+ButtonStyle
+
+Disabled By: Project lint.xml file
+
++
+Button bars typically use a borderless style for the buttons. Set the
To suppress this error, use the issue id "ButtonStyle" as explained in the Suppressing Warnings and Errors section.
+
+style="?android:attr/buttonBarButtonStyle" attribute on each of the buttons, and set style="?android:attr/buttonBarStyle" on the parent layoutTo suppress this error, use the issue id "ButtonStyle" as explained in the Suppressing Warnings and Errors section.
+
+
+ByteOrderMark
+
+Disabled By: Project lint.xml file
+
++
+Lint will flag any byte-order-mark (BOM) characters it finds in the middle of a file. Since we expect files to be encoded with UTF-8 (see the EnforceUTF8 issue), the BOM characters are not necessary, and they are not handled correctly by all tools. For example, if you have a BOM as part of a resource name in one particular translation, that name will not be considered identical to the base resource's name and the translation will not be used.
+To suppress this error, use the issue id "ByteOrderMark" as explained in the Suppressing Warnings and Errors section.
+
+More info: http://en.wikipedia.org/wiki/Byte_order_mark
+
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.+To suppress this error, use the issue id "ByteOrderMark" as explained in the Suppressing Warnings and Errors section.
+
+
+CheckResult
+
+Disabled By: Project lint.xml file
+
++
+Some methods have no side effects, an calling them without doing something without the result is suspicious.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "CheckResult" as explained in the Suppressing Warnings and Errors section.
+
+Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "CheckResult" as explained in the Suppressing Warnings and Errors section.
+
+
+ClickableViewAccessibility
+
+Disabled By: Project lint.xml file
+
++
+If a
To suppress this error, use the issue id "ClickableViewAccessibility" as explained in the Suppressing Warnings and Errors section.
+
+View that overrides onTouchEvent or uses an OnTouchListener does not also implement performClick and call it when clicks are detected, the View may not handle accessibility actions properly. Logic handling the click actions should ideally be placed in View#performClick as some accessibility services invoke performClick when a click action should occur.To suppress this error, use the issue id "ClickableViewAccessibility" as explained in the Suppressing Warnings and Errors section.
+
+
+CommitPrefEdits
+
+Disabled By: Project lint.xml file
+
++
+After calling
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "CommitPrefEdits" as explained in the Suppressing Warnings and Errors section.
+
+edit() on a SharedPreference, you must call commit() or apply() on the editor to save the results.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "CommitPrefEdits" as explained in the Suppressing Warnings and Errors section.
+
+
+CommitTransaction
+
+Disabled By: Project lint.xml file
+
++
+After creating a
To suppress this error, use the issue id "CommitTransaction" as explained in the Suppressing Warnings and Errors section.
+
+FragmentTransaction, you typically need to commit it as wellTo suppress this error, use the issue id "CommitTransaction" as explained in the Suppressing Warnings and Errors section.
+
+
+ContentDescription
+
+Disabled By: Project lint.xml file
+
++
+Non-textual widgets like ImageViews and ImageButtons should use the
+
+Note that elements in application screens that are purely decorative and do not provide any content or enable a user action should not have accessibility content descriptions. In this case, just suppress the lint warning with a tools:ignore="ContentDescription" attribute.
+
+Note that for text fields, you should not set both the
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ContentDescription" as explained in the Suppressing Warnings and Errors section.
+
+contentDescription attribute to specify a textual description of the widget such that screen readers and other accessibility tools can adequately describe the user interface.+
+Note that elements in application screens that are purely decorative and do not provide any content or enable a user action should not have accessibility content descriptions. In this case, just suppress the lint warning with a tools:ignore="ContentDescription" attribute.
+
+Note that for text fields, you should not set both the
hint and the contentDescription attributes since the hint will never be shown. Just set the hint. See http://developer.android.com/guide/topics/ui/accessibility/checklist.html#special-cases.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ContentDescription" as explained in the Suppressing Warnings and Errors section.
+
+
+ConvertToWebp
+
+Disabled By: Default
+
++
+The WebP format is typically more compact than PNG and JPEG. As of Android 4.2.1 it supports transparency and lossless conversion as well. Note that there is a quickfix in the IDE which lets you perform conversion.
+
+Launcher icons must be in the PNG format.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ConvertToWebp" as explained in the Suppressing Warnings and Errors section.
+
++
+Launcher icons must be in the PNG format.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ConvertToWebp" as explained in the Suppressing Warnings and Errors section.
+
+
+CustomViewStyleable
+
+Disabled By: Project lint.xml file
+
++
+The convention for custom views is to use a
+
+(Similarly, layout parameter classes should use the suffix
To suppress this error, use the issue id "CustomViewStyleable" as explained in the Suppressing Warnings and Errors section.
+
+declare-styleable whose name matches the custom view class name. The IDE relies on this convention such that for example code completion can be offered for attributes in a custom view in layout XML resource files.+
+(Similarly, layout parameter classes should use the suffix
_Layout.)To suppress this error, use the issue id "CustomViewStyleable" as explained in the Suppressing Warnings and Errors section.
+
+
+CutPasteId
+
+Disabled By: Project lint.xml file
+
++
+This lint check looks for cases where you have cut & pasted calls to
To suppress this error, use the issue id "CutPasteId" as explained in the Suppressing Warnings and Errors section.
+
+findViewById but have forgotten to update the R.id field. It's possible that your code is simply (redundantly) looking up the field repeatedly, but lint cannot distinguish that from a case where you for example want to initialize fields prev and next and you cut & pasted findViewById(R.id.prev) and forgot to update the second initialization to R.id.next.To suppress this error, use the issue id "CutPasteId" as explained in the Suppressing Warnings and Errors section.
+
+
+DalvikOverride
+
+Disabled By: Project lint.xml file
+
++
+The Android virtual machine will treat a package private method in one class as overriding a package private method in its super class, even if they are in separate packages. This may be surprising, but for compatibility reasons the behavior has not been changed (yet).
+
+If you really did intend for this method to override the other, make the method
+
+If you did not intend the override, consider making the method private, or changing its name or signature.
To suppress this error, use the issue id "DalvikOverride" as explained in the Suppressing Warnings and Errors section.
+
++
+If you really did intend for this method to override the other, make the method
protected instead.+
+If you did not intend the override, consider making the method private, or changing its name or signature.
To suppress this error, use the issue id "DalvikOverride" as explained in the Suppressing Warnings and Errors section.
+
+
+DefaultLocale
+
+Disabled By: Project lint.xml file
+
++
+Calling
+
+If you want the methods to just perform ASCII replacement, for example to convert an enum name, call
To suppress this error, use the issue id "DefaultLocale" as explained in the Suppressing Warnings and Errors section.
+
+String#toLowerCase() or #toUpperCase() without specifying an explicit locale is a common source of bugs. The reason for that is that those methods will use the current locale on the user's device, and even though the code appears to work correctly when you are developing the app, it will fail in some locales. For example, in the Turkish locale, the uppercase replacement for i is not I.+
+If you want the methods to just perform ASCII replacement, for example to convert an enum name, call
String#toUpperCase(Locale.US) instead. If you really want to use the current locale, call String#toUpperCase(Locale.getDefault()) instead.To suppress this error, use the issue id "DefaultLocale" as explained in the Suppressing Warnings and Errors section.
+
+
+Deprecated
+
+Disabled By: Project lint.xml file
+
++
+Deprecated views, attributes and so on are deprecated because there is a better way to do something. Do it that new way. You've been warned.
To suppress this error, use the issue id "Deprecated" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "Deprecated" as explained in the Suppressing Warnings and Errors section.
+
+
+DevModeObsolete
+
+Disabled By: Project lint.xml file
+
++
+In the past, our documentation recommended creating a
+
+That workaround is no longer necessary, and it has some serious downsides, such as breaking API access checking (since the true
+
+In recent versions of the IDE and the Gradle plugin, the IDE automatically passes the API level of the connected device used for deployment, and if that device is at least API 21, then multidexing is automatically turned on, meaning that you get the same speed benefits as the
To suppress this error, use the issue id "DevModeObsolete" as explained in the Suppressing Warnings and Errors section.
+
+dev product flavor with has a minSdkVersion of 21, in order to enable multidexing to speed up builds significantly during development.+
+That workaround is no longer necessary, and it has some serious downsides, such as breaking API access checking (since the true
minSdkVersion is no longer known).+
+In recent versions of the IDE and the Gradle plugin, the IDE automatically passes the API level of the connected device used for deployment, and if that device is at least API 21, then multidexing is automatically turned on, meaning that you get the same speed benefits as the
dev product flavor but without the downsides.To suppress this error, use the issue id "DevModeObsolete" as explained in the Suppressing Warnings and Errors section.
+
+
+DeviceAdmin
+
+Disabled By: Project lint.xml file
+
++
+If you register a broadcast receiver which acts as a device admin, you must also register an
+
+To do this, add
+
+
+
+to your
To suppress this error, use the issue id "DeviceAdmin" as explained in the Suppressing Warnings and Errors section.
+
+<intent-filter> for the action android.app.action.DEVICE_ADMIN_ENABLED, without any <data>, such that the device admin can be activated/deactivated.+
+To do this, add
+
<intent-filter>+
<action android:name="android.app.action.DEVICE_ADMIN_ENABLED" />+
</intent-filter>+to your
<receiver>.To suppress this error, use the issue id "DeviceAdmin" as explained in the Suppressing Warnings and Errors section.
+
+
+DisableBaselineAlignment
+
+Disabled By: Project lint.xml file
+
++
+When a LinearLayout is used to distribute the space proportionally between nested layouts, the baseline alignment property should be turned off to make the layout computation faster.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "DisableBaselineAlignment" as explained in the Suppressing Warnings and Errors section.
+
+Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "DisableBaselineAlignment" as explained in the Suppressing Warnings and Errors section.
+
+
+DrawAllocation
+
+Disabled By: Project lint.xml file
+
++
+You should avoid allocating objects during a drawing or layout operation. These are called frequently, so a smooth UI can be interrupted by garbage collection pauses caused by the object allocations.
+
+The way this is generally handled is to allocate the needed objects up front and to reuse them for each drawing operation.
+
+Some methods allocate memory on your behalf (such as
To suppress this error, use the issue id "DrawAllocation" as explained in the Suppressing Warnings and Errors section.
+
++
+The way this is generally handled is to allocate the needed objects up front and to reuse them for each drawing operation.
+
+Some methods allocate memory on your behalf (such as
Bitmap.create), and these should be handled in the same way.To suppress this error, use the issue id "DrawAllocation" as explained in the Suppressing Warnings and Errors section.
+
+
+DuplicateDefinition
+
+Disabled By: Project lint.xml file
+
++
+You can define a resource multiple times in different resource folders; that's how string translations are done, for example. However, defining the same resource more than once in the same resource folder is likely an error, for example attempting to add a new resource without realizing that the name is already used, and so on.
To suppress this error, use the issue id "DuplicateDefinition" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "DuplicateDefinition" as explained in the Suppressing Warnings and Errors section.
+
+
+DuplicateDivider
+
+Disabled By: Project lint.xml file
+
++
+Older versions of the RecyclerView library did not include a divider decorator, but one was provided as a sample in the support demos. This divider class has been widely copy/pasted into various projects.
+
+In recent versions of the support library, the divider decorator is now included, so you can replace custom copies with the "built-in" version,
To suppress this error, use the issue id "DuplicateDivider" as explained in the Suppressing Warnings and Errors section.
+
++
+In recent versions of the support library, the divider decorator is now included, so you can replace custom copies with the "built-in" version,
android.support.v7.widget.DividerItemDecoration.To suppress this error, use the issue id "DuplicateDivider" as explained in the Suppressing Warnings and Errors section.
+
+
+DuplicateIncludedIds
+
+Disabled By: Project lint.xml file
+
++
+It's okay for two independent layouts to use the same ids. However, if layouts are combined with include tags, then the id's need to be unique within any chain of included layouts, or
To suppress this error, use the issue id "DuplicateIncludedIds" as explained in the Suppressing Warnings and Errors section.
+
+Activity#findViewById() can return an unexpected view.To suppress this error, use the issue id "DuplicateIncludedIds" as explained in the Suppressing Warnings and Errors section.
+
+
+DuplicateUsesFeature
+
+Disabled By: Project lint.xml file
+
++
+A given feature should only be declared once in the manifest.
To suppress this error, use the issue id "DuplicateUsesFeature" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "DuplicateUsesFeature" as explained in the Suppressing Warnings and Errors section.
+
+
+EasterEgg
+
+Disabled By: Default
+
++
+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.
To suppress this error, use the issue id "EasterEgg" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "EasterEgg" as explained in the Suppressing Warnings and Errors section.
+
+
+EllipsizeMaxLines
+
+Disabled By: Project lint.xml file
+
++
+Combining
+To suppress this error, use the issue id "EllipsizeMaxLines" as explained in the Suppressing Warnings and Errors section.
+
+ellipsize and maxLines=1 can lead to crashes on some devices. Earlier versions of lint recommended replacing singleLine=true with maxLines=1 but that should not be done when using ellipsize.More info: https://issuetracker.google.com/issues/36950033
+
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.+To suppress this error, use the issue id "EllipsizeMaxLines" as explained in the Suppressing Warnings and Errors section.
+
+
+ExifInterface
+
+Disabled By: Project lint.xml file
+
++
+The
To suppress this error, use the issue id "ExifInterface" as explained in the Suppressing Warnings and Errors section.
+
+android.media.ExifInterface implementation has some known security bugs in older versions of Android. There is a new implementation available of this library in the support library, which is preferable.To suppress this error, use the issue id "ExifInterface" as explained in the Suppressing Warnings and Errors section.
+
+
+ExportedContentProvider
+
+Disabled By: Project lint.xml file
+
++
+Content providers are exported by default and any application on the system can potentially use them to read and write data. If the content provider provides access to sensitive data, it should be protected by specifying
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ExportedContentProvider" as explained in the Suppressing Warnings and Errors section.
+
+export=false in the manifest or by protecting it with a permission that can be granted to other applications.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ExportedContentProvider" as explained in the Suppressing Warnings and Errors section.
+
+
+ExportedPreferenceActivity
+
+Disabled By: Project lint.xml file
+
++
+Fragment injection gives anyone who can send your PreferenceActivity an intent the ability to load any fragment, with any arguments, in your process.
To suppress this error, use the issue id "ExportedPreferenceActivity" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "ExportedPreferenceActivity" as explained in the Suppressing Warnings and Errors section.
+
+
+ExportedReceiver
+
+Disabled By: Project lint.xml file
+
++
+Exported receivers (receivers which either set
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ExportedReceiver" as explained in the Suppressing Warnings and Errors section.
+
+exported=true or contain an intent-filter and do not specify exported=false) should define a permission that an entity must have in order to launch the receiver or bind to it. Without this, any application can use this receiver.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ExportedReceiver" as explained in the Suppressing Warnings and Errors section.
+
+
+ExportedService
+
+Disabled By: Project lint.xml file
+
++
+Exported services (services which either set
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ExportedService" as explained in the Suppressing Warnings and Errors section.
+
+exported=true or contain an intent-filter and do not specify exported=false) should define a permission that an entity must have in order to launch the service or bind to it. Without this, any application can use this service.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ExportedService" as explained in the Suppressing Warnings and Errors section.
+
+
+ExtraText
+
+Disabled By: Project lint.xml file
+
++
+Layout resource files should only contain elements and attributes. Any XML text content found in the file is likely accidental (and potentially dangerous if the text resembles XML and the developer believes the text to be functional)
To suppress this error, use the issue id "ExtraText" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "ExtraText" as explained in the Suppressing Warnings and Errors section.
+
+
+FieldGetter
+
+Disabled By: Default
+
++
+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.
+
++
+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.
+
+
+FindViewByIdCast
+
+Disabled By: Project lint.xml file
+
++
+In Android O, the
+
+However, due to language changes between Java 7 and 8, this change may cause code to not compile without explicit casts. This lint check looks for these scenarios and suggests casts to be added now such that the code will continue to compile if the language level is updated to 1.8.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "FindViewByIdCast" as explained in the Suppressing Warnings and Errors section.
+
+findViewById signature switched to using generics, which means that most of the time you can leave out explicit casts and just assign the result of the findViewById call to variables of specific view classes.+
+However, due to language changes between Java 7 and 8, this change may cause code to not compile without explicit casts. This lint check looks for these scenarios and suggests casts to be added now such that the code will continue to compile if the language level is updated to 1.8.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "FindViewByIdCast" as explained in the Suppressing Warnings and Errors section.
+
+
+FloatMath
+
+Disabled By: Project lint.xml file
+
++
+In older versions of Android, using
To suppress this error, use the issue id "FloatMath" as explained in the Suppressing Warnings and Errors section.
+
+android.util.FloatMath was recommended for performance reasons when operating on floats. However, on modern hardware doubles are just as fast as float (though they take more memory), and in recent versions of Android, FloatMath is actually slower than using java.lang.Math due to the way the JIT optimizes java.lang.Math. Therefore, you should use Math instead of FloatMath if you are only targeting Froyo and above.To suppress this error, use the issue id "FloatMath" as explained in the Suppressing Warnings and Errors section.
+
+
+FontValidationError
+
+Disabled By: Project lint.xml file
+
++
+Look for problems in various font files.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "FontValidationError" as explained in the Suppressing Warnings and Errors section.
+
+Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "FontValidationError" as explained in the Suppressing Warnings and Errors section.
+
+
+FontValidationWarning
+
+Disabled By: Project lint.xml file
+
++
+Look for problems in various font files.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "FontValidationWarning" as explained in the Suppressing Warnings and Errors section.
+
+Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "FontValidationWarning" as explained in the Suppressing Warnings and Errors section.
+
+
+GetContentDescriptionOverride
+
+Disabled By: Project lint.xml file
+
++
+Overriding
To suppress this error, use the issue id "GetContentDescriptionOverride" as explained in the Suppressing Warnings and Errors section.
+
+getContentDescription() may prevent some accessibility services from properly navigating content exposed by your view. Instead, call setContentDescription() when the content description needs to be changed.To suppress this error, use the issue id "GetContentDescriptionOverride" as explained in the Suppressing Warnings and Errors section.
+
+
+GetInstance
+
+Disabled By: Project lint.xml file
+
++
+
To suppress this error, use the issue id "GetInstance" as explained in the Suppressing Warnings and Errors section.
+
+Cipher#getInstance should not be called with ECB as the cipher mode or without setting the cipher mode because the default mode on android is ECB, which is insecure.To suppress this error, use the issue id "GetInstance" as explained in the Suppressing Warnings and Errors section.
+
+
+GetLocales
+
+Disabled By: Project lint.xml file
+
++
+TODO
To suppress this error, use the issue id "GetLocales" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "GetLocales" as explained in the Suppressing Warnings and Errors section.
+
+
+GifUsage
+
+Disabled By: Project lint.xml file
+
++
+The
To suppress this error, use the issue id "GifUsage" as explained in the Suppressing Warnings and Errors section.
+
+.gif file format is discouraged. Consider using .png (preferred) or .jpg (acceptable) instead.To suppress this error, use the issue id "GifUsage" as explained in the Suppressing Warnings and Errors section.
+
+
+GoogleAppIndexingApiWarning
+
+Disabled By: Default
+
++
+Adds URLs to get your app into the Google index, to get installs and traffic to your app from Google Search.
+To suppress this error, use the issue id "GoogleAppIndexingApiWarning" as explained in the Suppressing Warnings and Errors section.
+
+More info: https://g.co/AppIndexing/AndroidStudio
+
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.+To suppress this error, use the issue id "GoogleAppIndexingApiWarning" as explained in the Suppressing Warnings and Errors section.
+
+
+GoogleAppIndexingWarning
+
+Disabled By: Project lint.xml file
+
++
+Adds URLs to get your app into the Google index, to get installs and traffic to your app from Google Search.
+To suppress this error, use the issue id "GoogleAppIndexingWarning" as explained in the Suppressing Warnings and Errors section.
+
+More info: https://g.co/AppIndexing/AndroidStudio
+
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.+To suppress this error, use the issue id "GoogleAppIndexingWarning" as explained in the Suppressing Warnings and Errors section.
+
+
+GradleDependency
+
+Disabled By: Project lint.xml file
+
++
+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.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "GradleDependency" as explained in the Suppressing Warnings and Errors section.
+
+Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "GradleDependency" as explained in the Suppressing Warnings and Errors section.
+
+
+GradleDeprecated
+
+Disabled By: Project lint.xml file
+
++
+This detector looks for deprecated Gradle constructs which currently work but will likely stop working in a future update.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "GradleDeprecated" as explained in the Suppressing Warnings and Errors section.
+
+Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "GradleDeprecated" as explained in the Suppressing Warnings and Errors section.
+
+
+GradleDynamicVersion
+
+Disabled By: Project lint.xml file
+
++
+Using
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "GradleDynamicVersion" as explained in the Suppressing Warnings and Errors section.
+
++ 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.)Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "GradleDynamicVersion" as explained in the Suppressing Warnings and Errors section.
+
+
+GradleGetter
+
+Disabled By: Project lint.xml file
+
++
+Gradle will let you replace specific constants in your build scripts with method calls, so you can for example dynamically compute a version string based on your current version control revision number, rather than hardcoding a number.
+
+When computing a version name, it's tempting to for example call the method to do that
To suppress this error, use the issue id "GradleGetter" as explained in the Suppressing Warnings and Errors section.
+
++
+When computing a version name, it's tempting to for example call the method to do that
getVersionName. However, when you put that method call inside the defaultConfig block, you will actually be calling the Groovy getter for the versionName property instead. Therefore, you need to name your method something which does not conflict with the existing implicit getters. Consider using compute as a prefix instead of get.To suppress this error, use the issue id "GradleGetter" as explained in the Suppressing Warnings and Errors section.
+
+
+GradleIdeError
+
+Disabled By: Project lint.xml file
+
++
+Gradle is highly flexible, and there are things you can do in Gradle files which can make it hard or impossible for IDEs to properly handle the project. This lint check looks for constructs that potentially break IDE support.
To suppress this error, use the issue id "GradleIdeError" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "GradleIdeError" as explained in the Suppressing Warnings and Errors section.
+
+
+GradleOverrides
+
+Disabled By: Project lint.xml file
+
++
+The value of (for example)
To suppress this error, use the issue id "GradleOverrides" as explained in the Suppressing Warnings and Errors section.
+
+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.To suppress this error, use the issue id "GradleOverrides" as explained in the Suppressing Warnings and Errors section.
+
+
+GradlePath
+
+Disabled By: Project lint.xml file
+
++
+Gradle build scripts are meant to be cross platform, so file paths use Unix-style path separators (a forward slash) rather than Windows path separators (a backslash). Similarly, to keep projects portable and repeatable, avoid using absolute paths on the system; keep files within the project instead. To share code between projects, consider creating an android-library and an AAR dependency
To suppress this error, use the issue id "GradlePath" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "GradlePath" as explained in the Suppressing Warnings and Errors section.
+
+
+GradlePluginVersion
+
+Disabled By: Project lint.xml file
+
++
+Not all versions of the Android Gradle plugin are compatible with all versions of the SDK. If you update your tools, or if you are trying to open a project that was built with an old version of the tools, you may need to update your plugin version number.
To suppress this error, use the issue id "GradlePluginVersion" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "GradlePluginVersion" as explained in the Suppressing Warnings and Errors section.
+
+
+GrantAllUris
+
+Disabled By: Project lint.xml file
+
++
+The
To suppress this error, use the issue id "GrantAllUris" as explained in the Suppressing Warnings and Errors section.
+
+<grant-uri-permission> element allows specific paths to be shared. This detector checks for a path URL of just '/' (everything), which is probably not what you want; you should limit access to a subset.To suppress this error, use the issue id "GrantAllUris" as explained in the Suppressing Warnings and Errors section.
+
+
+HalfFloat
+
+Disabled By: Project lint.xml file
+
++
+Half-precision floating point are stored in a short data type, and should be manipulated using the
To suppress this error, use the issue id "HalfFloat" as explained in the Suppressing Warnings and Errors section.
+
+android.util.Half class. This check flags usages where it appears that these values are used incorrectly.To suppress this error, use the issue id "HalfFloat" as explained in the Suppressing Warnings and Errors section.
+
+
+HandlerLeak
+
+Disabled By: Project lint.xml file
+
++
+Since this Handler is declared as an inner class, it may prevent the outer class from being garbage collected. If the Handler is using a Looper or MessageQueue for a thread other than the main thread, then there is no issue. If the Handler is using the Looper or MessageQueue of the main thread, you need to fix your Handler declaration, as follows: Declare the Handler as a static class; In the outer class, instantiate a WeakReference to the outer class and pass this object to your Handler when you instantiate the Handler; Make all references to members of the outer class using the WeakReference object.
To suppress this error, use the issue id "HandlerLeak" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "HandlerLeak" as explained in the Suppressing Warnings and Errors section.
+
+
+HardcodedText
+
+Disabled By: Project lint.xml file
+
++
+Hardcoding text attributes directly in layout files is bad for several reasons:
+
+* When creating configuration variations (for example for landscape or portrait)you have to repeat the actual text (and keep it up to date when making changes)
+
+* The application cannot be translated to other languages by just adding new translations for existing string resources.
+
+There are quickfixes to automatically extract this hardcoded string into a resource lookup.
To suppress this error, use the issue id "HardcodedText" as explained in the Suppressing Warnings and Errors section.
+
++
+* When creating configuration variations (for example for landscape or portrait)you have to repeat the actual text (and keep it up to date when making changes)
+
+* The application cannot be translated to other languages by just adding new translations for existing string resources.
+
+There are quickfixes to automatically extract this hardcoded string into a resource lookup.
To suppress this error, use the issue id "HardcodedText" as explained in the Suppressing Warnings and Errors section.
+
+
+HardwareIds
+
+Disabled By: Project lint.xml file
+
++
+Using these device identifiers is not recommended other than for high value fraud prevention and advanced telephony use-cases. For advertising use-cases, use
To suppress this error, use the issue id "HardwareIds" as explained in the Suppressing Warnings and Errors section.
+
+AdvertisingIdClient$Info#getId and for analytics, use InstanceId#getId.To suppress this error, use the issue id "HardwareIds" as explained in the Suppressing Warnings and Errors section.
+
+
+HighAppVersionCode
+
+Disabled By: Project lint.xml file
+
++
+The declared
To suppress this error, use the issue id "HighAppVersionCode" as explained in the Suppressing Warnings and Errors section.
+
+versionCode is an Integer. Ensure that the version number is not close to the limit. It is recommended to monotonically increase this number each minor or major release of the app. Note that updating an app with a versionCode over Integer.MAX_VALUE is not possible.To suppress this error, use the issue id "HighAppVersionCode" as explained in the Suppressing Warnings and Errors section.
+
+
+IconColors
+
+Disabled By: Project lint.xml file
+
++
+Notification icons and Action Bar icons should only white and shades of gray. See the Android Design Guide for more details. Note that the way Lint decides whether an icon is an action bar icon or a notification icon is based on the filename prefix:
To suppress this error, use the issue id "IconColors" as explained in the Suppressing Warnings and Errors section.
+
+ic_menu_ for action bar icons, ic_stat_ for notification icons etc. These correspond to the naming conventions documented in http://developer.android.com/guide/practices/ui_guidelines/icon_design.htmlTo suppress this error, use the issue id "IconColors" as explained in the Suppressing Warnings and Errors section.
+
+
+IconDensities
+
+Disabled By: Project lint.xml file
+
++
+Icons will look best if a custom version is provided for each of the major screen density classes (low, medium, high, extra high). This lint check identifies icons which do not have complete coverage across the densities.
+
+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
To suppress this error, use the issue id "IconDensities" as explained in the Suppressing Warnings and Errors section.
+
++
+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.htmlTo suppress this error, use the issue id "IconDensities" as explained in the Suppressing Warnings and Errors section.
+
+
+IconDipSize
+
+Disabled By: Project lint.xml file
+
++
+Checks the all icons which are provided in multiple densities, all compute to roughly the same density-independent pixel (
To suppress this error, use the issue id "IconDipSize" as explained in the Suppressing Warnings and Errors section.
+
+dip) size. This catches errors where images are either placed in the wrong folder, or icons are changed to new sizes but some folders are forgotten.To suppress this error, use the issue id "IconDipSize" as explained in the Suppressing Warnings and Errors section.
+
+
+IconDuplicates
+
+Disabled By: Project lint.xml file
+
++
+If an icon is repeated under different names, you can consolidate and just use one of the icons and delete the others to make your application smaller. However, duplicated icons usually are not intentional and can sometimes point to icons that were accidentally overwritten or accidentally not updated.
To suppress this error, use the issue id "IconDuplicates" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "IconDuplicates" as explained in the Suppressing Warnings and Errors section.
+
+
+IconDuplicatesConfig
+
+Disabled By: Project lint.xml file
+
++
+If an icon is provided under different configuration parameters such as
To suppress this error, use the issue id "IconDuplicatesConfig" as explained in the Suppressing Warnings and Errors section.
+
+drawable-hdpi or -v11, they should typically be different. This detector catches cases where the same icon is provided in different configuration folder which is usually not intentional.To suppress this error, use the issue id "IconDuplicatesConfig" as explained in the Suppressing Warnings and Errors section.
+
+
+IconExpectedSize
+
+Disabled By: Default
+
++
+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.
+
+To suppress this error, use the issue id "IconExpectedSize" as explained in the Suppressing Warnings and Errors section.
+
+
+IconExtension
+
+Disabled By: Project lint.xml file
+
++
+Ensures that icons have the correct file extension (e.g. a
To suppress this error, use the issue id "IconExtension" as explained in the Suppressing Warnings and Errors section.
+
+.png file is really in the PNG format and not for example a GIF file named .png).To suppress this error, use the issue id "IconExtension" as explained in the Suppressing Warnings and Errors section.
+
+
+IconLauncherShape
+
+Disabled By: Project lint.xml file
+
++
+According to the Android Design Guide (http://developer.android.com/design/style/iconography.html) your launcher icons should "use a distinct silhouette", a "three-dimensional, front view, with a slight perspective as if viewed from above, so that users perceive some depth."
+
+The unique silhouette implies that your launcher icon should not be a filled square.
To suppress this error, use the issue id "IconLauncherShape" as explained in the Suppressing Warnings and Errors section.
+
++
+The unique silhouette implies that your launcher icon should not be a filled square.
To suppress this error, use the issue id "IconLauncherShape" as explained in the Suppressing Warnings and Errors section.
+
+
+IconLocation
+
+Disabled By: Project lint.xml file
+
++
+The res/drawable folder is intended for density-independent graphics such as shapes defined in XML. For bitmaps, move it to
To suppress this error, use the issue id "IconLocation" as explained in the Suppressing Warnings and Errors section.
+
+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.To suppress this error, use the issue id "IconLocation" as explained in the Suppressing Warnings and Errors section.
+
+
+IconMissingDensityFolder
+
+Disabled By: Project lint.xml file
+
++
+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
+
+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
To suppress this error, use the issue id "IconMissingDensityFolder" as explained in the Suppressing Warnings and Errors section.
+
+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.htmlTo suppress this error, use the issue id "IconMissingDensityFolder" as explained in the Suppressing Warnings and Errors section.
+
+
+IconMixedNinePatch
+
+Disabled By: Project lint.xml file
+
++
+If you accidentally name two separate resources
To suppress this error, use the issue id "IconMixedNinePatch" as explained in the Suppressing Warnings and Errors section.
+
+file.png and file.9.png, the image file and the nine patch file will both map to the same drawable resource, @drawable/file, which is probably not what was intended.To suppress this error, use the issue id "IconMixedNinePatch" as explained in the Suppressing Warnings and Errors section.
+
+
+IconNoDpi
+
+Disabled By: Project lint.xml file
+
++
+Bitmaps that appear in
To suppress this error, use the issue id "IconNoDpi" as explained in the Suppressing Warnings and Errors section.
+
+drawable-nodpi folders will not be scaled by the Android framework. If a drawable resource of the same name appears both in a -nodpi folder as well as a dpi folder such as drawable-hdpi, then the behavior is ambiguous and probably not intentional. Delete one or the other, or use different names for the icons.To suppress this error, use the issue id "IconNoDpi" as explained in the Suppressing Warnings and Errors section.
+
+
+IconXmlAndPng
+
+Disabled By: Project lint.xml file
+
++
+If a drawable resource appears as an
To suppress this error, use the issue id "IconXmlAndPng" as explained in the Suppressing Warnings and Errors section.
+
+.xml file in the drawable/ folder, it's usually not intentional for it to also appear as a bitmap using the same name; generally you expect the drawable XML file to define states and each state has a corresponding drawable bitmap.To suppress this error, use the issue id "IconXmlAndPng" as explained in the Suppressing Warnings and Errors section.
+
+
+IllegalResourceRef
+
+Disabled By: Project lint.xml file
+
++
+For the
To suppress this error, use the issue id "IllegalResourceRef" as explained in the Suppressing Warnings and Errors section.
+
+versionCode attribute, you have to specify an actual integer literal; you cannot use an indirection with a @dimen/name resource. Similarly, the versionName attribute should be an actual string, not a string resource url.To suppress this error, use the issue id "IllegalResourceRef" as explained in the Suppressing Warnings and Errors section.
+
+
+ImpliedQuantity
+
+Disabled By: Project lint.xml file
+
++
+Plural strings should generally include a
+
+In these locales, it is usually an error to have a message which does not include a formatting argument (such as '%d'), since it will not be clear from the grammar what quantity the quantity string is describing.
To suppress this error, use the issue id "ImpliedQuantity" as explained in the Suppressing Warnings and Errors section.
+
+%s or %d formatting argument. In locales like English, the one quantity only applies to a single value, 1, but that's not true everywhere. For example, in Slovene, the one quantity will apply to 1, 101, 201, 301, and so on. Similarly, there are locales where multiple values match the zero and two quantities.+
+In these locales, it is usually an error to have a message which does not include a formatting argument (such as '%d'), since it will not be clear from the grammar what quantity the quantity string is describing.
To suppress this error, use the issue id "ImpliedQuantity" as explained in the Suppressing Warnings and Errors section.
+
+
+ImpliedTouchscreenHardware
+
+Disabled By: Project lint.xml file
+
++
+Apps require the
+
To suppress this error, use the issue id "ImpliedTouchscreenHardware" as explained in the Suppressing Warnings and Errors section.
+
+android.hardware.touchscreen feature by default. If you want your app to be available on TV, you must also explicitly declare that a touchscreen is not required as follows:+
<uses-feature android:name="android.hardware.touchscreen" android:required="false"/>To suppress this error, use the issue id "ImpliedTouchscreenHardware" as explained in the Suppressing Warnings and Errors section.
+
+
+InOrMmUsage
+
+Disabled By: Project lint.xml file
+
++
+Avoid using
+
+While it should work in principle, unfortunately many devices do not report the correct true physical density, which means that the dimension calculations won't work correctly. You are better off using
To suppress this error, use the issue id "InOrMmUsage" as explained in the Suppressing Warnings and Errors section.
+
+mm (millimeters) or in (inches) as the unit for dimensions.+
+While it should work in principle, unfortunately many devices do not report the correct true physical density, which means that the dimension calculations won't work correctly. You are better off using
dp (and for font sizes, sp).To suppress this error, use the issue id "InOrMmUsage" as explained in the Suppressing Warnings and Errors section.
+
+
+IncludeLayoutParam
+
+Disabled By: Project lint.xml file
+
++
+Layout parameters specified on an
+To suppress this error, use the issue id "IncludeLayoutParam" as explained in the Suppressing Warnings and Errors section.
+
+<include> tag will only be used if you also override layout_width and layout_height on the <include> tag; otherwise they will be ignored.More info: http://stackoverflow.com/questions/2631614/does-android-xml-layouts-include-tag-really-work
+
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.+To suppress this error, use the issue id "IncludeLayoutParam" as explained in the Suppressing Warnings and Errors section.
+
+
+IncompatibleMediaBrowserServiceCompatVersion
+
+Disabled By: Project lint.xml file
+
++
+
To suppress this error, use the issue id "IncompatibleMediaBrowserServiceCompatVersion" as explained in the Suppressing Warnings and Errors section.
+
+MediaBrowserServiceCompat from version 23.2.0 to 23.4.0 of the Support v4 Library used private APIs and will not be compatible with future versions of Android beyond Android N.Please upgrade to version 24.0.0 or higher of the Support Library.To suppress this error, use the issue id "IncompatibleMediaBrowserServiceCompatVersion" as explained in the Suppressing Warnings and Errors section.
+
+
+InconsistentArrays
+
+Disabled By: Project lint.xml file
+
++
+When an array is translated in a different locale, it should normally have the same number of elements as the original array. When adding or removing elements to an array, it is easy to forget to update all the locales, and this lint warning finds inconsistencies like these.
+
+Note however that there may be cases where you really want to declare a different number of array items in each configuration (for example where the array represents available options, and those options differ for different layout orientations and so on), so use your own judgement to decide if this is really an error.
+
+You can suppress this error type if it finds false errors in your project.
To suppress this error, use the issue id "InconsistentArrays" as explained in the Suppressing Warnings and Errors section.
+
++
+Note however that there may be cases where you really want to declare a different number of array items in each configuration (for example where the array represents available options, and those options differ for different layout orientations and so on), so use your own judgement to decide if this is really an error.
+
+You can suppress this error type if it finds false errors in your project.
To suppress this error, use the issue id "InconsistentArrays" as explained in the Suppressing Warnings and Errors section.
+
+
+InconsistentLayout
+
+Disabled By: Project lint.xml file
+
++
+This check ensures that a layout resource which is defined in multiple resource folders, specifies the same set of widgets.
+
+This finds cases where you have accidentally forgotten to add a widget to all variations of the layout, which could result in a runtime crash for some resource configurations when a
+
+There are cases where this is intentional. For example, you may have a dedicated large tablet layout which adds some extra widgets that are not present in the phone version of the layout. As long as the code accessing the layout resource is careful to handle this properly, it is valid. In that case, you can suppress this lint check for the given extra or missing views, or the whole layout
To suppress this error, use the issue id "InconsistentLayout" as explained in the Suppressing Warnings and Errors section.
+
++
+This finds cases where you have accidentally forgotten to add a widget to all variations of the layout, which could result in a runtime crash for some resource configurations when a
findViewById() fails.+
+There are cases where this is intentional. For example, you may have a dedicated large tablet layout which adds some extra widgets that are not present in the phone version of the layout. As long as the code accessing the layout resource is careful to handle this properly, it is valid. In that case, you can suppress this lint check for the given extra or missing views, or the whole layout
To suppress this error, use the issue id "InconsistentLayout" as explained in the Suppressing Warnings and Errors section.
+
+
+InefficientWeight
+
+Disabled By: Project lint.xml file
+
++
+When only a single widget in a LinearLayout defines a weight, it is more efficient to assign a width/height of
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "InefficientWeight" as explained in the Suppressing Warnings and Errors section.
+
+0dp to it since it will absorb all the remaining space anyway. With a declared width/height of 0dp it does not have to measure its own size first.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "InefficientWeight" as explained in the Suppressing Warnings and Errors section.
+
+
+InflateParams
+
+Disabled By: Project lint.xml file
+
++
+When inflating a layout, avoid passing in null as the parent view, since otherwise any layout parameters on the root of the inflated layout will be ignored.
To suppress this error, use the issue id "InflateParams" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "InflateParams" as explained in the Suppressing Warnings and Errors section.
+
+
+InlinedApi
+
+Disabled By: Project lint.xml file
+
++
+This check scans through all the Android API field references in the application and flags certain constants, such as static final integers and Strings, which were introduced in later versions. These will actually be copied into the class files rather than being referenced, which means that the value is available even when running on older devices. In some cases that's fine, and in other cases it can result in a runtime crash or incorrect behavior. It depends on the context, so consider the code carefully and decide whether it's safe and can be suppressed or whether the code needs to be guarded.
+
+If you really want to use this API and don't need to support older devices just set the
+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
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "InlinedApi" as explained in the Suppressing Warnings and Errors section.
+
++
+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.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "InlinedApi" as explained in the Suppressing Warnings and Errors section.
+
+
+InnerclassSeparator
+
+Disabled By: Project lint.xml file
+
++
+When you reference an inner class in a manifest file, you must use '$' instead of '.' as the separator character, i.e. Outer$Inner instead of Outer.Inner.
+
+(If you get this warning for a class which is not actually an inner class, it's because you are using uppercase characters in your package name, which is not conventional.)
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "InnerclassSeparator" as explained in the Suppressing Warnings and Errors section.
+
++
+(If you get this warning for a class which is not actually an inner class, it's because you are using uppercase characters in your package name, which is not conventional.)
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "InnerclassSeparator" as explained in the Suppressing Warnings and Errors section.
+
+
+InstantApps
+
+Disabled By: Project lint.xml file
+
++
+This issue flags code that will not work correctly in Instant Apps
To suppress this error, use the issue id "InstantApps" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "InstantApps" as explained in the Suppressing Warnings and Errors section.
+
+
+InvalidAnalyticsName
+
+Disabled By: Project lint.xml file
+
++
+Event names and parameters must follow the naming conventions defined in the`FirebaseAnalytics#logEvent()` documentation.
To suppress this error, use the issue id "InvalidAnalyticsName" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "InvalidAnalyticsName" as explained in the Suppressing Warnings and Errors section.
+
+
+InvalidImeActionId
+
+Disabled By: Project lint.xml file
+
++
+android:imeActionId should not be a resourceId such as @+id/resName. It must be an integer constant, or an integer resource reference, as defined in EditorInfo.
To suppress this error, use the issue id "InvalidImeActionId" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "InvalidImeActionId" as explained in the Suppressing Warnings and Errors section.
+
+
+InvalidPackage
+
+Disabled By: Project lint.xml file
+
++
+This check scans through libraries looking for calls to APIs that are not included in Android.
+
+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.
+
+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.
To suppress this error, use the issue id "InvalidPackage" as explained in the Suppressing Warnings and Errors section.
+
++
+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.
+
+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.
To suppress this error, use the issue id "InvalidPackage" as explained in the Suppressing Warnings and Errors section.
+
+
+InvalidPermission
+
+Disabled By: Project lint.xml file
+
++
+Not all elements support the permission attribute. If a permission is set on an invalid element, it is a no-op and ignored. Ensure that this permission attribute was set on the correct element to protect the correct component.
To suppress this error, use the issue id "InvalidPermission" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "InvalidPermission" as explained in the Suppressing Warnings and Errors section.
+
+
+InvalidResourceFolder
+
+Disabled By: Project lint.xml file
+
++
+This lint check looks for a folder name that is not a valid resource folder name; these will be ignored and not packaged by the Android Gradle build plugin.
+
+Note that the order of resources is very important; for example, you can't specify a language before a network code.
+
+Similarly, note that to use 3 letter region codes, you have to use a special BCP 47 syntax: the prefix b+ followed by the BCP 47 language tag but with
+
++
+Note that the order of resources is very important; for example, you can't specify a language before a network code.
+
+Similarly, note that to use 3 letter region codes, you have to use a special BCP 47 syntax: the prefix b+ followed by the BCP 47 language tag but with
+ as the individual separators instead of -. Therefore, for the BCP 47 language tag nl-ABW you have to use b+nl+ABW.More info:
To suppress this error, use the issue id "InvalidResourceFolder" as explained in the Suppressing Warnings and Errors section.+
+
+InvalidUsesTagAttribute
+
+Disabled By: Project lint.xml file
+
++
+The <uses> element in
+Valid values are
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "InvalidUsesTagAttribute" as explained in the Suppressing Warnings and Errors section.
+
+<automotiveApp> should contain a valid value for the name attribute.+Valid values are
media or notification.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "InvalidUsesTagAttribute" as explained in the Suppressing Warnings and Errors section.
+
+
+InvalidVectorPath
+
+Disabled By: Project lint.xml file
+
++
+This check ensures that vector paths are valid. For example, it makes sure that the numbers are not using scientific notation (such as 1.0e3) which can lead to runtime crashes on older devices. As another example, it flags numbers like
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "InvalidVectorPath" as explained in the Suppressing Warnings and Errors section.
+
+.5 which should be written as 0.5 instead to avoid crashes on some pre-Marshmallow devices.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "InvalidVectorPath" as explained in the Suppressing Warnings and Errors section.
+
+
+InvalidWearFeatureAttribute
+
+Disabled By: Project lint.xml file
+
++
+For the
To suppress this error, use the issue id "InvalidWearFeatureAttribute" as explained in the Suppressing Warnings and Errors section.
+
+android.hardware.type.watch uses-feature, android:required="false" is disallowed. A single APK for Wear and non-Wear devices is not supported.To suppress this error, use the issue id "InvalidWearFeatureAttribute" as explained in the Suppressing Warnings and Errors section.
+
+
+JavascriptInterface
+
+Disabled By: Project lint.xml file
+
++
+As of API 17, you must annotate methods in objects registered with the
To suppress this error, use the issue id "JavascriptInterface" as explained in the Suppressing Warnings and Errors section.
+
+addJavascriptInterface method with a @JavascriptInterface annotation.To suppress this error, use the issue id "JavascriptInterface" as explained in the Suppressing Warnings and Errors section.
+
+
+JobSchedulerService
+
+Disabled By: Project lint.xml file
+
++
+This check looks for various common mistakes in using the JobScheduler API: the service class must extend
To suppress this error, use the issue id "JobSchedulerService" as explained in the Suppressing Warnings and Errors section.
+
+JobService, the service must be registered in the manifest and the registration must require the permission android.permission.BIND_JOB_SERVICE.To suppress this error, use the issue id "JobSchedulerService" as explained in the Suppressing Warnings and Errors section.
+
+
+KeyboardInaccessibleWidget
+
+Disabled By: Project lint.xml file
+
++
+A widget that is declared to be clickable but not declared to be focusable is not accessible via the keyboard. Please add the
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "KeyboardInaccessibleWidget" as explained in the Suppressing Warnings and Errors section.
+
+focusable attribute as well.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "KeyboardInaccessibleWidget" as explained in the Suppressing Warnings and Errors section.
+
+
+LabelFor
+
+Disabled By: Project lint.xml file
+
++
+Editable text fields should provide an
+
+When using
+
+If your view is labeled but by a label in a different layout which includes this one, just suppress this warning from lint.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "LabelFor" as explained in the Suppressing Warnings and Errors section.
+
+android:hint or, provided your minSdkVersion is at least 17, they may be referenced by a view with a android:labelFor attribute.+
+When using
android:labelFor, be sure to provide an android:text or an android:contentDescription.+
+If your view is labeled but by a label in a different layout which includes this one, just suppress this warning from lint.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "LabelFor" as explained in the Suppressing Warnings and Errors section.
+
+
+LocalSuppress
+
+Disabled By: Project lint.xml file
+
++
+The
To suppress this error, use the issue id "LocalSuppress" as explained in the Suppressing Warnings and Errors section.
+
+@SuppressAnnotation is used to suppress Lint warnings in Java files. However, while many lint checks analyzes the Java source code, where they can find annotations on (for example) local variables, some checks are analyzing the .class files. And in class files, annotations only appear on classes, fields and methods. Annotations placed on local variables disappear. If you attempt to suppress a lint error for a class-file based lint check, the suppress annotation not work. You must move the annotation out to the surrounding method.To suppress this error, use the issue id "LocalSuppress" as explained in the Suppressing Warnings and Errors section.
+
+
+LocaleFolder
+
+Disabled By: Project lint.xml file
+
++
+From the
+"Note that Java uses several deprecated two-letter codes. The Hebrew ("he") language code is rewritten as "iw", Indonesian ("id") as "in", and Yiddish ("yi") as "ji". This rewriting happens even if you construct your own Locale object, not just for instances returned by the various lookup methods.
+
+Because of this, if you add your localized resources in for example
+
+To work around this, place your resources in a
To suppress this error, use the issue id "LocaleFolder" as explained in the Suppressing Warnings and Errors section.
+
+java.util.Locale documentation:+"Note that Java uses several deprecated two-letter codes. The Hebrew ("he") language code is rewritten as "iw", Indonesian ("id") as "in", and Yiddish ("yi") as "ji". This rewriting happens even if you construct your own Locale object, not just for instances returned by the various lookup methods.
+
+Because of this, if you add your localized resources in for example
values-he they will not be used, since the system will look for values-iw instead.+
+To work around this, place your resources in a
values folder using the deprecated language code instead.To suppress this error, use the issue id "LocaleFolder" as explained in the Suppressing Warnings and Errors section.
+
+
+LogConditional
+
+Disabled By: Default
+
++
+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.
To suppress this error, use the issue id "LogConditional" as explained in the Suppressing Warnings and Errors section.
+
++
+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.
To suppress this error, use the issue id "LogConditional" as explained in the Suppressing Warnings and Errors section.
+
+
+LogTagMismatch
+
+Disabled By: Project lint.xml file
+
++
+When guarding a
To suppress this error, use the issue id "LogTagMismatch" as explained in the Suppressing Warnings and Errors section.
+
+Log.v(tag, ...) call with Log.isLoggable(tag), the tag passed to both calls should be the same. Similarly, the level passed in to Log.isLoggable should typically match the type of Log call, e.g. if checking level Log.DEBUG, the corresponding Log call should be Log.d, not Log.i.To suppress this error, use the issue id "LogTagMismatch" as explained in the Suppressing Warnings and Errors section.
+
+
+LongLogTag
+
+Disabled By: Project lint.xml file
+
++
+Log tags are only allowed to be at most 23 tag characters long.
To suppress this error, use the issue id "LongLogTag" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "LongLogTag" as explained in the Suppressing Warnings and Errors section.
+
+
+MangledCRLF
+
+Disabled By: Default
+
++
+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.
+
++
+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.+
+
+ManifestOrder
+
+Disabled By: Project lint.xml file
+
++
+The <application> tag should appear after the elements which declare which version you need, which features you need, which libraries you need, and so on. In the past there have been subtle bugs (such as themes not getting applied correctly) when the
To suppress this error, use the issue id "ManifestOrder" as explained in the Suppressing Warnings and Errors section.
+
+<application> tag appears before some of these other elements, so it's best to order your manifest in the logical dependency order.To suppress this error, use the issue id "ManifestOrder" as explained in the Suppressing Warnings and Errors section.
+
+
+MenuTitle
+
+Disabled By: Project lint.xml file
+
++
+From the action bar documentation:
+"It's important that you always define android:title for each menu item — even if you don't declare that the title appear with the action item — for three reasons:
+
+* If there's not enough room in the action bar for the action item, the menu item appears in the overflow menu and only the title appears.
+* Screen readers for sight-impaired users read the menu item's title.
+* If the action item appears with only the icon, a user can long-press the item to reveal a tool-tip that displays the action item's title.
+The android:icon is always optional, but recommended.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "MenuTitle" as explained in the Suppressing Warnings and Errors section.
+
++"It's important that you always define android:title for each menu item — even if you don't declare that the title appear with the action item — for three reasons:
+
+* If there's not enough room in the action bar for the action item, the menu item appears in the overflow menu and only the title appears.
+* Screen readers for sight-impaired users read the menu item's title.
+* If the action item appears with only the icon, a user can long-press the item to reveal a tool-tip that displays the action item's title.
+The android:icon is always optional, but recommended.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "MenuTitle" as explained in the Suppressing Warnings and Errors section.
+
+
+MergeMarker
+
+Disabled By: Project lint.xml file
+
++
+Many version control systems leave unmerged files with markers such as <<< in the source code. This check looks for these markers, which are sometimes accidentally left in, particularly in resource files where they don't break compilation.
To suppress this error, use the issue id "MergeMarker" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "MergeMarker" as explained in the Suppressing Warnings and Errors section.
+
+
+MergeRootFrame
+
+Disabled By: Project lint.xml file
+
++
+If a
+
+<FrameLayout> is the root of a layout and does not provide background or padding etc, it can often be replaced with a <merge> tag which is slightly more efficient. Note that this depends on context, so make sure you understand how the <merge> tag works before proceeding.More info: http://android-developers.blogspot.com/2009/03/android-layout-tricks-3-optimize-by.html
+
To suppress this error, use the issue id "MergeRootFrame" as explained in the Suppressing Warnings and Errors section.+
+
+MinSdkTooLow
+
+Disabled By: Default
+
++
+The value of the
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "MinSdkTooLow" as explained in the Suppressing Warnings and Errors section.
+
+minSdkVersion property is too low and can be incrementedwithout noticeably reducing the number of supported devices.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "MinSdkTooLow" as explained in the Suppressing Warnings and Errors section.
+
+
+MipmapIcons
+
+Disabled By: Project lint.xml file
+
++
+Launcher icons should be provided in the
+
+In certain cases, the Launcher app may use a higher resolution asset (than would normally be computed for the device) to display large app shortcuts. If drawables for densities other than the device's resolution have been stripped out, then the app shortcut could appear blurry.
+
+To fix this, move your launcher icons from `drawable-`dpi to `mipmap-`dpi and change references from @drawable/ and R.drawable to @mipmap/ and R.mipmap.
+In Android Studio this lint warning has a quickfix to perform this automatically.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "MipmapIcons" as explained in the Suppressing Warnings and Errors section.
+
+mipmap resource directory. This is the same as the drawable resource directory, except resources in the mipmap directory will not get stripped out when creating density-specific APKs.+
+In certain cases, the Launcher app may use a higher resolution asset (than would normally be computed for the device) to display large app shortcuts. If drawables for densities other than the device's resolution have been stripped out, then the app shortcut could appear blurry.
+
+To fix this, move your launcher icons from `drawable-`dpi to `mipmap-`dpi and change references from @drawable/ and R.drawable to @mipmap/ and R.mipmap.
+In Android Studio this lint warning has a quickfix to perform this automatically.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "MipmapIcons" as explained in the Suppressing Warnings and Errors section.
+
+
+MissingApplicationIcon
+
+Disabled By: Project lint.xml file
+
++
+You should set an icon for the application as whole because there is no default. This attribute must be set as a reference to a drawable resource containing the image (for example
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "MissingApplicationIcon" as explained in the Suppressing Warnings and Errors section.
+
+@drawable/icon).Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "MissingApplicationIcon" as explained in the Suppressing Warnings and Errors section.
+
+
+MissingBackupPin
+
+Disabled By: Project lint.xml file
+
++
+It is highly recommended to declare a backup
To suppress this error, use the issue id "MissingBackupPin" as explained in the Suppressing Warnings and Errors section.
+
+<pin> element. Not having a second pin defined can cause connection failures when the particular site certificate is rotated and the app has not yet been updated.To suppress this error, use the issue id "MissingBackupPin" as explained in the Suppressing Warnings and Errors section.
+
+
+MissingConstraints
+
+Disabled By: Project lint.xml file
+
++
+The layout editor allows you to place widgets anywhere on the canvas, and it records the current position with designtime attributes (such as
To suppress this error, use the issue id "MissingConstraints" as explained in the Suppressing Warnings and Errors section.
+
+layout_editor_absoluteX). These attributes are not applied at runtime, so if you push your layout on a device, the widgets may appear in a different location than shown in the editor. To fix this, make sure a widget has both horizontal and vertical constraints by dragging from the edge connections.To suppress this error, use the issue id "MissingConstraints" as explained in the Suppressing Warnings and Errors section.
+
+
+MissingFirebaseInstanceTokenRefresh
+
+Disabled By: Project lint.xml file
+
++
+Apps that check the Firebase Instance ID should usually implement the FirebaseInstanceIdService#onTokenRefresh() callback in order to observe changes.
+
+More info: https://firebase.google.com/docs/cloud-messaging/android/client#monitor-token-generation
+
To suppress this error, use the issue id "MissingFirebaseInstanceTokenRefresh" as explained in the Suppressing Warnings and Errors section.+
+
+MissingId
+
+Disabled By: Project lint.xml file
+
++
+If you do not specify an android:id or an android:tag attribute on a <fragment> element, then if the activity is restarted (for example for an orientation rotation) you may lose state. From the fragment documentation:
+
+"Each fragment requires a unique identifier that the system can use to restore the fragment if the activity is restarted (and which you can use to capture the fragment to perform transactions, such as remove it).
+
+* Supply the android:id attribute with a unique ID.
+* Supply the android:tag attribute with a unique string.
+If you provide neither of the previous two, the system uses the ID of the container view.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "MissingId" as explained in the Suppressing Warnings and Errors section.
+
++
+"Each fragment requires a unique identifier that the system can use to restore the fragment if the activity is restarted (and which you can use to capture the fragment to perform transactions, such as remove it).
+
+* Supply the android:id attribute with a unique ID.
+* Supply the android:tag attribute with a unique string.
+If you provide neither of the previous two, the system uses the ID of the container view.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "MissingId" as explained in the Suppressing Warnings and Errors section.
+
+
+MissingIntentFilterForMediaSearch
+
+Disabled By: Project lint.xml file
+
++
+To support voice searches on Android Auto, you should also register an
+To do this, add
+
+
+
+to your
To suppress this error, use the issue id "MissingIntentFilterForMediaSearch" as explained in the Suppressing Warnings and Errors section.
+
+intent-filter for the action android.media.action.MEDIA_PLAY_FROM_SEARCH.+To do this, add
+
<intent-filter>+
<action android:name="android.media.action.MEDIA_PLAY_FROM_SEARCH" />+
</intent-filter>+to your
<activity> or <service>.To suppress this error, use the issue id "MissingIntentFilterForMediaSearch" as explained in the Suppressing Warnings and Errors section.
+
+
+MissingLeanbackLauncher
+
+Disabled By: Project lint.xml file
+
++
+An application intended to run on TV devices must declare a launcher activity for TV in its manifest using a
To suppress this error, use the issue id "MissingLeanbackLauncher" as explained in the Suppressing Warnings and Errors section.
+
+android.intent.category.LEANBACK_LAUNCHER intent filter.To suppress this error, use the issue id "MissingLeanbackLauncher" as explained in the Suppressing Warnings and Errors section.
+
+
+MissingLeanbackSupport
+
+Disabled By: Project lint.xml file
+
++
+The manifest should declare the use of the Leanback user interface required by Android TV.
+To fix this, add
+
+to your manifest.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "MissingLeanbackSupport" as explained in the Suppressing Warnings and Errors section.
+
++To fix this, add
+
<uses-feature android:name="android.software.leanback" android:required="false" />+to your manifest.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "MissingLeanbackSupport" as explained in the Suppressing Warnings and Errors section.
+
+
+MissingMediaBrowserServiceIntentFilter
+
+Disabled By: Project lint.xml file
+
++
+An Automotive Media App requires an exported service that extends
+To do this, add
+
+
+
+ to the service that extends
To suppress this error, use the issue id "MissingMediaBrowserServiceIntentFilter" as explained in the Suppressing Warnings and Errors section.
+
+android.service.media.MediaBrowserService with an intent-filter for the action android.media.browse.MediaBrowserService to be able to browse and play media.+To do this, add
+
<intent-filter>+
<action android:name="android.media.browse.MediaBrowserService" />+
</intent-filter>+ to the service that extends
android.service.media.MediaBrowserServiceTo suppress this error, use the issue id "MissingMediaBrowserServiceIntentFilter" as explained in the Suppressing Warnings and Errors section.
+
+
+MissingOnPlayFromSearch
+
+Disabled By: Project lint.xml file
+
++
+To support voice searches on Android Auto, in addition to adding an
To suppress this error, use the issue id "MissingOnPlayFromSearch" as explained in the Suppressing Warnings and Errors section.
+
+intent-filter for the action onPlayFromSearch, you also need to override and implement onPlayFromSearch(String query, Bundle bundle)To suppress this error, use the issue id "MissingOnPlayFromSearch" as explained in the Suppressing Warnings and Errors section.
+
+
+MissingPermission
+
+Disabled By: Project lint.xml file
+
++
+This check scans through your code and libraries and looks at the APIs being used, and checks this against the set of permissions required to access those APIs. If the code using those APIs is called at runtime, then the program will crash.
+
+Furthermore, for permissions that are revocable (with targetSdkVersion 23), client code must also be prepared to handle the calls throwing an exception if the user rejects the request for permission at runtime.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "MissingPermission" as explained in the Suppressing Warnings and Errors section.
+
++
+Furthermore, for permissions that are revocable (with targetSdkVersion 23), client code must also be prepared to handle the calls throwing an exception if the user rejects the request for permission at runtime.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "MissingPermission" as explained in the Suppressing Warnings and Errors section.
+
+
+MissingPrefix
+
+Disabled By: Project lint.xml file
+
++
+Most Android views have attributes in the Android namespace. When referencing these attributes you must include the namespace prefix, or your attribute will be interpreted by
+
+Similarly, in manifest files, nearly all attributes should be in the
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "MissingPrefix" as explained in the Suppressing Warnings and Errors section.
+
+aapt as just a custom attribute.+
+Similarly, in manifest files, nearly all attributes should be in the
android: namespace.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "MissingPrefix" as explained in the Suppressing Warnings and Errors section.
+
+
+MissingQuantity
+
+Disabled By: Project lint.xml file
+
++
+Different languages have different rules for grammatical agreement with quantity. In English, for example, the quantity 1 is a special case. We write "1 book", but for any other quantity we'd write "n books". This distinction between singular and plural is very common, but other languages make finer distinctions.
+
+This lint check looks at each translation of a
+
+For example, an English translation must provide a string for
To suppress this error, use the issue id "MissingQuantity" as explained in the Suppressing Warnings and Errors section.
+
++
+This lint check looks at each translation of a
<plural> and makes sure that all the quantity strings considered by the given language are provided by this translation.+
+For example, an English translation must provide a string for
quantity="one". Similarly, a Czech translation must provide a string for quantity="few".To suppress this error, use the issue id "MissingQuantity" as explained in the Suppressing Warnings and Errors section.
+
+
+MissingRegistered
+
+Disabled By: Default
+
++
+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.
To suppress this error, use the issue id "MissingRegistered" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "MissingRegistered" as explained in the Suppressing Warnings and Errors section.
+
+
+MissingSuperCall
+
+Disabled By: Project lint.xml file
+
++
+Some methods, such as
+implementation as part of your method.
To suppress this error, use the issue id "MissingSuperCall" as explained in the Suppressing Warnings and Errors section.
+
+View#onDetachedFromWindow, require that you also call the super+implementation as part of your method.
To suppress this error, use the issue id "MissingSuperCall" as explained in the Suppressing Warnings and Errors section.
+
+
+MissingTvBanner
+
+Disabled By: Project lint.xml file
+
++
+A TV application must provide a home screen banner for each localization if it includes a Leanback launcher intent filter. The banner is the app launch point that appears on the home screen in the apps and games rows.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "MissingTvBanner" as explained in the Suppressing Warnings and Errors section.
+
+Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "MissingTvBanner" as explained in the Suppressing Warnings and Errors section.
+
+
+MissingVersion
+
+Disabled By: Project lint.xml file
+
++
+You should define the version information for your application.
+
+
+
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "MissingVersion" as explained in the Suppressing Warnings and Errors section.
+
++
android:versionCode: An integer value that represents the version of the application code, relative to other versions.+
+
android:versionName: A string value that represents the release version of the application code, as it should be shown to users.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "MissingVersion" as explained in the Suppressing Warnings and Errors section.
+
+
+NegativeMargin
+
+Disabled By: Default
+
++
+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.
To suppress this error, use the issue id "NegativeMargin" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "NegativeMargin" as explained in the Suppressing Warnings and Errors section.
+
+
+NestedScrolling
+
+Disabled By: Project lint.xml file
+
++
+A scrolling widget such as a
To suppress this error, use the issue id "NestedScrolling" as explained in the Suppressing Warnings and Errors section.
+
+ScrollView should not contain any nested scrolling widgets since this has various usability issuesTo suppress this error, use the issue id "NestedScrolling" as explained in the Suppressing Warnings and Errors section.
+
+
+NestedWeights
+
+Disabled By: Project lint.xml file
+
++
+Layout weights require a widget to be measured twice. When a LinearLayout with non-zero weights is nested inside another LinearLayout with non-zero weights, then the number of measurements increase exponentially.
To suppress this error, use the issue id "NestedWeights" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "NestedWeights" as explained in the Suppressing Warnings and Errors section.
+
+
+NewApi
+
+Disabled By: Project lint.xml file
+
++
+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
+
+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
+
+If you are deliberately setting
+
+Similarly, you can use tools:targetApi="11" in an XML file to indicate that the element will only be inflated in an adequate context.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "NewApi" as explained in the Suppressing Warnings and Errors section.
+
++
+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.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "NewApi" as explained in the Suppressing Warnings and Errors section.
+
+
+NewerVersionAvailable
+
+Disabled By: Default
+
++
+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
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "NewerVersionAvailable" as explained in the Suppressing Warnings and Errors section.
+
+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.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "NewerVersionAvailable" as explained in the Suppressing Warnings and Errors section.
+
+
+NotInterpolated
+
+Disabled By: Project lint.xml file
+
++
+To insert the value of a variable, you can use
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "NotInterpolated" as explained in the Suppressing Warnings and Errors section.
+
+${variable} inside a string literal, but only if you are using double quotes!Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "NotInterpolated" as explained in the Suppressing Warnings and Errors section.
+
+
+ObjectAnimatorBinding
+
+Disabled By: Project lint.xml file
+
++
+This check cross references properties referenced by String from
To suppress this error, use the issue id "ObjectAnimatorBinding" as explained in the Suppressing Warnings and Errors section.
+
+ObjectAnimator and PropertyValuesHolder method calls and ensures that the corresponding setter methods exist and have the right signatures.To suppress this error, use the issue id "ObjectAnimatorBinding" as explained in the Suppressing Warnings and Errors section.
+
+
+ObsoleteLayoutParam
+
+Disabled By: Project lint.xml file
+
++
+The given layout_param is not defined for the given layout, meaning it has no effect. This usually happens when you change the parent layout or move view code around without updating the layout params. This will cause useless attribute processing at runtime, and is misleading for others reading the layout so the parameter should be removed.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ObsoleteLayoutParam" as explained in the Suppressing Warnings and Errors section.
+
+Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ObsoleteLayoutParam" as explained in the Suppressing Warnings and Errors section.
+
+
+ObsoleteSdkInt
+
+Disabled By: Project lint.xml file
+
++
+This check flags version checks that are not necessary, because the
+
+Similarly, it also looks for resources in
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ObsoleteSdkInt" as explained in the Suppressing Warnings and Errors section.
+
+minSdkVersion (or surrounding known API level) is already at least as high as the version checked for.+
+Similarly, it also looks for resources in
-vNN folders, such as values-v14 where the version qualifier is less than or equal to the minSdkVersion, where the contents should be merged into the best folder.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ObsoleteSdkInt" as explained in the Suppressing Warnings and Errors section.
+
+
+OldTargetApi
+
+Disabled By: Project lint.xml file
+
++
+When your application runs on a version of Android that is more recent than your
+
+To fix this issue, set the
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "OldTargetApi" as explained in the Suppressing Warnings and Errors section.
+
+targetSdkVersion 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 targetSdkVersion is less than 14, your app may get an option button in the UI.+
+To fix this issue, set the
targetSdkVersion 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: http://developer.android.com/reference/android/os/Build.VERSION_CODES.htmlNote: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "OldTargetApi" as explained in the Suppressing Warnings and Errors section.
+
+
+OnClick
+
+Disabled By: Project lint.xml file
+
++
+The
+
+Must be a string value, using '\;' to escape characters such as '\n' or '\uxxxx' for a unicode character.
To suppress this error, use the issue id "OnClick" as explained in the Suppressing Warnings and Errors section.
+
+onClick attribute value should be the name of a method in this View's context to invoke when the view is clicked. This name must correspond to a public method that takes exactly one parameter of type View.+
+Must be a string value, using '\;' to escape characters such as '\n' or '\uxxxx' for a unicode character.
To suppress this error, use the issue id "OnClick" as explained in the Suppressing Warnings and Errors section.
+
+
+Orientation
+
+Disabled By: Project lint.xml file
+
++
+The default orientation of a LinearLayout is horizontal. It's pretty easy to believe that the layout is vertical, add multiple children to it, and wonder why only the first child is visible (when the subsequent children are off screen to the right). This lint rule helps pinpoint this issue by warning whenever a LinearLayout is used with an implicit orientation and multiple children.
+
+It also checks for empty LinearLayouts without an
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "Orientation" as explained in the Suppressing Warnings and Errors section.
+
++
+It also checks for empty LinearLayouts without an
orientation attribute that also defines an id attribute. This catches the scenarios where children will be added to the LinearLayout dynamically.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "Orientation" as explained in the Suppressing Warnings and Errors section.
+
+
+Overdraw
+
+Disabled By: Project lint.xml file
+
++
+If you set a background drawable on a root view, then you should use a custom theme where the theme background is null. Otherwise, the theme background will be painted first, only to have your custom background completely cover it; this is called "overdraw".
+
+NOTE: This detector relies on figuring out which layouts are associated with which activities based on scanning the Java code, and it's currently doing that using an inexact pattern matching algorithm. Therefore, it can incorrectly conclude which activity the layout is associated with and then wrongly complain that a background-theme is hidden.
+
+If you want your custom background on multiple pages, then you should consider making a custom theme with your custom background and just using that theme instead of a root element background.
+
+Of course it's possible that your custom drawable is translucent and you want it to be mixed with the background. However, you will get better performance if you pre-mix the background with your drawable and use that resulting image or color as a custom theme background instead.
To suppress this error, use the issue id "Overdraw" as explained in the Suppressing Warnings and Errors section.
+
++
+NOTE: This detector relies on figuring out which layouts are associated with which activities based on scanning the Java code, and it's currently doing that using an inexact pattern matching algorithm. Therefore, it can incorrectly conclude which activity the layout is associated with and then wrongly complain that a background-theme is hidden.
+
+If you want your custom background on multiple pages, then you should consider making a custom theme with your custom background and just using that theme instead of a root element background.
+
+Of course it's possible that your custom drawable is translucent and you want it to be mixed with the background. However, you will get better performance if you pre-mix the background with your drawable and use that resulting image or color as a custom theme background instead.
To suppress this error, use the issue id "Overdraw" as explained in the Suppressing Warnings and Errors section.
+
+
+Override
+
+Disabled By: Project lint.xml file
+
++
+Suppose you are building against Android API 8, and you've subclassed Activity. In your subclass you add a new method called
+
+The above scenario is what this lint detector looks for. The above example is real, since
+
+To fix this, either rename your method, or if you are really trying to augment the builtin method if available, switch to a higher build target where you can deliberately add
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "Override" as explained in the Suppressing Warnings and Errors section.
+
+isDestroyed(). At some later point, a method of the same name and signature is added to Android. Your method will now override the Android method, and possibly break its contract. Your method is not calling super.isDestroyed(), since your compilation target doesn't know about the method.+
+The above scenario is what this lint detector looks for. The above example is real, since
isDestroyed() was added in API 17, but it will be true for any method you have added to a subclass of an Android class where your build target is lower than the version the method was introduced in.+
+To fix this, either rename your method, or if you are really trying to augment the builtin method if available, switch to a higher build target where you can deliberately add
@Override on your overriding method, and call super if appropriate etc.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "Override" as explained in the Suppressing Warnings and Errors section.
+
+
+OverrideAbstract
+
+Disabled By: Project lint.xml file
+
++
+To improve the usability of some APIs, some methods that used to be
+
+However, if your code is also targeting older versions of the platform where these methods were still
To suppress this error, use the issue id "OverrideAbstract" as explained in the Suppressing Warnings and Errors section.
+
+abstract have been made concrete by adding default implementations. This means that when compiling with new versions of the SDK, your code does not have to override these methods.+
+However, if your code is also targeting older versions of the platform where these methods were still
abstract, the code will crash. You must override all methods that used to be abstract in any versions targeted by your application's minSdkVersion.To suppress this error, use the issue id "OverrideAbstract" as explained in the Suppressing Warnings and Errors section.
+
+
+PackageManagerGetSignatures
+
+Disabled By: Project lint.xml file
+
++
+Improper validation of app signatures could lead to issues where a malicious app submits itself to the Play Store with both its real certificate and a fake certificate and gains access to functionality or information it shouldn't have due to another application only checking for the fake certificate and ignoring the rest. Please make sure to validate all signatures returned by this method.
To suppress this error, use the issue id "PackageManagerGetSignatures" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "PackageManagerGetSignatures" as explained in the Suppressing Warnings and Errors section.
+
+
+ParcelClassLoader
+
+Disabled By: Project lint.xml file
+
++
+The documentation for
+
+If you are writing your own classes into the
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ParcelClassLoader" as explained in the Suppressing Warnings and Errors section.
+
+Parcel#readParcelable(ClassLoader) (and its variations) says that you can pass in null to pick up the default class loader. However, that ClassLoader is a system class loader and is not able to find classes in your own application.+
+If you are writing your own classes into the
Parcel (not just SDK classes like String and so on), then you should supply a ClassLoader for your application instead; a simple way to obtain one is to just call getClass().getClassLoader() from your own class.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ParcelClassLoader" as explained in the Suppressing Warnings and Errors section.
+
+
+ParcelCreator
+
+Disabled By: Project lint.xml file
+
++
+According to the
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ParcelCreator" as explained in the Suppressing Warnings and Errors section.
+
+Parcelable interface documentation, "Classes implementing the Parcelable interface must also have a static field called CREATOR, which is an object implementing the Parcelable.Creator interface."Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ParcelCreator" as explained in the Suppressing Warnings and Errors section.
+
+
+PendingBindings
+
+Disabled By: Project lint.xml file
+
++
+When using a
To suppress this error, use the issue id "PendingBindings" as explained in the Suppressing Warnings and Errors section.
+
+ViewDataBinding in a onBindViewHolder method, you must call executePendingBindings() before the method exits; otherwise the data binding runtime will update the UI in the next animation frame causing a delayed update and potential jumps if the item resizes.To suppress this error, use the issue id "PendingBindings" as explained in the Suppressing Warnings and Errors section.
+
+
+PermissionImpliesUnsupportedChromeOsHardware
+
+Disabled By: Default
+
++
+The
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "PermissionImpliesUnsupportedChromeOsHardware" as explained in the Suppressing Warnings and Errors section.
+
+<uses-permission> element should not require a permission that implies an unsupported Chrome OS hardware feature. Google Play assumes that certain hardware related permissions indicate that the underlying hardware features are required by default. To fix the issue, consider declaring the corresponding uses-feature element with required="false" attribute.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "PermissionImpliesUnsupportedChromeOsHardware" as explained in the Suppressing Warnings and Errors section.
+
+
+PermissionImpliesUnsupportedHardware
+
+Disabled By: Project lint.xml file
+
++
+The <uses-permission> element should not require a permission that implies an unsupported TV hardware feature. Google Play assumes that certain hardware related permissions indicate that the underlying hardware features are required by default. To fix the issue, consider declaring the corresponding uses-feature element with required="false" attribute.
+To suppress this error, use the issue id "PermissionImpliesUnsupportedHardware" as explained in the Suppressing Warnings and Errors section.
+
+More info: http://developer.android.com/guide/topics/manifest/uses-feature-element.html#permissions
+
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.+To suppress this error, use the issue id "PermissionImpliesUnsupportedHardware" as explained in the Suppressing Warnings and Errors section.
+
+
+PinSetExpiry
+
+Disabled By: Project lint.xml file
+
++
+Ensures that the
To suppress this error, use the issue id "PinSetExpiry" as explained in the Suppressing Warnings and Errors section.
+
+expiration attribute of the <pin-set> element is valid and has not already expired or is expiring soonTo suppress this error, use the issue id "PinSetExpiry" as explained in the Suppressing Warnings and Errors section.
+
+
+PluralsCandidate
+
+Disabled By: Project lint.xml file
+
++
+This lint check looks for potential errors in internationalization where you have translated a message which involves a quantity and it looks like other parts of the string may need grammatical changes.
+
+For example, rather than something like this:
+ <string name="try_again">Try again in %d seconds.</string>
+you should be using a plural:
+ <plurals name="try_again">
+ <item quantity="one">Try again in %d second</item>
+ <item quantity="other">Try again in %d seconds</item>
+ </plurals>
+This will ensure that in other languages the right set of translations are provided for the different quantity classes.
+
+(This check depends on some heuristics, so it may not accurately determine whether a string really should be a quantity. You can use tools:ignore to filter out false positives.
To suppress this error, use the issue id "PluralsCandidate" as explained in the Suppressing Warnings and Errors section.
+
++
+For example, rather than something like this:
+ <string name="try_again">Try again in %d seconds.</string>
+you should be using a plural:
+ <plurals name="try_again">
+ <item quantity="one">Try again in %d second</item>
+ <item quantity="other">Try again in %d seconds</item>
+ </plurals>
+This will ensure that in other languages the right set of translations are provided for the different quantity classes.
+
+(This check depends on some heuristics, so it may not accurately determine whether a string really should be a quantity. You can use tools:ignore to filter out false positives.
To suppress this error, use the issue id "PluralsCandidate" as explained in the Suppressing Warnings and Errors section.
+
+
+PrivateApi
+
+Disabled By: Project lint.xml file
+
++
+Using reflection to access hidden/private Android APIs is not safe; it will often not work on devices from other vendors, and it may suddenly stop working (if the API is removed) or crash spectacularly (if the API behavior changes, since there are no guarantees for compatibility).
To suppress this error, use the issue id "PrivateApi" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "PrivateApi" as explained in the Suppressing Warnings and Errors section.
+
+
+PrivateResource
+
+Disabled By: Project lint.xml file
+
++
+Private resources should not be referenced; the may not be present everywhere, and even where they are they may disappear without notice.
+
+To fix this, copy the resource into your own project instead.
To suppress this error, use the issue id "PrivateResource" as explained in the Suppressing Warnings and Errors section.
+
++
+To fix this, copy the resource into your own project instead.
To suppress this error, use the issue id "PrivateResource" as explained in the Suppressing Warnings and Errors section.
+
+
+ProguardSplit
+
+Disabled By: Project lint.xml file
+
++
+Earlier versions of the Android tools bundled a single
+
+In the new version of the tools, we have split the ProGuard configuration into two halves:
+* A simple configuration file containing only project-specific flags, in your project
+* A generic configuration file containing the recommended set of ProGuard options for Android projects. This generic file lives in the SDK install directory which means that it gets updated along with the tools.
+
+In order for this to work, the proguard.config property in the
+
+To migrate your project to the new setup, create a new
+
To suppress this error, use the issue id "ProguardSplit" as explained in the Suppressing Warnings and Errors section.
+
+proguard.cfg file containing a ProGuard configuration file suitable for Android shrinking and obfuscation. However, that version was copied into new projects, which means that it does not continue to get updated as we improve the default ProGuard rules for Android.+
+In the new version of the tools, we have split the ProGuard configuration into two halves:
+* A simple configuration file containing only project-specific flags, in your project
+* A generic configuration file containing the recommended set of ProGuard options for Android projects. This generic file lives in the SDK install directory which means that it gets updated along with the tools.
+
+In order for this to work, the proguard.config property in the
project.properties file now refers to a path, so you can reference both the generic file as well as your own (and any additional files too).+
+To migrate your project to the new setup, create a new
proguard-project.txt file in your project containing any project specific ProGuard flags as well as any customizations you have made, then update your project.properties file to contain:+
proguard.config=${sdk.dir}/tools/proguard/proguard-android.txt:proguard-project.txtTo suppress this error, use the issue id "ProguardSplit" as explained in the Suppressing Warnings and Errors section.
+
+
+PropertyEscape
+
+Disabled By: Project lint.xml file
+
++
+All backslashes and colons in .property files must be escaped with a backslash (). This means that when writing a Windows path, you must escape the file separators, so the path MyFiles should be written as
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "PropertyEscape" as explained in the Suppressing Warnings and Errors section.
+
+key=\\My\\Files.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "PropertyEscape" as explained in the Suppressing Warnings and Errors section.
+
+
+ProtectedPermissions
+
+Disabled By: Project lint.xml file
+
++
+Permissions with the protection level signature, privileged or signatureOrSystem are only granted to system apps. If an app is a regular non-system app, it will never be able to use these permissions.
To suppress this error, use the issue id "ProtectedPermissions" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "ProtectedPermissions" as explained in the Suppressing Warnings and Errors section.
+
+
+PxUsage
+
+Disabled By: Project lint.xml file
+
++
+For performance reasons and to keep the code simpler, the Android system uses pixels as the standard unit for expressing dimension or coordinate values. That means that the dimensions of a view are always expressed in the code using pixels, but always based on the current screen density. For instance, if
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "PxUsage" as explained in the Suppressing Warnings and Errors section.
+
+myView.getWidth() returns 10, the view is 10 pixels wide on the current screen, but on a device with a higher density screen, the value returned might be 15. If you use pixel values in your application code to work with bitmaps that are not pre-scaled for the current screen density, you might need to scale the pixel values that you use in your code to match the un-scaled bitmap source.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "PxUsage" as explained in the Suppressing Warnings and Errors section.
+
+
+Range
+
+Disabled By: Project lint.xml file
+
++
+Some parameters are required to in a particular numerical range; this check makes sure that arguments passed fall within the range. For arrays, Strings and collections this refers to the size or length.
To suppress this error, use the issue id "Range" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "Range" as explained in the Suppressing Warnings and Errors section.
+
+
+Recycle
+
+Disabled By: Project lint.xml file
+
++
+Many resources, such as TypedArrays, VelocityTrackers, etc., should be recycled (with a
To suppress this error, use the issue id "Recycle" as explained in the Suppressing Warnings and Errors section.
+
+recycle() call) after use. This lint check looks for missing recycle() calls.To suppress this error, use the issue id "Recycle" as explained in the Suppressing Warnings and Errors section.
+
+
+RecyclerView
+
+Disabled By: Project lint.xml file
+
++
+
+
+For this reason, you should only use the position parameter while acquiring the related data item inside this method, and should not keep a copy of it.
+
+If you need the position of an item later on (e.g. in a click listener), use
To suppress this error, use the issue id "RecyclerView" as explained in the Suppressing Warnings and Errors section.
+
+RecyclerView will not call onBindViewHolder again when the position of the item changes in the data set unless the item itself is invalidated or the new position cannot be determined.+
+For this reason, you should only use the position parameter while acquiring the related data item inside this method, and should not keep a copy of it.
+
+If you need the position of an item later on (e.g. in a click listener), use
getAdapterPosition() which will have the updated adapter position.To suppress this error, use the issue id "RecyclerView" as explained in the Suppressing Warnings and Errors section.
+
+
+Registered
+
+Disabled By: Default
+
++
+Activities, services and content providers should be registered in the
+
+If your activity is simply a parent class intended to be subclassed by other "real" activities, make it an abstract class.
To suppress this error, use the issue id "Registered" as explained in the Suppressing Warnings and Errors section.
+
+AndroidManifest.xml file using <activity>, <service> and <provider> tags.+
+If your activity is simply a parent class intended to be subclassed by other "real" activities, make it an abstract class.
To suppress this error, use the issue id "Registered" as explained in the Suppressing Warnings and Errors section.
+
+
+RelativeOverlap
+
+Disabled By: Project lint.xml file
+
++
+If relative layout has text or button items aligned to left and right sides they can overlap each other due to localized text expansion unless they have mutual constraints like
To suppress this error, use the issue id "RelativeOverlap" as explained in the Suppressing Warnings and Errors section.
+
+toEndOf/toStartOf.To suppress this error, use the issue id "RelativeOverlap" as explained in the Suppressing Warnings and Errors section.
+
+
+RequiredSize
+
+Disabled By: Project lint.xml file
+
++
+All views must specify an explicit
+
+It's possible to specify these widths via styles as well. GridLayout, as a special case, does not require you to specify a size.
To suppress this error, use the issue id "RequiredSize" as explained in the Suppressing Warnings and Errors section.
+
+layout_width and layout_height attribute. There is a runtime check for this, so if you fail to specify a size, an exception is thrown at runtime.+
+It's possible to specify these widths via styles as well. GridLayout, as a special case, does not require you to specify a size.
To suppress this error, use the issue id "RequiredSize" as explained in the Suppressing Warnings and Errors section.
+
+
+ResourceAsColor
+
+Disabled By: Project lint.xml file
+
++
+Methods that take a color in the form of an integer should be passed an RGB triple, not the actual color resource id. You must call
+
+Similarly, methods that take a dimension integer should be passed an actual dimension (call
To suppress this error, use the issue id "ResourceAsColor" as explained in the Suppressing Warnings and Errors section.
+
+getResources().getColor(resource) to resolve the actual color value first.+
+Similarly, methods that take a dimension integer should be passed an actual dimension (call
getResources().getDimension(resource)To suppress this error, use the issue id "ResourceAsColor" as explained in the Suppressing Warnings and Errors section.
+
+
+ResourceType
+
+Disabled By: Project lint.xml file
+
++
+Ensures that resource id's passed to APIs are of the right type; for example, calling
To suppress this error, use the issue id "ResourceType" as explained in the Suppressing Warnings and Errors section.
+
+Resources.getColor(R.string.name) is wrong.To suppress this error, use the issue id "ResourceType" as explained in the Suppressing Warnings and Errors section.
+
+
+RestrictedApi
+
+Disabled By: Project lint.xml file
+
++
+This API has been flagged with a restriction that has not been met.
+
+Examples of API restrictions:
+* Method can only be invoked by a subclass
+* Method can only be accessed from within the same library (defined by the Gradle library group id)
+.* Method can only be accessed from tests.
+.
+You can add your own API restrictions with the
To suppress this error, use the issue id "RestrictedApi" as explained in the Suppressing Warnings and Errors section.
+
++
+Examples of API restrictions:
+* Method can only be invoked by a subclass
+* Method can only be accessed from within the same library (defined by the Gradle library group id)
+.* Method can only be accessed from tests.
+.
+You can add your own API restrictions with the
@RestrictTo annotation.To suppress this error, use the issue id "RestrictedApi" as explained in the Suppressing Warnings and Errors section.
+
+
+RtlCompat
+
+Disabled By: Project lint.xml file
+
++
+API 17 adds a
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "RtlCompat" as explained in the Suppressing Warnings and Errors section.
+
+textAlignment attribute to specify text alignment. However, if you are supporting older versions than API 17, you must also specify a gravity or layout_gravity attribute, since older platforms will ignore the textAlignment attribute.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "RtlCompat" as explained in the Suppressing Warnings and Errors section.
+
+
+RtlEnabled
+
+Disabled By: Project lint.xml file
+
++
+To enable right-to-left support, when running on API 17 and higher, you must set the
+
+If you have started adding RTL attributes, but have not yet finished the migration, you can set the attribute to false to satisfy this lint check.
To suppress this error, use the issue id "RtlEnabled" as explained in the Suppressing Warnings and Errors section.
+
+android:supportsRtl attribute in the manifest <application> element.+
+If you have started adding RTL attributes, but have not yet finished the migration, you can set the attribute to false to satisfy this lint check.
To suppress this error, use the issue id "RtlEnabled" as explained in the Suppressing Warnings and Errors section.
+
+
+RtlHardcoded
+
+Disabled By: Project lint.xml file
+
++
+Using
+
+For XML attributes such as paddingLeft and
+
+(Note: For
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "RtlHardcoded" as explained in the Suppressing Warnings and Errors section.
+
+Gravity#LEFT and Gravity#RIGHT can lead to problems when a layout is rendered in locales where text flows from right to left. Use Gravity#START and Gravity#END instead. Similarly, in XML gravity and layout_gravity attributes, use start rather than left.+
+For XML attributes such as paddingLeft and
layout_marginLeft, use paddingStart and layout_marginStart. NOTE: If your minSdkVersion is less than 17, you should add both the older left/right attributes as well as the new start/right attributes. On older platforms, where RTL is not supported and the start/right attributes are unknown and therefore ignored, you need the older left/right attributes. There is a separate lint check which catches that type of error.+
+(Note: For
Gravity#LEFT and Gravity#START, you can use these constants even when targeting older platforms, because the start bitmask is a superset of the left bitmask. Therefore, you can use gravity="start" rather than gravity="left|start".)Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "RtlHardcoded" as explained in the Suppressing Warnings and Errors section.
+
+
+RtlSymmetry
+
+Disabled By: Project lint.xml file
+
++
+If you specify padding or margin on the left side of a layout, you should probably also specify padding on the right side (and vice versa) for right-to-left layout symmetry.
To suppress this error, use the issue id "RtlSymmetry" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "RtlSymmetry" as explained in the Suppressing Warnings and Errors section.
+
+
+SQLiteString
+
+Disabled By: Project lint.xml file
+
++
+In SQLite, any column can store any data type; the declared type for a column is more of a hint as to what the data should be cast to when stored.
+
+There are many ways to store a string.
+
+If you try to store a value in a numeric column, SQLite will try to cast it to a float or an integer before storing. If it can't, it will just store it as a string.
+
+This can lead to some subtle bugs. For example, when SQLite encounters a string like
+
+To fix this, you can change your schema to use a
+
++
+There are many ways to store a string.
TEXT, VARCHAR, CHARACTER and CLOB are string types, but `STRING` is not. Columns defined as STRING are actually numeric.+
+If you try to store a value in a numeric column, SQLite will try to cast it to a float or an integer before storing. If it can't, it will just store it as a string.
+
+This can lead to some subtle bugs. For example, when SQLite encounters a string like
1234567e1234, it will parse it as a float, but the result will be out of range for floating point numbers, so Inf will be stored! Similarly, strings that look like integers will lose leading zeroes.+
+To fix this, you can change your schema to use a
TEXT type instead.More info: https://www.sqlite.org/datatype3.html
+
To suppress this error, use the issue id "SQLiteString" as explained in the Suppressing Warnings and Errors section.+
+
+SSLCertificateSocketFactoryCreateSocket
+
+Disabled By: Project lint.xml file
+
++
+When
To suppress this error, use the issue id "SSLCertificateSocketFactoryCreateSocket" as explained in the Suppressing Warnings and Errors section.
+
+SSLCertificateSocketFactory.createSocket() is called with an InetAddress as the first parameter, TLS/SSL hostname verification is not performed, which could result in insecure network traffic caused by trusting arbitrary hostnames in TLS/SSL certificates presented by peers. In this case, developers must ensure that the InetAddress is explicitly verified against the certificate through other means, such as by calling `SSLCertificateSocketFactory.getDefaultHostnameVerifier() to get a HostnameVerifier and calling HostnameVerifier.verify().To suppress this error, use the issue id "SSLCertificateSocketFactoryCreateSocket" as explained in the Suppressing Warnings and Errors section.
+
+
+SSLCertificateSocketFactoryGetInsecure
+
+Disabled By: Project lint.xml file
+
++
+The
To suppress this error, use the issue id "SSLCertificateSocketFactoryGetInsecure" as explained in the Suppressing Warnings and Errors section.
+
+SSLCertificateSocketFactory.getInsecure() method returns an SSLSocketFactory with all TLS/SSL security checks disabled, which could result in insecure network traffic caused by trusting arbitrary TLS/SSL certificates presented by peers. This method should be avoided unless needed for a special circumstance such as debugging. Instead, SSLCertificateSocketFactory.getDefault() should be used.To suppress this error, use the issue id "SSLCertificateSocketFactoryGetInsecure" as explained in the Suppressing Warnings and Errors section.
+
+
+ScrollViewCount
+
+Disabled By: Project lint.xml file
+
++
+ScrollViews can only have one child widget. If you want more children, wrap them in a container layout.
To suppress this error, use the issue id "ScrollViewCount" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "ScrollViewCount" as explained in the Suppressing Warnings and Errors section.
+
+
+ScrollViewSize
+
+Disabled By: Project lint.xml file
+
++
+ScrollView children must set their
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ScrollViewSize" as explained in the Suppressing Warnings and Errors section.
+
+layout_width or layout_height attributes to wrap_content rather than fill_parent or match_parent in the scrolling dimensionNote: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ScrollViewSize" as explained in the Suppressing Warnings and Errors section.
+
+
+SdCardPath
+
+Disabled By: Project lint.xml file
+
++
+Your code should not reference the
+
+Similarly, do not reference the
To suppress this error, use the issue id "SdCardPath" as explained in the Suppressing Warnings and Errors section.
+
+/sdcard path directly; instead use Environment.getExternalStorageDirectory().getPath().+
+Similarly, do not reference the
/data/data/ path directly; it can vary in multi-user scenarios. Instead, use Context.getFilesDir().getPath().To suppress this error, use the issue id "SdCardPath" as explained in the Suppressing Warnings and Errors section.
+
+
+SecureRandom
+
+Disabled By: Project lint.xml file
+
++
+Specifying a fixed seed will cause the instance to return a predictable sequence of numbers. This may be useful for testing but it is not appropriate for secure use.
To suppress this error, use the issue id "SecureRandom" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "SecureRandom" as explained in the Suppressing Warnings and Errors section.
+
+
+SelectableText
+
+Disabled By: Default
+
++
+If a
+
+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
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "SelectableText" as explained in the Suppressing Warnings and Errors section.
+
+<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.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "SelectableText" as explained in the Suppressing Warnings and Errors section.
+
+
+ServiceCast
+
+Disabled By: Project lint.xml file
+
++
+When you call
To suppress this error, use the issue id "ServiceCast" as explained in the Suppressing Warnings and Errors section.
+
+Context#getSystemService(), the result is typically cast to a specific interface. This lint check ensures that the cast is compatible with the expected type of the return value.To suppress this error, use the issue id "ServiceCast" as explained in the Suppressing Warnings and Errors section.
+
+
+SetJavaScriptEnabled
+
+Disabled By: Project lint.xml file
+
++
+Your code should not invoke
To suppress this error, use the issue id "SetJavaScriptEnabled" as explained in the Suppressing Warnings and Errors section.
+
+setJavaScriptEnabled if you are not sure that your app really requires JavaScript support.To suppress this error, use the issue id "SetJavaScriptEnabled" as explained in the Suppressing Warnings and Errors section.
+
+
+SetTextI18n
+
+Disabled By: Project lint.xml file
+
++
+When calling
+* Never call
+* Do not pass a string literal (e.g. "Hello") to display text. Hardcoded text can not be properly translated to other languages. Consider using Android resource strings instead.
+* Do not build messages by concatenating text chunks. Such messages can not be properly translated.
To suppress this error, use the issue id "SetTextI18n" as explained in the Suppressing Warnings and Errors section.
+
+TextView#setText+* Never call
Number#toString() to format numbers; it will not handle fraction separators and locale-specific digits properly. Consider using String#format with proper format specifications (%d or %f) instead.+* Do not pass a string literal (e.g. "Hello") to display text. Hardcoded text can not be properly translated to other languages. Consider using Android resource strings instead.
+* Do not build messages by concatenating text chunks. Such messages can not be properly translated.
To suppress this error, use the issue id "SetTextI18n" as explained in the Suppressing Warnings and Errors section.
+
+
+SetWorldReadable
+
+Disabled By: Project lint.xml file
+
++
+Setting files world-readable is very dangerous, and likely to cause security holes in applications. It is strongly discouraged; instead, applications should use more formal mechanisms for interactions such as
To suppress this error, use the issue id "SetWorldReadable" as explained in the Suppressing Warnings and Errors section.
+
+ContentProvider, BroadcastReceiver, and Service.To suppress this error, use the issue id "SetWorldReadable" as explained in the Suppressing Warnings and Errors section.
+
+
+SetWorldWritable
+
+Disabled By: Project lint.xml file
+
++
+Setting files world-writable is very dangerous, and likely to cause security holes in applications. It is strongly discouraged; instead, applications should use more formal mechanisms for interactions such as
To suppress this error, use the issue id "SetWorldWritable" as explained in the Suppressing Warnings and Errors section.
+
+ContentProvider, BroadcastReceiver, and Service.To suppress this error, use the issue id "SetWorldWritable" as explained in the Suppressing Warnings and Errors section.
+
+
+ShiftFlags
+
+Disabled By: Project lint.xml file
+
++
+When defining multiple constants for use in flags, the recommended style is to use the form
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ShiftFlags" as explained in the Suppressing Warnings and Errors section.
+
+1 << 2, 1 << 3, 1 << 4 and so on to ensure that the constants are unique and non-overlapping.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "ShiftFlags" as explained in the Suppressing Warnings and Errors section.
+
+
+ShortAlarm
+
+Disabled By: Project lint.xml file
+
++
+Frequent alarms are bad for battery life. As of API 22, the
+
+If you really need to do work sooner than 5 seconds, post a delayed message or runnable to a Handler.
To suppress this error, use the issue id "ShortAlarm" as explained in the Suppressing Warnings and Errors section.
+
+AlarmManager will override near-future and high-frequency alarm requests, delaying the alarm at least 5 seconds into the future and ensuring that the repeat interval is at least 60 seconds.+
+If you really need to do work sooner than 5 seconds, post a delayed message or runnable to a Handler.
To suppress this error, use the issue id "ShortAlarm" as explained in the Suppressing Warnings and Errors section.
+
+
+ShowToast
+
+Disabled By: Project lint.xml file
+
++
+
To suppress this error, use the issue id "ShowToast" as explained in the Suppressing Warnings and Errors section.
+
+Toast.makeText() creates a Toast but does not show it. You must call show() on the resulting object to actually make the Toast appear.To suppress this error, use the issue id "ShowToast" as explained in the Suppressing Warnings and Errors section.
+
+
+SignatureOrSystemPermissions
+
+Disabled By: Project lint.xml file
+
++
+The
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "SignatureOrSystemPermissions" as explained in the Suppressing Warnings and Errors section.
+
+signature protection level should probably be sufficient for most needs and works regardless of where applications are installed. The signatureOrSystem level is used for certain situations where multiple vendors have applications built into a system image and need to share specific features explicitly because they are being built together.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "SignatureOrSystemPermissions" as explained in the Suppressing Warnings and Errors section.
+
+
+SimpleDateFormat
+
+Disabled By: Project lint.xml file
+
++
+Almost all callers should use
+
+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.
To suppress this error, use the issue id "SimpleDateFormat" as explained in the Suppressing Warnings and Errors section.
+
+getDateInstance(), getDateTimeInstance(), or getTimeInstance() 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).+
+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.
To suppress this error, use the issue id "SimpleDateFormat" as explained in the Suppressing Warnings and Errors section.
+
+
+SmallSp
+
+Disabled By: Project lint.xml file
+
++
+Avoid using sizes smaller than 12sp.
To suppress this error, use the issue id "SmallSp" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "SmallSp" as explained in the Suppressing Warnings and Errors section.
+
+
+SpUsage
+
+Disabled By: Project lint.xml file
+
++
+When setting text sizes, you should normally use
+
+There are cases where you might need to use
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "SpUsage" as explained in the Suppressing Warnings and Errors section.
+
+sp, or "scale-independent pixels". This is like the dp unit, but it is also scaled by the user's font size preference. It is recommend you use this unit when specifying font sizes, so they will be adjusted for both the screen density and the user's preference.+
+There are cases where you might need to use
dp; typically this happens when the text is in a container with a specific dp-size. This will prevent the text from spilling outside the container. Note however that this means that the user's font size settings are not respected, so consider adjusting the layout itself to be more flexible.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "SpUsage" as explained in the Suppressing Warnings and Errors section.
+
+
+StateListReachable
+
+Disabled By: Project lint.xml file
+
++
+In a selector, only the last child in the state list should omit a state qualifier. If not, all subsequent items in the list will be ignored since the given item will match all.
To suppress this error, use the issue id "StateListReachable" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "StateListReachable" as explained in the Suppressing Warnings and Errors section.
+
+
+StaticFieldLeak
+
+Disabled By: Project lint.xml file
+
++
+A static field will leak contexts.
+
+Non-static inner classes have an implicit reference to their outer class. If that outer class is for example a
+
+Similarly, direct field references to activities and fragments from these longer running instances can cause leaks.
+
+ViewModel classes should never point to Views or non-application Contexts.
To suppress this error, use the issue id "StaticFieldLeak" as explained in the Suppressing Warnings and Errors section.
+
++
+Non-static inner classes have an implicit reference to their outer class. If that outer class is for example a
Fragment or Activity, then this reference means that the long-running handler/loader/task will hold a reference to the activity which prevents it from getting garbage collected.+
+Similarly, direct field references to activities and fragments from these longer running instances can cause leaks.
+
+ViewModel classes should never point to Views or non-application Contexts.
To suppress this error, use the issue id "StaticFieldLeak" as explained in the Suppressing Warnings and Errors section.
+
+
+StopShip
+
+Disabled By: Default
+
++
+Using the comment
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "StopShip" as explained in the Suppressing Warnings and Errors section.
+
+// 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. In Gradle projects, this is only checked for non-debug (release) builds.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "StopShip" as explained in the Suppressing Warnings and Errors section.
+
+
+StringEscaping
+
+Disabled By: Project lint.xml file
+
++
+Apostrophes (') must always be escaped (with a \), unless they appear in a string which is itself escaped in double quotes (").
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "StringEscaping" as explained in the Suppressing Warnings and Errors section.
+
+Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "StringEscaping" as explained in the Suppressing Warnings and Errors section.
+
+
+StringFormatCount
+
+Disabled By: Project lint.xml file
+
++
+When a formatted string takes arguments, it usually needs to reference the same arguments in all translations (or all arguments if there are no translations.
+
+There are cases where this is not the case, so this issue is a warning rather than an error by default. However, this usually happens when a language is not translated or updated correctly.
To suppress this error, use the issue id "StringFormatCount" as explained in the Suppressing Warnings and Errors section.
+
++
+There are cases where this is not the case, so this issue is a warning rather than an error by default. However, this usually happens when a language is not translated or updated correctly.
To suppress this error, use the issue id "StringFormatCount" as explained in the Suppressing Warnings and Errors section.
+
+
+StringFormatInvalid
+
+Disabled By: Project lint.xml file
+
++
+If a string contains a '%' character, then the string may be a formatting string which will be passed to
+
+This lint warning checks for two related problems:
+(1) Formatting strings that are invalid, meaning that
+(2) Strings containing '%' that are not formatting strings getting passed to a
+
+NOTE: Not all Strings which look like formatting strings are intended for use by
To suppress this error, use the issue id "StringFormatInvalid" as explained in the Suppressing Warnings and Errors section.
+
+String.format from Java code to replace each '%' occurrence with specific values.+
+This lint warning checks for two related problems:
+(1) Formatting strings that are invalid, meaning that
String.format will throw exceptions at runtime when attempting to use the format string.+(2) Strings containing '%' that are not formatting strings getting passed to a
String.format call. In this case the '%' will need to be escaped as '%%'.+
+NOTE: Not all Strings which look like formatting strings are intended for use by
String.format; for example, they may contain date formats intended for android.text.format.Time#format(). Lint cannot always figure out that a String is a date format, so you may get false warnings in those scenarios. See the suppress help topic for information on how to suppress errors in that case.To suppress this error, use the issue id "StringFormatInvalid" as explained in the Suppressing Warnings and Errors section.
+
+
+StringFormatMatches
+
+Disabled By: Project lint.xml file
+
++
+This lint check ensures the following:
+(1) If there are multiple translations of the format string, then all translations use the same type for the same numbered arguments
+(2) The usage of the format string in Java is consistent with the format string, meaning that the parameter types passed to String.format matches those in the format string.
To suppress this error, use the issue id "StringFormatMatches" as explained in the Suppressing Warnings and Errors section.
+
++(1) If there are multiple translations of the format string, then all translations use the same type for the same numbered arguments
+(2) The usage of the format string in Java is consistent with the format string, meaning that the parameter types passed to String.format matches those in the format string.
To suppress this error, use the issue id "StringFormatMatches" as explained in the Suppressing Warnings and Errors section.
+
+
+StringShouldBeInt
+
+Disabled By: Project lint.xml file
+
++
+The properties
+
+However, you can not use a number as a string (e.g. "19" instead of 19); that will result in a platform not found error message at build/sync time.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "StringShouldBeInt" as explained in the Suppressing Warnings and Errors section.
+
+compileSdkVersion, minSdkVersion and targetSdkVersion are usually numbers, but can be strings when you are using an add-on (in the case of compileSdkVersion) or a preview platform (for the other two properties).+
+However, you can not use a number as a string (e.g. "19" instead of 19); that will result in a platform not found error message at build/sync time.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "StringShouldBeInt" as explained in the Suppressing Warnings and Errors section.
+
+
+SupportAnnotationUsage
+
+Disabled By: Project lint.xml file
+
++
+This lint check makes sure that the support annotations (such as
To suppress this error, use the issue id "SupportAnnotationUsage" as explained in the Suppressing Warnings and Errors section.
+
+@IntDef and @ColorInt) are used correctly. For example, it's an error to specify an @IntRange where the from value is higher than the to value.To suppress this error, use the issue id "SupportAnnotationUsage" as explained in the Suppressing Warnings and Errors section.
+
+
+Suspicious0dp
+
+Disabled By: Project lint.xml file
+
++
+Using 0dp as the width in a horizontal LinearLayout with weights is a useful trick to ensure that only the weights (and not the intrinsic sizes) are used when sizing the children.
+
+However, if you use 0dp for the opposite dimension, the view will be invisible. This can happen if you change the orientation of a layout without also flipping the 0dp dimension in all the children.
To suppress this error, use the issue id "Suspicious0dp" as explained in the Suppressing Warnings and Errors section.
+
++
+However, if you use 0dp for the opposite dimension, the view will be invisible. This can happen if you change the orientation of a layout without also flipping the 0dp dimension in all the children.
To suppress this error, use the issue id "Suspicious0dp" as explained in the Suppressing Warnings and Errors section.
+
+
+SuspiciousImport
+
+Disabled By: Project lint.xml file
+
++
+Importing
+
+Once the import is there you might get a lot of "confusing" error messages because of course the fields available on
To suppress this error, use the issue id "SuspiciousImport" as explained in the Suppressing Warnings and Errors section.
+
+android.R is usually not intentional; it sometimes happens when you use an IDE and ask it to automatically add imports at a time when your project's R class it not present.+
+Once the import is there you might get a lot of "confusing" error messages because of course the fields available on
android.R are not the ones you'd expect from just looking at your own R class.To suppress this error, use the issue id "SuspiciousImport" as explained in the Suppressing Warnings and Errors section.
+
+
+SwitchIntDef
+
+Disabled By: Project lint.xml file
+
++
+This check warns if a
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "SwitchIntDef" as explained in the Suppressing Warnings and Errors section.
+
+switch statement does not explicitly include all the values declared by the typedef @IntDef declaration.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "SwitchIntDef" as explained in the Suppressing Warnings and Errors section.
+
+
+TextFields
+
+Disabled By: Project lint.xml file
+
++
+Providing an
+
+The lint detector also looks at the
+
+If you really want to keep the text field generic, you can suppress this warning by setting
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "TextFields" as explained in the Suppressing Warnings and Errors section.
+
+inputType attribute on a text field improves usability because depending on the data to be input, optimized keyboards can be shown to the user (such as just digits and parentheses for a phone number). +
+The lint detector also looks at the
id of the view, and if the id offers a hint of the purpose of the field (for example, the id contains the phrase phone or email), then lint will also ensure that the inputType contains the corresponding type attributes.+
+If you really want to keep the text field generic, you can suppress this warning by setting
inputType="text".Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "TextFields" as explained in the Suppressing Warnings and Errors section.
+
+
+TextViewEdits
+
+Disabled By: Project lint.xml file
+
++
+Using a
+
+This check also checks subclasses of
To suppress this error, use the issue id "TextViewEdits" as explained in the Suppressing Warnings and Errors section.
+
+<TextView> to input text is generally an error, you should be using <EditText> instead. EditText is a subclass of TextView, and some of the editing support is provided by TextView, so it's possible to set some input-related properties on a TextView. However, using a TextView along with input attributes is usually a cut & paste error. To input text you should be using <EditText>.+
+This check also checks subclasses of
TextView, such as Button and CheckBox, since these have the same issue: they should not be used with editable attributes.To suppress this error, use the issue id "TextViewEdits" as explained in the Suppressing Warnings and Errors section.
+
+
+TooDeepLayout
+
+Disabled By: Project lint.xml file
+
++
+Layouts with too much nesting is bad for performance. Consider using a flatter layout (such as
To suppress this error, use the issue id "TooDeepLayout" as explained in the Suppressing Warnings and Errors section.
+
+RelativeLayout or GridLayout).The default maximum depth is 10 but can be configured with the environment variable ANDROID_LINT_MAX_DEPTH.To suppress this error, use the issue id "TooDeepLayout" as explained in the Suppressing Warnings and Errors section.
+
+
+TooManyViews
+
+Disabled By: Project lint.xml file
+
++
+Using too many views in a single layout is bad for performance. Consider using compound drawables or other tricks for reducing the number of views in this layout.
+
+The maximum view count defaults to 80 but can be configured with the environment variable
To suppress this error, use the issue id "TooManyViews" as explained in the Suppressing Warnings and Errors section.
+
++
+The maximum view count defaults to 80 but can be configured with the environment variable
ANDROID_LINT_MAX_VIEW_COUNT.To suppress this error, use the issue id "TooManyViews" as explained in the Suppressing Warnings and Errors section.
+
+
+TrulyRandom
+
+Disabled By: Project lint.xml file
+
++
+Key generation, signing, encryption, and random number generation may not receive cryptographically strong values due to improper initialization of the underlying PRNG on Android 4.3 and below.
+
+If your application relies on cryptographically secure random number generation you should apply the workaround described in https://android-developers.blogspot.com/2013/08/some-securerandom-thoughts.html .
+
+This lint rule is mostly informational; it does not accurately detect whether cryptographically secure RNG is required, or whether the workaround has already been applied. After reading the blog entry and updating your code if necessary, you can disable this lint issue.
To suppress this error, use the issue id "TrulyRandom" as explained in the Suppressing Warnings and Errors section.
+
++
+If your application relies on cryptographically secure random number generation you should apply the workaround described in https://android-developers.blogspot.com/2013/08/some-securerandom-thoughts.html .
+
+This lint rule is mostly informational; it does not accurately detect whether cryptographically secure RNG is required, or whether the workaround has already been applied. After reading the blog entry and updating your code if necessary, you can disable this lint issue.
To suppress this error, use the issue id "TrulyRandom" as explained in the Suppressing Warnings and Errors section.
+
+
+TrustAllX509TrustManager
+
+Disabled By: Project lint.xml file
+
++
+This check looks for X509TrustManager implementations whose
To suppress this error, use the issue id "TrustAllX509TrustManager" as explained in the Suppressing Warnings and Errors section.
+
+checkServerTrusted or checkClientTrusted methods do nothing (thus trusting any certificate chain) which could result in insecure network traffic caused by trusting arbitrary TLS/SSL certificates presented by peers.To suppress this error, use the issue id "TrustAllX509TrustManager" as explained in the Suppressing Warnings and Errors section.
+
+
+TypographyDashes
+
+Disabled By: Project lint.xml file
+
++
+The "n dash" (–, –) and the "m dash" (—, —) characters are used for ranges (n dash) and breaks (m dash). Using these instead of plain hyphens can make text easier to read and your application will look more polished.
+To suppress this error, use the issue id "TypographyDashes" as explained in the Suppressing Warnings and Errors section.
+
+More info: http://en.wikipedia.org/wiki/Dash
+
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.+To suppress this error, use the issue id "TypographyDashes" as explained in the Suppressing Warnings and Errors section.
+
+
+TypographyEllipsis
+
+Disabled By: Project lint.xml file
+
++
+You can replace the string "..." with a dedicated ellipsis character, ellipsis character (…, …). This can help make the text more readable.
+To suppress this error, use the issue id "TypographyEllipsis" as explained in the Suppressing Warnings and Errors section.
+
+More info: http://en.wikipedia.org/wiki/Ellipsis
+
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.+To suppress this error, use the issue id "TypographyEllipsis" as explained in the Suppressing Warnings and Errors section.
+
+
+TypographyFractions
+
+Disabled By: Project lint.xml file
+
++
+You can replace certain strings, such as 1/2, and 1/4, with dedicated characters for these, such as ½ (½) and ¼ (¼). This can help make the text more readable.
+To suppress this error, use the issue id "TypographyFractions" as explained in the Suppressing Warnings and Errors section.
+
+More info: http://en.wikipedia.org/wiki/Number_Forms
+
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.+To suppress this error, use the issue id "TypographyFractions" as explained in the Suppressing Warnings and Errors section.
+
+
+TypographyOther
+
+Disabled By: Project lint.xml file
+
++
+This check looks for miscellaneous typographical problems and offers replacement sequences that will make the text easier to read and your application more polished.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "TypographyOther" as explained in the Suppressing Warnings and Errors section.
+
+Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "TypographyOther" as explained in the Suppressing Warnings and Errors section.
+
+
+TypographyQuotes
+
+Disabled By: Default
+
++
+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.
+
++
+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
+
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.+To suppress this error, use the issue id "TypographyQuotes" as explained in the Suppressing Warnings and Errors section.
+
+
+Typos
+
+Disabled By: Project lint.xml file
+
++
+This check looks through the string definitions, and if it finds any words that look like likely misspellings, they are flagged.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "Typos" as explained in the Suppressing Warnings and Errors section.
+
+Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "Typos" as explained in the Suppressing Warnings and Errors section.
+
+
+UniqueConstants
+
+Disabled By: Project lint.xml file
+
++
+The
+
+In some cases, the repeated constant is intentional (for example, renaming a constant to a more intuitive name, and leaving the old name in place for compatibility purposes). In that case, simply suppress this check by adding a
To suppress this error, use the issue id "UniqueConstants" as explained in the Suppressing Warnings and Errors section.
+
+@IntDef annotation allows you to create a light-weight "enum" or type definition. However, it's possible to accidentally specify the same value for two or more of the values, which can lead to hard-to-detect bugs. This check looks for this scenario and flags any repeated constants.+
+In some cases, the repeated constant is intentional (for example, renaming a constant to a more intuitive name, and leaving the old name in place for compatibility purposes). In that case, simply suppress this check by adding a
@SuppressLint("UniqueConstants") annotation.To suppress this error, use the issue id "UniqueConstants" as explained in the Suppressing Warnings and Errors section.
+
+
+UnknownIdInLayout
+
+Disabled By: Project lint.xml file
+
++
+The
+
+This is sometimes intentional, for example where you are referring to a view which is provided in a different layout via an include. However, it is usually an accident where you have a typo or you have renamed a view without updating all the references to it.
To suppress this error, use the issue id "UnknownIdInLayout" as explained in the Suppressing Warnings and Errors section.
+
+@+id/ syntax refers to an existing id, or creates a new one if it has not already been defined elsewhere. However, this means that if you have a typo in your reference, or if the referred view no longer exists, you do not get a warning since the id will be created on demand.+
+This is sometimes intentional, for example where you are referring to a view which is provided in a different layout via an include. However, it is usually an accident where you have a typo or you have renamed a view without updating all the references to it.
To suppress this error, use the issue id "UnknownIdInLayout" as explained in the Suppressing Warnings and Errors section.
+
+
+UnlocalizedSms
+
+Disabled By: Project lint.xml file
+
++
+SMS destination numbers must start with a country code or the application code must ensure that the SMS is only sent when the user is in the same country as the receiver.
To suppress this error, use the issue id "UnlocalizedSms" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "UnlocalizedSms" as explained in the Suppressing Warnings and Errors section.
+
+
+UnpackedNativeCode
+
+Disabled By: Default
+
++
+This app loads native libraries using
+
+Consider adding
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UnpackedNativeCode" as explained in the Suppressing Warnings and Errors section.
+
+System.loadLibrary().+
+Consider adding
android:extractNativeLibs="false" to the <application> tag in AndroidManifest.xml. Starting with Android 6.0, this will make installation faster, the app will take up less space on the device and updates will have smaller download sizes.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UnpackedNativeCode" as explained in the Suppressing Warnings and Errors section.
+
+
+UnprotectedSMSBroadcastReceiver
+
+Disabled By: Project lint.xml file
+
++
+BroadcastReceivers that declare an intent-filter for SMS_DELIVER or SMS_RECEIVED must ensure that the caller has the BROADCAST_SMS permission, otherwise it is possible for malicious actors to spoof intents.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UnprotectedSMSBroadcastReceiver" as explained in the Suppressing Warnings and Errors section.
+
+Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UnprotectedSMSBroadcastReceiver" as explained in the Suppressing Warnings and Errors section.
+
+
+UnsafeDynamicallyLoadedCode
+
+Disabled By: Project lint.xml file
+
++
+Dynamically loading code from locations other than the application's library directory or the Android platform's built-in library directories is dangerous, as there is an increased risk that the code could have been tampered with. Applications should use
To suppress this error, use the issue id "UnsafeDynamicallyLoadedCode" as explained in the Suppressing Warnings and Errors section.
+
+loadLibrary when possible, which provides increased assurance that libraries are loaded from one of these safer locations. Application developers should use the features of their development environment to place application native libraries into the lib directory of their compiled APKs.To suppress this error, use the issue id "UnsafeDynamicallyLoadedCode" as explained in the Suppressing Warnings and Errors section.
+
+
+UnsafeNativeCodeLocation
+
+Disabled By: Project lint.xml file
+
++
+In general, application native code should only be placed in the application's library directory, not in other locations such as the res or assets directories. Placing the code in the library directory provides increased assurance that the code will not be tampered with after application installation. Application developers should use the features of their development environment to place application native libraries into the lib directory of their compiled APKs. Embedding non-shared library native executables into applications should be avoided when possible.
To suppress this error, use the issue id "UnsafeNativeCodeLocation" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "UnsafeNativeCodeLocation" as explained in the Suppressing Warnings and Errors section.
+
+
+UnsafeProtectedBroadcastReceiver
+
+Disabled By: Project lint.xml file
+
++
+BroadcastReceivers that declare an intent-filter for a protected-broadcast action string must check that the received intent's action string matches the expected value, otherwise it is possible for malicious actors to spoof intents.
To suppress this error, use the issue id "UnsafeProtectedBroadcastReceiver" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "UnsafeProtectedBroadcastReceiver" as explained in the Suppressing Warnings and Errors section.
+
+
+UnsupportedChromeOsHardware
+
+Disabled By: Default
+
++
+The
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UnsupportedChromeOsHardware" as explained in the Suppressing Warnings and Errors section.
+
+<uses-feature> element should not require this unsupported Chrome OS hardware feature. Any uses-feature not explicitly marked with required="false" is necessary on the device to be installed on. Ensure that any features that might prevent it from being installed on a Chrome OS device are reviewed and marked as not required in the manifest.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UnsupportedChromeOsHardware" as explained in the Suppressing Warnings and Errors section.
+
+
+UnsupportedTvHardware
+
+Disabled By: Project lint.xml file
+
++
+The <uses-feature> element should not require this unsupported TV hardware feature. Any uses-feature not explicitly marked with required="false" is necessary on the device to be installed on. Ensure that any features that might prevent it from being installed on a TV device are reviewed and marked as not required in the manifest.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UnsupportedTvHardware" as explained in the Suppressing Warnings and Errors section.
+
+Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UnsupportedTvHardware" as explained in the Suppressing Warnings and Errors section.
+
+
+UnusedAttribute
+
+Disabled By: Project lint.xml file
+
++
+This check finds attributes set in XML files that were introduced in a version newer than the oldest version targeted by your application (with the
+
+This is not an error; the application will simply ignore the attribute. However, if the attribute is important to the appearance or functionality of your application, you should consider finding an alternative way to achieve the same result with only available attributes, and then you can optionally create a copy of the layout in a layout-vNN folder which will be used on API NN or higher where you can take advantage of the newer attribute.
+
+Note: This check does not only apply to attributes. For example, some tags can be unused too, such as the new
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UnusedAttribute" as explained in the Suppressing Warnings and Errors section.
+
+minSdkVersion attribute).+
+This is not an error; the application will simply ignore the attribute. However, if the attribute is important to the appearance or functionality of your application, you should consider finding an alternative way to achieve the same result with only available attributes, and then you can optionally create a copy of the layout in a layout-vNN folder which will be used on API NN or higher where you can take advantage of the newer attribute.
+
+Note: This check does not only apply to attributes. For example, some tags can be unused too, such as the new
<tag> element in layouts introduced in API 21.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UnusedAttribute" as explained in the Suppressing Warnings and Errors section.
+
+
+UnusedIds
+
+Disabled By: Default
+
++
+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.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UnusedIds" as explained in the Suppressing Warnings and Errors section.
+
+Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UnusedIds" as explained in the Suppressing Warnings and Errors section.
+
+
+UnusedNamespace
+
+Disabled By: Project lint.xml file
+
++
+Unused namespace declarations take up space and require processing that is not necessary
To suppress this error, use the issue id "UnusedNamespace" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "UnusedNamespace" as explained in the Suppressing Warnings and Errors section.
+
+
+UnusedQuantity
+
+Disabled By: Project lint.xml file
+
++
+Android defines a number of different quantity strings, such as
+
+This lint check looks at the quantity strings defined for each translation and flags any quantity strings that are unused (because the language does not make that quantity distinction, and Android will therefore not look it up).
+
+For example, in Chinese, only the
To suppress this error, use the issue id "UnusedQuantity" as explained in the Suppressing Warnings and Errors section.
+
+zero, one, few and many. However, many languages do not distinguish grammatically between all these different quantities.+
+This lint check looks at the quantity strings defined for each translation and flags any quantity strings that are unused (because the language does not make that quantity distinction, and Android will therefore not look it up).
+
+For example, in Chinese, only the
other quantity is used, so even if you provide translations for zero and one, these strings will not be returned when getQuantityString() is called, even with 0 or 1.To suppress this error, use the issue id "UnusedQuantity" as explained in the Suppressing Warnings and Errors section.
+
+
+UnusedResources
+
+Disabled By: Project lint.xml file
+
++
+Unused resources make applications larger and slow down builds.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UnusedResources" as explained in the Suppressing Warnings and Errors section.
+
+Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UnusedResources" as explained in the Suppressing Warnings and Errors section.
+
+
+UseAlpha2
+
+Disabled By: Project lint.xml file
+
++
+For compatibility with earlier devices, you should only use 3-letter language and region codes when there is no corresponding 2 letter code.
+
+More info: https://tools.ietf.org/html/bcp47
+
To suppress this error, use the issue id "UseAlpha2" as explained in the Suppressing Warnings and Errors section.+
+
+UseCheckPermission
+
+Disabled By: Project lint.xml file
+
++
+You normally want to use the result of checking a permission; these methods return whether the permission is held; they do not throw an error if the permission is not granted. Code which does not do anything with the return value probably meant to be calling the enforce methods instead, e.g. rather than
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UseCheckPermission" as explained in the Suppressing Warnings and Errors section.
+
+Context#checkCallingPermission it should call Context#enforceCallingPermission.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UseCheckPermission" as explained in the Suppressing Warnings and Errors section.
+
+
+UseCompoundDrawables
+
+Disabled By: Project lint.xml file
+
++
+A
+
+If the two widgets are offset from each other with margins, this can be replaced with a
+
+There's a lint quickfix to perform this conversion in the Eclipse plugin.
To suppress this error, use the issue id "UseCompoundDrawables" as explained in the Suppressing Warnings and Errors section.
+
+LinearLayout which contains an ImageView and a TextView can be more efficiently handled as a compound drawable (a single TextView, using the drawableTop, drawableLeft, drawableRight and/or drawableBottom attributes to draw one or more images adjacent to the text).+
+If the two widgets are offset from each other with margins, this can be replaced with a
drawablePadding attribute.+
+There's a lint quickfix to perform this conversion in the Eclipse plugin.
To suppress this error, use the issue id "UseCompoundDrawables" as explained in the Suppressing Warnings and Errors section.
+
+
+UseOfBundledGooglePlayServices
+
+Disabled By: Project lint.xml file
+
++
+Google Play services SDK's can be selectively included, which enables a smaller APK size. Consider declaring dependencies on individual Google Play services SDK's. If you are using Firebase API's (http://firebase.google.com/docs/android/setup), Android Studio's Tools → Firebase assistant window can automatically add just the dependencies needed for each feature.
To suppress this error, use the issue id "UseOfBundledGooglePlayServices" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "UseOfBundledGooglePlayServices" as explained in the Suppressing Warnings and Errors section.
+
+
+UseSparseArrays
+
+Disabled By: Project lint.xml file
+
++
+For maps where the keys are of type integer, it's typically more efficient to use the Android
+
+This is particularly useful when the value types are primitives like ints, where you can use
+
+If you need to construct a
To suppress this error, use the issue id "UseSparseArrays" as explained in the Suppressing Warnings and Errors section.
+
+SparseArray API. This check identifies scenarios where you might want to consider using SparseArray instead of HashMap for better performance.+
+This is particularly useful when the value types are primitives like ints, where you can use
SparseIntArray and avoid auto-boxing the values from int to Integer.+
+If you need to construct a
HashMap because you need to call an API outside of your control which requires a Map, you can suppress this warning using for example the @SuppressLint annotation.To suppress this error, use the issue id "UseSparseArrays" as explained in the Suppressing Warnings and Errors section.
+
+
+UseValueOf
+
+Disabled By: Project lint.xml file
+
++
+You should not call the constructor for wrapper classes directly, such as`new Integer(42)`. Instead, call the
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UseValueOf" as explained in the Suppressing Warnings and Errors section.
+
+valueOf factory method, such as Integer.valueOf(42). This will typically use less memory because common integers such as 0 and 1 will share a single instance.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UseValueOf" as explained in the Suppressing Warnings and Errors section.
+
+
+UselessLeaf
+
+Disabled By: Project lint.xml file
+
++
+A layout that has no children or no background can often be removed (since it is invisible) for a flatter and more efficient layout hierarchy.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UselessLeaf" as explained in the Suppressing Warnings and Errors section.
+
+Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UselessLeaf" as explained in the Suppressing Warnings and Errors section.
+
+
+UselessParent
+
+Disabled By: Project lint.xml file
+
++
+A layout with children that has no siblings, is not a scrollview or a root layout, and does not have a background, can be removed and have its children moved directly into the parent for a flatter and more efficient layout hierarchy.
To suppress this error, use the issue id "UselessParent" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "UselessParent" as explained in the Suppressing Warnings and Errors section.
+
+
+UsesMinSdkAttributes
+
+Disabled By: Project lint.xml file
+
++
+The manifest should contain a
To suppress this error, use the issue id "UsesMinSdkAttributes" as explained in the Suppressing Warnings and Errors section.
+
+<uses-sdk> element which defines the minimum API Level required for the application to run, as well as the target version (the highest API level you have tested the version for).To suppress this error, use the issue id "UsesMinSdkAttributes" as explained in the Suppressing Warnings and Errors section.
+
+
+UsingHttp
+
+Disabled By: Project lint.xml file
+
++
+The Gradle Wrapper is available both via HTTP and HTTPS. HTTPS is more secure since it protects against man-in-the-middle attacks etc. Older projects created in Android Studio used HTTP but we now default to HTTPS and recommend upgrading existing projects.
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UsingHttp" as explained in the Suppressing Warnings and Errors section.
+
+Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "UsingHttp" as explained in the Suppressing Warnings and Errors section.
+
+
+ValidFragment
+
+Disabled By: Project lint.xml file
+
++
+From the Fragment documentation:
+Every fragment must have an empty constructor, so it can be instantiated when restoring its activity's state. It is strongly recommended that subclasses do not have other constructors with parameters, since these constructors will not be called when the fragment is re-instantiated; instead, arguments can be supplied by the caller with
To suppress this error, use the issue id "ValidFragment" as explained in the Suppressing Warnings and Errors section.
+
++Every fragment must have an empty constructor, so it can be instantiated when restoring its activity's state. It is strongly recommended that subclasses do not have other constructors with parameters, since these constructors will not be called when the fragment is re-instantiated; instead, arguments can be supplied by the caller with
setArguments(Bundle) and later retrieved by the Fragment with getArguments().To suppress this error, use the issue id "ValidFragment" as explained in the Suppressing Warnings and Errors section.
+
+
+VectorDrawableCompat
+
+Disabled By: Project lint.xml file
+
++
+To use VectorDrawableCompat, you need to make two modifications to your project. First, set
To suppress this error, use the issue id "VectorDrawableCompat" as explained in the Suppressing Warnings and Errors section.
+
+android.defaultConfig.vectorDrawables.useSupportLibrary = true in your build.gradle file, and second, use app:srcCompat instead of android:src to refer to vector drawables.To suppress this error, use the issue id "VectorDrawableCompat" as explained in the Suppressing Warnings and Errors section.
+
+
+VectorPath
+
+Disabled By: Project lint.xml file
+
++
+Using long vector paths is bad for performance. There are several ways to make the
+* Using less precision
+* Removing some minor details
+* Using the Android Studio vector conversion tool
+* Rasterizing the image (converting to PNG)
To suppress this error, use the issue id "VectorPath" as explained in the Suppressing Warnings and Errors section.
+
+pathData shorter:+* Using less precision
+* Removing some minor details
+* Using the Android Studio vector conversion tool
+* Rasterizing the image (converting to PNG)
To suppress this error, use the issue id "VectorPath" as explained in the Suppressing Warnings and Errors section.
+
+
+VectorRaster
+
+Disabled By: Project lint.xml file
+
++
+Vector icons require API 21 or API 24 depending on used features, but when
+
+However, there are some limitations to this raster image generation, and this lint check flags elements and attributes that are not fully supported. You should manually check whether the generated output is acceptable for those older devices.
To suppress this error, use the issue id "VectorRaster" as explained in the Suppressing Warnings and Errors section.
+
+minSdkVersion is less than 21 or 24 and Android Gradle plugin 1.4 or higher is used, a vector drawable placed in the drawable folder is automatically moved to drawable-anydpi-v21 or drawable-anydpi-v24 and bitmap images are generated for different screen resolutions for backwards compatibility.+
+However, there are some limitations to this raster image generation, and this lint check flags elements and attributes that are not fully supported. You should manually check whether the generated output is acceptable for those older devices.
To suppress this error, use the issue id "VectorRaster" as explained in the Suppressing Warnings and Errors section.
+
+
+ViewConstructor
+
+Disabled By: Project lint.xml file
+
++
+Some layout tools (such as the Android layout editor) need to find a constructor with one of the following signatures:
+*
+*
+*
+
+If your custom view needs to perform initialization which does not apply when used in a layout editor, you can surround the given code with a check to see if
To suppress this error, use the issue id "ViewConstructor" as explained in the Suppressing Warnings and Errors section.
+
++*
View(Context context)+*
View(Context context, AttributeSet attrs)+*
View(Context context, AttributeSet attrs, int defStyle)+
+If your custom view needs to perform initialization which does not apply when used in a layout editor, you can surround the given code with a check to see if
View#isInEditMode() is false, since that method will return false at runtime but true within a user interface editor.To suppress this error, use the issue id "ViewConstructor" as explained in the Suppressing Warnings and Errors section.
+
+
+ViewHolder
+
+Disabled By: Project lint.xml file
+
++
+When implementing a view Adapter, you should avoid unconditionally inflating a new layout; if an available item is passed in for reuse, you should try to use that one instead. This helps make for example ListView scrolling much smoother.
+
+More info: http://developer.android.com/training/improving-layouts/smooth-scrolling.html#ViewHolder
+
To suppress this error, use the issue id "ViewHolder" as explained in the Suppressing Warnings and Errors section.+
+
+ViewTag
+
+Disabled By: Project lint.xml file
+
++
+Prior to Android 4.0, the implementation of
To suppress this error, use the issue id "ViewTag" as explained in the Suppressing Warnings and Errors section.
+
+View.setTag(int, Object) would store the objects in a static map, where the values were strongly referenced. This means that if the object contains any references pointing back to the context, the context (which points to pretty much everything else) will leak. If you pass a view, the view provides a reference to the context that created it. Similarly, view holders typically contain a view, and cursors are sometimes also associated with views.To suppress this error, use the issue id "ViewTag" as explained in the Suppressing Warnings and Errors section.
+
+
+VisibleForTests
+
+Disabled By: Project lint.xml file
+
++
+With the
+
+This check looks for accesses from production code (e.g. not tests) where the access would not have been allowed with the intended production visibility.
To suppress this error, use the issue id "VisibleForTests" as explained in the Suppressing Warnings and Errors section.
+
+@VisibleForTesting annotation you can specify an otherwise= attribute which specifies the intended visibility if the method had not been made more widely visible for the tests.+
+This check looks for accesses from production code (e.g. not tests) where the access would not have been allowed with the intended production visibility.
To suppress this error, use the issue id "VisibleForTests" as explained in the Suppressing Warnings and Errors section.
+
+
+VulnerableCordovaVersion
+
+Disabled By: Project lint.xml file
+
++
+The version of Cordova used in the app is vulnerable to security issues. Please update to the latest Apache Cordova version.
To suppress this error, use the issue id "VulnerableCordovaVersion" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "VulnerableCordovaVersion" as explained in the Suppressing Warnings and Errors section.
+
+
+Wakelock
+
+Disabled By: Project lint.xml file
+
++
+Failing to release a wakelock properly can keep the Android device in a high power mode, which reduces battery life. There are several causes of this, such as releasing the wake lock in
+
+NOTE: If you are using the lock just to keep the screen on, you should strongly consider using
To suppress this error, use the issue id "Wakelock" as explained in the Suppressing Warnings and Errors section.
+
+onDestroy() instead of in onPause(), failing to call release() in all possible code paths after an acquire(), and so on.+
+NOTE: If you are using the lock just to keep the screen on, you should strongly consider using
FLAG_KEEP_SCREEN_ON instead. This window flag will be correctly managed by the platform as the user moves between applications and doesn't require a special permission. See http://developer.android.com/reference/android/view/WindowManager.LayoutParams.html#FLAG_KEEP_SCREEN_ON.To suppress this error, use the issue id "Wakelock" as explained in the Suppressing Warnings and Errors section.
+
+
+WakelockTimeout
+
+Disabled By: Project lint.xml file
+
++
+Wakelocks have two acquire methods: one with a timeout, and one without. You should generally always use the one with a timeout. A typical timeout is 10 minutes. If the task takes longer than it is critical that it happens (i.e. can't use
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "WakelockTimeout" as explained in the Suppressing Warnings and Errors section.
+
+JobScheduler) then maybe they should consider a foreground service instead (which is a stronger run guarantee and lets the user know something long/important is happening).Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "WakelockTimeout" as explained in the Suppressing Warnings and Errors section.
+
+
+WearStandaloneAppFlag
+
+Disabled By: Project lint.xml file
+
++
+Wearable apps should specify whether they can work standalone, without a phone app.Add a valid meta-data entry for
+
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "WearStandaloneAppFlag" as explained in the Suppressing Warnings and Errors section.
+
+com.google.android.wearable.standalone to your application element and set the value to true or false.+
<meta-data android:name="com.google.android.wearable.standalone"
+ android:value="true"/>Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "WearStandaloneAppFlag" as explained in the Suppressing Warnings and Errors section.
+
+
+WebViewLayout
+
+Disabled By: Project lint.xml file
+
++
+The WebView implementation has certain performance optimizations which will not work correctly if the parent view is using
To suppress this error, use the issue id "WebViewLayout" as explained in the Suppressing Warnings and Errors section.
+
+wrap_content rather than match_parent. This can lead to subtle UI bugs.To suppress this error, use the issue id "WebViewLayout" as explained in the Suppressing Warnings and Errors section.
+
+
+WebpUnsupported
+
+Disabled By: Project lint.xml file
+
++
+The WebP format requires Android 4.0 (API 15). Certain features, such as lossless encoding and transparency, requires Android 4.2.1 (API 18; API 17 is 4.2.0.)
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "WebpUnsupported" as explained in the Suppressing Warnings and Errors section.
+
+Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "WebpUnsupported" as explained in the Suppressing Warnings and Errors section.
+
+
+WifiManagerLeak
+
+Disabled By: Project lint.xml file
+
++
+On versions prior to Android N (24), initializing the
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "WifiManagerLeak" as explained in the Suppressing Warnings and Errors section.
+
+WifiManager via Context#getSystemService can cause a memory leak if the context is not the application context. Change context.getSystemService(...) to context.getApplicationContext().getSystemService(...).Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "WifiManagerLeak" as explained in the Suppressing Warnings and Errors section.
+
+
+WifiManagerPotentialLeak
+
+Disabled By: Project lint.xml file
+
++
+On versions prior to Android N (24), initializing the
+
+In many cases, it's not obvious from the code where the
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "WifiManagerPotentialLeak" as explained in the Suppressing Warnings and Errors section.
+
+WifiManager via Context#getSystemService can cause a memory leak if the context is not the application context.+
+In many cases, it's not obvious from the code where the
Context is coming from (e.g. it might be a parameter to a method, or a field initialized from various method calls). It's possible that the context being passed in is the application context, but to be on the safe side, you should consider changing context.getSystemService(...) to context.getApplicationContext().getSystemService(...).Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "WifiManagerPotentialLeak" as explained in the Suppressing Warnings and Errors section.
+
+
+WorldReadableFiles
+
+Disabled By: Project lint.xml file
+
++
+There are cases where it is appropriate for an application to write world readable files, but these should be reviewed carefully to ensure that they contain no private data that is leaked to other applications.
To suppress this error, use the issue id "WorldReadableFiles" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "WorldReadableFiles" as explained in the Suppressing Warnings and Errors section.
+
+
+WorldWriteableFiles
+
+Disabled By: Project lint.xml file
+
++
+There are cases where it is appropriate for an application to write world writeable files, but these should be reviewed carefully to ensure that they contain no private data, and that if the file is modified by a malicious application it does not trick or compromise your application.
To suppress this error, use the issue id "WorldWriteableFiles" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "WorldWriteableFiles" as explained in the Suppressing Warnings and Errors section.
+
+
+WrongCall
+
+Disabled By: Project lint.xml file
+
++
+Custom views typically need to call
Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "WrongCall" as explained in the Suppressing Warnings and Errors section.
+
+measure() on their children, not onMeasure. Ditto for onDraw, onLayout, etc.Note: This issue has an associated quickfix operation in Android Studio and IntelliJ IDEA.
+To suppress this error, use the issue id "WrongCall" as explained in the Suppressing Warnings and Errors section.
+
+
+WrongConstant
+
+Disabled By: Project lint.xml file
+
++
+Ensures that when parameter in a method only allows a specific set of constants, calls obey those rules.
To suppress this error, use the issue id "WrongConstant" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "WrongConstant" as explained in the Suppressing Warnings and Errors section.
+
+
+WrongRegion
+
+Disabled By: Project lint.xml file
+
++
+Android uses the letter codes ISO 639-1 for languages, and the letter codes ISO 3166-1 for the region codes. In many cases, the language code and the country where the language is spoken is the same, but it is also often not the case. For example, while 'se' refers to Sweden, where Swedish is spoken, the language code for Swedish is not
+
+This lint check looks for suspicious language and region combinations, to help catch cases where you've accidentally used the wrong language or region code. Lint knows about the most common regions where a language is spoken, and if a folder combination is not one of these, it is flagged as suspicious.
+
+Note however that it may not be an error: you can theoretically have speakers of any language in any region and want to target that with your resources, so this check is aimed at tracking down likely mistakes, not to enforce a specific set of region and language combinations.
To suppress this error, use the issue id "WrongRegion" as explained in the Suppressing Warnings and Errors section.
+
+se (which refers to the Northern Sami language), the language code is sv. And similarly the region code for sv is El Salvador.+
+This lint check looks for suspicious language and region combinations, to help catch cases where you've accidentally used the wrong language or region code. Lint knows about the most common regions where a language is spoken, and if a folder combination is not one of these, it is flagged as suspicious.
+
+Note however that it may not be an error: you can theoretically have speakers of any language in any region and want to target that with your resources, so this check is aimed at tracking down likely mistakes, not to enforce a specific set of region and language combinations.
To suppress this error, use the issue id "WrongRegion" as explained in the Suppressing Warnings and Errors section.
+
+
+WrongThread
+
+Disabled By: Project lint.xml file
+
++
+Ensures that a method which expects to be called on a specific thread, is actually called from that thread. For example, calls on methods in widgets should always be made on the UI thread.
To suppress this error, use the issue id "WrongThread" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "WrongThread" as explained in the Suppressing Warnings and Errors section.
+
+
+WrongThreadInterprocedural
+
+Disabled By: Default
+
++
+Searches for interprocedural call paths that violate thread annotations in the program. Tracks the flow of instantiated types and lambda expressions to increase accuracy across method boundaries.
To suppress this error, use the issue id "WrongThreadInterprocedural" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "WrongThreadInterprocedural" as explained in the Suppressing Warnings and Errors section.
+
+
+WrongViewCast
+
+Disabled By: Project lint.xml file
+
++
+Keeps track of the view types associated with ids and if it finds a usage of the id in the Java code it ensures that it is treated as the same type.
To suppress this error, use the issue id "WrongViewCast" as explained in the Suppressing Warnings and Errors section.
+
+To suppress this error, use the issue id "WrongViewCast" 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
+2. With a
+3. With a //noinspection comment in the source code
+4. With ignore flags specified in the
+5. With a
+6. With a
+7. With the --ignore flag passed to lint.
+
+To suppress a lint warning with an annotation, add a
+
+To suppress a lint warning with a comment, add a
+
+To suppress a lint warning in an XML file, add a
+
+
+To suppress a lint warning in a
+
+android {
+ lintOptions {
+ disable 'TypographyFractions','TypographyQuotes'
+ }
+}
+
+Here we specify a comma separated list of issue id's after the disable command. You can also use
+
+To suppress lint warnings with a configuration XML file, create a file named
+
+The format of the
+
+<?xml version="1.0" encoding="UTF-8"?>
+<lint>
+ <!-- Ignore everything in the test source set -->
+ <issue id="all">
+ <ignore path="*/test/*" />
+ </issue>
+
+ <!-- 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" />
+ <ignore regexp="(foo|bar).java" />
+ </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:
+
+
+For more information, see http://g.co/androidstudio/suppressing-lint-warnings
+ +
+ +
+1. With a
@SuppressLint annotation in the Java code+2. With a
tools:ignore attribute in the XML file+3. With a //noinspection comment in the source code
+4. With ignore flags specified in the
build.gradle file, as explained below+5. With a
lint.xml configuration file in the project+6. With a
lint.xml configuration file passed to lint via the --config flag+7. 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 with a comment, add a
//noinspection id comment on the line before the statement with the error.+
+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 module in which it applies.+
+The format of the
lint.xml file is something like the following:+
+<?xml version="1.0" encoding="UTF-8"?>
+<lint>
+ <!-- Ignore everything in the test source set -->
+ <issue id="all">
+ <ignore path="*/test/*" />
+ </issue>
+
+ <!-- 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" />
+ <ignore regexp="(foo|bar).java" />
+ </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
+ +