Right now, mobile/android's Java code base has a huge number of lint warnings due to Android SDK version mismatches. This ticket tracks using standard practices to minimize the warnings, with the belief that we may find some real positives in the warning soup. We have rolled our own AppConstants.Versions flags, which foils the linter. Perhaps there's an equivalent construct that the linter understands? Perhaps we can make our own linter extension to handle our construct?

The simple fix is probably to liberally scatter @TargetApi(21) etc. all over the codebase, wherever an API isn't available in an earlier release.

Also, apparently this was improved recently (July): https://code.google.com/p/android/issues/detail?id=178686 https://android-review.googlesource.com/#/c/157845/ so perhaps we just need a more recent linter.

Worth noting that it is possible to write custom rules: https://github.com/googlesamples/android-custom-lint-rules However, if Richard is correct, this shouldn't be necessary. Unfortunately, I loaded fennec into Android Studio and found the warnings still present – perhaps I need to update my android SDK (updated maybe a week ago?) or these changes haven't been released into the mainline lint yet. NI self to investigate.

nalexander mentioned elsewhere that IJ15 gets features from AS1.3 – maybe this just works?

This is not fixed in IJ 15.0.3. Nick, I hear you run AS with fennec – does this just work?

(In reply to Michael Comella (:mcomella) from comment #5) > This is not fixed in IJ 15.0.3. > > Nick, I hear you run AS with fennec – does this just work? I remember being disappointed that it does not get better. I dug into the lint code and it's looking for a very specific if guard, which we don't meet with our fancy Version constants. I think we should confirm that and then inline all of those tests. Lint is more valuable than an unsubstantiated Proguard win.

Or write a custom lint rule (comment 3) for our specific checks.

Need to unassign myself atm since shift to some other works.

bug 1369631 is resolved so we can safely remove <ignore path="**/mobile/android/base/java/org/mozilla/gecko/activitystream/ActivityStreamPreference.java"/>

The dependencies here all seem related to Android, and the linting file seems to be related to android, so moving across to there, as it doesn't feel like a general build configuration issue.

Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195 Needinfo :susheel if you think this bug should be re-triaged.

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.