-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove all location permissions from sdk manifest #430
Conversation
cc @mapbox/maps-android |
Instead of removing all location permissions for all API levels, have you considered setting the value of |
@zugaldia see @nkukday's comments: https://github.com/mapbox/mobile-telemetry/issues/445#issuecomment-544612609 Looks like adding the |
For what it's worth: I just built https://github.com/mapbox/mapbox-gl-native-android perfectly fine with Was able to install the |
From https://github.com/mapbox/mobile-telemetry/issues/445#issuecomment-544612609:
great catch, this enforces configurations on users that they don't expect, 👍 on removal |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! 🚀
Codecov Report
@@ Coverage Diff @@
## master #430 +/- ##
===========================================
- Coverage 68.25% 68.2% -0.05%
Complexity 382 382
===========================================
Files 68 68
Lines 2079 2079
Branches 163 163
===========================================
- Hits 1419 1418 -1
- Misses 570 571 +1
Partials 90 90 |
Problem
For apps targeting <= Android 9 but running on Android 10, the system automatically adds ACCESS_BACKGROUND_LOCATION when updating to Android 10 if either of ACCESS_FINE_LOCATION or ACCESS_COARSE_LOCATION is declared in the manifest.
Solution
Removing all location permissions from SDK to prevent ACCESS_BACKGROUND_LOCATION being added to app's manifest as a result of inheriting location permissions from SDK.
Test
Build Navigation and Maps successfully.