/home/jenkins/.jenkins/workspace/Respect-classes/respect-app-compose/build.gradle.kts:132: Warning: Not targeting the latest versions of Android; compatibility modes apply. Consider testing and updating this version. Consult the android.os.Build.VERSION_CODES javadoc for details. [OldTargetApi]
        targetSdk = libs.versions.android.targetSdk.get().toInt()
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/jenkins/.jenkins/workspace/Respect-classes/gradle/libs.versions.toml:5: Warning: Not targeting the latest versions of Android; compatibility modes apply. Consider testing and updating this version. Consult the android.os.Build.VERSION_CODES javadoc for details. [OldTargetApi]
android-targetSdk = "35"
                    ~~~~

   Explanation for issues of type "OldTargetApi":
   When your application or sdk runs on a version of Android that is more
   recent than your 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:
   https://developer.android.com/reference/android/os/Build.VERSION_CODES.html
   as well as follow this guide:
   https://developer.android.com/distribute/best-practices/develop/target-sdk.
   html

   https://developer.android.com/distribute/best-practices/develop/target-sdk.html

/home/jenkins/.jenkins/workspace/Respect-classes/gradle/wrapper/gradle-wrapper.properties:4: Warning: A newer version of Gradle than 8.13 is available: 8.14.3 [AndroidGradlePluginVersion]
distributionUrl=https\://services.gradle.org/distributions/gradle-8.13-bin.zip
                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/jenkins/.jenkins/workspace/Respect-classes/gradle/libs.versions.toml:2: Warning: A newer version of com.android.application than 8.11.1 is available: 8.12.0 [AndroidGradlePluginVersion]
agp = "8.11.1"
      ~~~~~~~~
/home/jenkins/.jenkins/workspace/Respect-classes/gradle/libs.versions.toml:2: Warning: A newer version of com.android.kotlin.multiplatform.library than 8.11.1 is available: 8.12.0 [AndroidGradlePluginVersion]
agp = "8.11.1"
      ~~~~~~~~
/home/jenkins/.jenkins/workspace/Respect-classes/gradle/libs.versions.toml:2: Warning: A newer version of com.android.library than 8.11.1 is available: 8.12.0 [AndroidGradlePluginVersion]
agp = "8.11.1"
      ~~~~~~~~

   Explanation for issues of type "AndroidGradlePluginVersion":
   This detector looks for usage of the Android Gradle Plugin 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.

/home/jenkins/.jenkins/workspace/Respect-classes/respect-app-compose/build.gradle.kts:127: Warning: A newer version of compileSdkVersion than 35 is available: 36 [GradleDependency]
    compileSdk = libs.versions.android.compileSdk.get().toInt()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/jenkins/.jenkins/workspace/Respect-classes/gradle/libs.versions.toml:3: Warning: A newer version of compileSdkVersion than 35 is available: 36 [GradleDependency]
android-compileSdk = "35"
                     ~~~~
/home/jenkins/.jenkins/workspace/Respect-classes/gradle/libs.versions.toml:8: Warning: A newer version of androidx.lifecycle:lifecycle-common-java8 than 2.9.1 is available: 2.9.2 [GradleDependency]
androidx-lifecycle = "2.9.1"
                     ~~~~~~~
/home/jenkins/.jenkins/workspace/Respect-classes/gradle/libs.versions.toml:8: Warning: A newer version of androidx.lifecycle:lifecycle-runtime-compose than 2.9.1 is available: 2.9.2 [GradleDependency]
androidx-lifecycle = "2.9.1"
                     ~~~~~~~
/home/jenkins/.jenkins/workspace/Respect-classes/gradle/libs.versions.toml:24: Warning: A newer version of androidx.test:runner than 1.6.2 is available: 1.7.0 [GradleDependency]
runner = "1.6.2"
         ~~~~~~~
/home/jenkins/.jenkins/workspace/Respect-classes/gradle/libs.versions.toml:25: Warning: A newer version of androidx.test:core than 1.6.1 is available: 1.7.0 [GradleDependency]
core = "1.6.1"
       ~~~~~~~
/home/jenkins/.jenkins/workspace/Respect-classes/gradle/libs.versions.toml:32: Warning: A newer version of androidx.webkit:webkit than 1.8.0 is available: 1.14.0 [GradleDependency]
androidx-webkit = "1.8.0"
                  ~~~~~~~

   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.

/home/jenkins/.jenkins/workspace/Respect-classes/gradle/libs.versions.toml:10: Warning: A newer version of org.jetbrains.androidx.navigation:navigation-compose than 2.9.0-beta03 is available: 2.9.0-beta04 [NewerVersionAvailable]
navigation = "2.9.0-beta03"
             ~~~~~~~~~~~~~~
/home/jenkins/.jenkins/workspace/Respect-classes/gradle/libs.versions.toml:21: Warning: A newer version of org.jetbrains.kotlinx:kotlinx-datetime than 0.7.0 is available: 0.7.1 [NewerVersionAvailable]
kotlinx-date-time = "0.7.0"
                    ~~~~~~~
/home/jenkins/.jenkins/workspace/Respect-classes/gradle/libs.versions.toml:22: Warning: A newer version of com.squareup.okhttp3:okhttp than 4.12.0 is available: 5.1.0 [NewerVersionAvailable]
okhttp = "4.12.0"
         ~~~~~~~~
