Lint option "InvalidPackage" should not be disabled
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
The lint option InvalidPackage is disabled in line 94 of play-services-core/build.gradle.
This should not be supressed as it can lead to errors on runtime. What is the reasoning behind ignoring it?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at line 94 of play-services-core/build.gradle and inspect the surrounding lint configuration to understand why InvalidPackage is disabled. Run the relevant Android lint checks after changing the setting; done means InvalidPackage is no longer suppressed and the checks pass without introducing runtime-invalid package errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- build-system, mobile
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100