/Users/spollom/AndroidStudioProjects/Bug186806269_ignored_lint_xml/app/src/main/res/layout/content_main.xml:8: Warning: Replace the <fragment> tag with FragmentContainerView. [FragmentTagUsage from fragment-1.2.4]
    <fragment
     ~~~~~~~~

   Explanation for issues of type "FragmentTagUsage":
   FragmentContainerView replaces the <fragment> tag as the preferred         
          way of adding fragments via XML. Unlike the <fragment> tag,
   FragmentContainerView                 uses a normal FragmentTransaction
   under the hood to add the initial fragment,                 allowing
   further FragmentTransaction operations on the FragmentContainerView        
           and providing a consistent timing for lifecycle events.

   https://developer.android.com/reference/androidx/fragment/app/FragmentContainerView.html

   Vendor: Android Open Source Project (fragment-1.2.4)
   Identifier: fragment-1.2.4
   Feedback: https://developer.android.com/jetpack/androidx/releases/appcompat#feedback

/Users/spollom/AndroidStudioProjects/Bug186806269_ignored_lint_xml/app/build.gradle:57: Warning: A newer version of androidx.navigation:navigation-fragment-ktx than 2.3.4 is available: 2.3.5 [GradleDependency]
    implementation 'androidx.navigation:navigation-fragment-ktx:2.3.4'
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Users/spollom/AndroidStudioProjects/Bug186806269_ignored_lint_xml/app/build.gradle:58: Warning: A newer version of androidx.navigation:navigation-ui-ktx than 2.3.4 is available: 2.3.5 [GradleDependency]
    implementation 'androidx.navigation:navigation-ui-ktx:2.3.4'
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   Explanation for issues of type "GradleDependency":
   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.

/Users/spollom/AndroidStudioProjects/Bug186806269_ignored_lint_xml/app/build.gradle:59: Warning: Avoid using + in version numbers; can lead to unpredictable and unrepeatable builds (junit:junit:4.+) [GradleDynamicVersion]
    testImplementation 'junit:junit:4.+'
                       ~~~~~~~~~~~~~~~~~

   Explanation for issues of type "GradleDynamicVersion":
   Using + 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.)

/Users/spollom/AndroidStudioProjects/Bug186806269_ignored_lint_xml/app/src/main/AndroidManifest.xml:6: Warning: On SDK version 23 and up, your app data will be automatically backed up and restored on app install. Consider adding the attribute android:fullBackupContent to specify an @xml resource which configures which files to backup, or just set android:fullBackupOnly=true. More info: https://developer.android.com/guide/topics/data/autobackup [AllowBackup]
        android:allowBackup="true"
        ~~~~~~~~~~~~~~~~~~~

   Explanation for issues of type "AllowBackup":
   The allowBackup attribute determines if an application's data can be backed
   up and restored. It is documented at
   https://developer.android.com/reference/android/R.attr.html#allowBackup

   By default, this flag is set to true which means application data can be
   backed up and restored by the OS. Setting allowBackup="false" opts the
   application out of being backed up and so users can't restore data related
   to it when they go through the device setup wizard.

   Allowing backups may have security consequences for an application.
   Currently 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.

   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 or android:fullBackupOnly to
   configure auto backup.

   https://developer.android.com/guide/topics/data/autobackup

/Users/spollom/AndroidStudioProjects/Bug186806269_ignored_lint_xml/app/src/main/res/values/strings.xml:11: Warning: The resource R.string.hello_second_fragment appears to be unused [UnusedResources]
    <string name="hello_second_fragment">Hello second fragment. Arg: %1$s</string>
            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   Explanation for issues of type "UnusedResources":
   Unused resources make applications larger and slow down builds.

   The unused resource check can ignore tests. If you want to include
   resources that are only referenced from tests, consider packaging them in a
   test source set instead.

   You can include test sources in the unused resource check by setting the
   system property lint.unused-resources.include-tests=true, and to exclude
   them (usually for performance reasons), use
   lint.unused-resources.exclude-tests=true.

/Users/spollom/AndroidStudioProjects/Bug186806269_ignored_lint_xml/app/src/main/res/layout/fragment_second.xml:19: Warning: Consider making the text value selectable by specifying android:textIsSelectable="true" [SelectableText]
    <TextView
     ~~~~~~~~

   Explanation for issues of type "SelectableText":
   If a <TextView> is used to display data, the user might want to copy that
   data and paste it elsewhere. To allow this, the <TextView> should specify
   android:textIsSelectable="true".

   This lint check looks for TextViews which are likely to be displaying data:
   views whose text is set dynamically.

/Users/spollom/AndroidStudioProjects/Bug186806269_ignored_lint_xml/app/src/main/res/layout/activity_main.xml:23: Warning: Missing contentDescription attribute on image [ContentDescription]
    <com.google.android.material.floatingactionbutton.FloatingActionButton
     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   Explanation for issues of type "ContentDescription":
   Non-textual widgets like ImageViews and ImageButtons should use the
   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.

   https://developer.android.com/guide/topics/ui/accessibility/apps#special-cases

0 errors, 8 warnings