/home/jenkins/.jenkins/workspace/Respect-classes/gradle/libs.versions.toml:30: Warning: A newer version of io.coil-kt.coil3:coil-compose than 3.2.0 is available: 3.3.0 [NewerVersionAvailable]
coilCompose = "3.2.0"
              ~~~~~~~
/home/jenkins/.jenkins/workspace/Respect-classes/gradle/libs.versions.toml:30: Warning: A newer version of io.coil-kt.coil3:coil-network-okhttp than 3.2.0 is available: 3.3.0 [NewerVersionAvailable]
coilCompose = "3.2.0"
              ~~~~~~~
/home/jenkins/.jenkins/workspace/Respect-classes/gradle/libs.versions.toml:36: Warning: A newer version of com.squareup.okhttp3:mockwebserver than 4.12.0 is available: 5.1.0 [NewerVersionAvailable]
mockwebserver =  "4.12.0"
                 ~~~~~~~~

   Explanation for issues of type "NewerVersionAvailable":
   This detector checks with a central repository to see if there are newer
   versions available for the dependencies used by this project. This is
   similar to the GradleDependency check, which checks for newer versions
   available in the Android SDK tools and libraries, but this works with any
   MavenCentral dependency, and connects to the library every time, which
   makes it more flexible but also much slower.

/home/jenkins/.jenkins/workspace/Respect-classes/gradle/libs.versions.toml:51: Hint: There are multiple dependencies io.coil-kt.coil3:coil-network-okhttp but with different version [SimilarGradleDependency]
coil-network-okhttp = { module = "io.coil-kt.coil3:coil-network-okhttp", version.ref = "coilCompose" }
                       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/jenkins/.jenkins/workspace/Respect-classes/gradle/libs.versions.toml:53: Hint: There are multiple dependencies io.coil-kt.coil3:coil-network-okhttp but with different version [SimilarGradleDependency]
coil3-network = { module = "io.coil-kt.coil3:coil-network-okhttp", version.ref = "coilCompose" }
                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   Explanation for issues of type "SimilarGradleDependency":
   This detector looks for usages of libraries when name and group are the
   same but versions are different. Using multiple versions in big project is
   fine, and there are cases where you deliberately want to stick with such
   approach. However, you may simply not be aware that this situation happens,
   and that is what this lint check helps find.

/home/jenkins/.jenkins/workspace/Respect-classes/respect-app-compose/src/androidMain/res/drawable-v24: Warning: This folder configuration (v24) is unnecessary; minSdkVersion is 24. Merge all the resources in this folder into drawable. [ObsoleteSdkInt]
/home/jenkins/.jenkins/workspace/Respect-classes/respect-app-compose/src/androidMain/res/values-v23: Warning: This folder configuration (v23) is unnecessary; minSdkVersion is 24. Merge all the resources in this folder into values. [ObsoleteSdkInt]

   Explanation for issues of type "ObsoleteSdkInt":
   This check flags version checks that are not necessary, because the
   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.

/home/jenkins/.jenkins/workspace/Respect-classes/respect-app-compose/src/androidMain/res/drawable/ic_launcher_background.xml:2: Warning: The resource R.drawable.ic_launcher_background appears to be unused [UnusedResources]
<vector xmlns:android="http://schemas.android.com/apk/res/android"
^
/home/jenkins/.jenkins/workspace/Respect-classes/respect-app-compose/src/androidMain/res/drawable-v24/ic_launcher_foreground.xml:1: Warning: The resource R.drawable.ic_launcher_foreground appears to be unused [UnusedResources]
<vector xmlns:android="http://schemas.android.com/apk/res/android"
^
/home/jenkins/.jenkins/workspace/Respect-classes/respect-app-compose/src/androidMain/res/mipmap-hdpi/ic_launcher_round.png: Warning: The resource R.mipmap.ic_launcher_round appears to be unused [UnusedResources]

   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.
   ,

   Available options:

   **skip-libraries** (default is true):
   Whether the unused resource check should skip reporting unused resources in libraries.

   Many libraries will declare resources that are part of the library surface; other modules depending on the library will also reference the resources. To avoid reporting all these resources as unused (in the context of a library), the unused resource check normally skips reporting unused resources in libraries. Instead, run the unused resource check on the consuming app module (along with `checkDependencies=true`).

   However, there are cases where you want to check that all the resources declared in a library are used; in that case, you can disable the skip option.

   To configure this option, use a `lint.xml` file with an <option> like this:

   ```xml
   <lint>
       <issue id="UnusedResources">
           <option name="skip-libraries" value="true" />
       </issue>
   </lint>
   ```

/home/jenkins/.jenkins/workspace/Respect-classes/respect-app-compose/src/androidMain/res/drawable/respect_logo.webp: Warning: Found bitmap drawable res/drawable/respect_logo.webp in densityless folder [IconLocation]
/home/jenkins/.jenkins/workspace/Respect-classes/respect-app-compose/src/androidMain/res/drawable/spix_logo.webp: Warning: Found bitmap drawable res/drawable/spix_logo.webp in densityless folder [IconLocation]

   Explanation for issues of type "IconLocation":
   The res/drawable folder is intended for density-independent graphics such
   as shapes defined in XML. For bitmaps, move it to drawable-mdpi and
   consider providing higher and lower resolution versions in drawable-ldpi,
   drawable-hdpi and drawable-xhdpi. If the icon really is density independent
   (for example a solid color) you can place it in drawable-nodpi.

   https://developer.android.com/guide/practices/screens_support.html

0 errors, 26 warnings, 2 hints
