Status Update
Comments
su...@google.com <su...@google.com> #2
Oh, worth noting that rule from that sample project works fine if Lint run via console.
lo...@gmail.com <lo...@gmail.com> #3
Hi all! 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).
lb...@gmail.com <lb...@gmail.com> #4
lb...@gmail.com <lb...@gmail.com> #6
vi...@google.com <vi...@google.com> #7
lb...@gmail.com <lb...@gmail.com> #8
Something needs to trigger building the lint artifact, but as a workaround, here's what I did which made it work:
- Opened the sample project in Flamingo, and used the upgrade assistant to update it to 8.0.0-alpha10 (the same version of Flamingo I was using)
- Opened the test file ("Test) -- there's no lint warning yet
- Opened the terminal window inside the IDE (Help > Find Action > terminal)
- Ran "./gradlew lint"
That triggered a build, and once it finished, the IDE also updated to start showing the lint warning without me having to do anything else (see screenshot).
lb...@gmail.com <lb...@gmail.com> #9
However for some reason, after changing over to 8.0.0-alpha10 it started working in Flamingo Canary 10.
lb...@gmail.com <lb...@gmail.com> #10
lb...@gmail.com <lb...@gmail.com> #11
Something needs to trigger building the lint artifact
Here are 2 options that come to mind:
- Trigger building the lint.jar file during sync.
- Add a dependency from common build commands (e.g.,
assembleDebug
) to the task that creates the lint.jar file (so that at least the lint.jar file would exist more often than it does now).
Chris, do you have more context to suggest the best way forward? Both of these seem like they might cause performance regressions, and I'm not sure that option 1 is even allowed.
Description
- requires QUERY_ALL_PACKAGES, as I've shown here:
(and others)
- when targeting API 33, sadly require MANAGE_EXTERNAL_STORAGE permission, which the Play Store policy team is currently against of using, even if it's a major feature of my app:
My request:
Have an alternative function, which would just tells us as a boolean/combination-of-flags, what is the current situation for each.
Meaning that from this function, we could know only these:
For lock and/or home, do we have image/live-wallpaper/nothing being set?
You can see that I don't request anything more. No extra information. Just something that could be answered of which type is used for each place.