You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used AS 4.1.1. Imported the project and could see the custom rule highlighting. Then I updated to 4.2.2, reseted AS to its defaults and re-imported the project. Since that moment custom rule highlighting doesn't work. However, the issue is reported when I run ./gradlew :app:lint.
Besides, even with the OLD AS version the custom rule highlighting didn't work in MY project, but worked from the command line. What can be the reason of that? Any way I can debug it?
The text was updated successfully, but these errors were encountered:
I face the same issue when using AS 4.2.2. I've tried on macOS and on Windows, but I can't see highlighting. I don't see highlighting neither opening the project nor after running :app:lint command (but I can see errors in the console).
I also experience this issue, the only fix that worked for me was to manually copy the generated jar file for the rule(checks.jar) into ~./android/lint. Doing this enabled the highlighting in AS (macos)
I also experience this issue, the only fix that worked for me was to manually copy the generated jar file for the rule(checks.jar) into ~./android/lint. Doing this enabled the highlighting in AS (macos)
Something is definitely broken. Lint integration must not be that unstable. I wish we had tools to debug what's going wrong.
I reported the issue to Google. Could you please +1 it as well? https://issuetracker.google.com/issues/192776762
I used AS 4.1.1. Imported the project and could see the custom rule highlighting. Then I updated to 4.2.2, reseted AS to its defaults and re-imported the project. Since that moment custom rule highlighting doesn't work. However, the issue is reported when I run ./gradlew :app:lint.
Besides, even with the OLD AS version the custom rule highlighting didn't work in MY project, but worked from the command line. What can be the reason of that? Any way I can debug it?
The text was updated successfully, but these errors were encountered: