Skip to content

Lint Error #4

Closed
Closed

Description

@alan412

The lint error that was in 5.5 is still here in 6.0

See: FIRST-Tech-Challenge/SkyStone#262

Activity

  1. abidingabi commented on Sep 25, 2020

    @abidingabi

    To clarify, this isn't an issue with Travis CI; this is an issue that has to do with the lint gradle task. However, this comes up in Travis CI because it likely uses some form of ./gradlew build under the hood, which would invoke the lint gradle task. This also precludes using ./gradlew build from the command line in the FTC SDK.

    Any call to the lint task will cause this error however (in this case caused by running ./gradlew lint:

    > Task :FtcRobotController:lint FAILED
    Ran lint on variant debug: 34 issues found
    Ran lint on variant release: 34 issues found
    Wrote HTML report to file:///home/dansman805/robotics/temp-ftc-sdk/FtcRobotController/build/reports/lint-results.html
    Wrote XML report to file:///home/dansman805/robotics/temp-ftc-sdk/FtcRobotController/build/reports/lint-results.xml
    
    FAILURE: Build failed with an exception.
    
    * What went wrong:
    Execution failed for task ':FtcRobotController:lint'.
    > Lint found errors in the project; aborting build.
    
      Fix the issues identified by lint, or add the following to your build script to proceed with errors:
      ...
      android {
          lintOptions {
              abortOnError false
          }
      }
      ...
    
      The first 3 errors (out of 5) were:
      /home/dansman805/robotics/temp-ftc-sdk/FtcRobotController/src/main/res/menu/ftc_robot_controller.xml:39: Error: Should use app:showAsAction with the appcompat library with xmlns:app="http://schemas.android.com/apk/res-auto" [AppCompatResource]
          android:showAsAction="never"
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      /home/dansman805/robotics/temp-ftc-sdk/FtcRobotController/src/main/res/menu/ftc_robot_controller.xml:44: Error: Should use app:showAsAction with the appcompat library with xmlns:app="http://schemas.android.com/apk/res-auto" [AppCompatResource]
          android:showAsAction="never"
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      /home/dansman805/robotics/temp-ftc-sdk/FtcRobotController/src/main/res/menu/ftc_robot_controller.xml:50: Error: Should use app:showAsAction with the appcompat library with xmlns:app="http://schemas.android.com/apk/res-auto" [AppCompatResource]
          android:showAsAction="never"
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    
    
    
    * Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
    

    Steps for reproduction:

    1. cd into the sdk's directory from the command line
    2. run ./gradlew lint (or ./gradlew build!)

    Note: this was run on Fedora, however I doubt OS would matter here

    Now of course, this isn't really an issue if you don't call ./gradlew lint, however this also occurs when you run ./gradlew build, which is the most convienient way to build from the command line and how CI would likely go about doing things.

    This can either be fixed by fixing the actual lint errors, or by adding

    android {
          lintOptions {
              abortOnError false
          }
      }

    to the build.gradle of the affected modules.

    Of course, actually fixing the lint errors would seem to be the preferred course of action.

  2. shaunsingh commented on Dec 6, 2020

    @shaunsingh

    adding

    android { lintOptions { abortOnError false } }

    still results in the same lint errors,

    however, running ./gradlew build -x lint seemed to work for me

  3. added a commit that references this issue on Sep 2, 2021
  4. alan412 commented on Sep 20, 2021

    @alan412
    Author

    This error is still there in 7.0

  5. cbrewsky commented on Sep 25, 2021

    @cbrewsky

    Can confirm, still here in 7.0...

  6. Windwoes commented on Oct 3, 2021

    @Windwoes
    Member

    This will be fixed in the next release

  7. Windwoes commented on Jan 17, 2022

    @Windwoes
    Member

    Fixed in 7.1

  8. added a commit that references this issue on Feb 15, 2022
  9. added a commit that references this issue on Oct 24, 2023
  10. added a commit that references this issue on Nov 22, 2023
  11. added a commit that references this issue on Nov 29, 2023
  12. 7 remaining items

  13. added a commit that references this issue on Dec 29, 2024
  14. added a commit that references this issue on Aug 14, 2025
  15. added a commit that references this issue on Sep 16, 2025
  16. added a commit that references this issue on Oct 30, 2025
  17. added a commit that references this issue on Nov 2, 2025
  18. added a commit that references this issue on Dec 19, 2025
  19. added a commit that references this issue on Jan 27, 2026
  20. added a commit that references this issue on Aug 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions