Repository navigation
Request approximate location only (drop ACCESS_FINE_LOCATION) - #85
Merged
Merged
Conversation
Google Play's minimum-scope location policy (effective 2027-01-27, all apps regardless of targetSdk) allows ACCESS_FINE_LOCATION only when neither the location button nor ACCESS_COARSE_LOCATION can support the feature. A weather forecast works on approximate location - Play's own guidance names "regional weather" as a coarse use case - so request coarse only. This also avoids the precise-location Play declaration. - Manifest: remove ACCESS_FINE_LOCATION. - MainActivity: request only ACCESS_COARSE_LOCATION, and base the "deniedForever" check on it; checking the now-undeclared fine permission would report every ordinary denial as deniedForever. - LocationProvider: permission check looks at coarse only. - SECURITY.md: update the permission list. - PRIVACY_POLICY.md: "device's GPS" -> "device's location services", heading matches the in-app "Current location"; bump both dates as the policy's change clause requires. "Approximate" is deliberately not claimed yet: builds that request precise location stay in use until this release fully replaces them. Android 12+ users who picked "Approximate" already run this coarse-only path. Verified: make analyze, make test (Dart + Kotlin), debug build, :app:lintDebug; merged manifest's only location permission is now ACCESS_COARSE_LOCATION. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
| Duplication | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Google Play's minimum-scope location policy (effective 2027-01-27, all apps regardless of targetSdk) allows ACCESS_FINE_LOCATION only when neither the location button nor ACCESS_COARSE_LOCATION can support the feature. A weather forecast works on approximate location - Play's own guidance names "regional weather" as a coarse use case - so request coarse only. This also avoids the precise-location Play declaration.
Android 12+ users who picked "Approximate" already run this coarse-only path. Verified: make analyze, make test (Dart + Kotlin), debug build, :app:lintDebug; merged manifest's only location permission is now ACCESS_COARSE_LOCATION.