Lint does not seem to detect correct API levels #2363
Comments
dellis1972
added a commit
to dellis1972/xamarin-android
that referenced
this issue
Nov 2, 2018
Fixes dotnet#2360, dotnet#2361, dotnet#2362, dotnet#2363 When running the `Lint` checks on an application we provide a path to a `project` directory. This is currently the `$(IntermediateOutputPath)`. The problem with this is that it also includes the `lp` directory. The `lp` directory contains ALL the resources and Manifest files for the library projects. As a result if you are referencing support packages ALL of those items are checked too. It turns out that most of the Manifest files shipped with the libraries are not complete or will cause `lint` errors or warnings. So what we need to do is point the `lint` check at the `$(IntermediateOutputPath)android`. This will restrict the checks to the files which the Build system produces (the java code, and the final app manifest). This PR includes an updated unit test which tests all the issues raised in the bug reports.
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Steps to Reproduce
Exactly the same as #2360.
Probably related to #2361.
Expected Behavior
My manifest says the minimum API level is 24, so I should not get any warnings or errors about API levels lower than 24.
Actual Behavior
A lot of errors in the log file of the following types (see log file below):
Version Information
Exactly the same as #2360.
Log File
The text was updated successfully, but these errors were encountered: