Details
-
Bug
-
Resolution: Fixed
-
P2: Important
-
6.6, 6.7, 6.8.0 FF
-
None
-
-
5
-
693d6d5bb (dev), 3a0f68e2b (6.8), 804857158 (6.7)
-
Foundation Sprint 115
Description
This bugreport results from this Jira comment by ntadej.
After https://codereview.qt-project.org/c/qt/qtpositioning/+/459939 got merged, the QtPositioning Android backend no longer requests the needed permissions, but only checks if they are granted.
The old code was always requesting the precise location (android.permission.ACCESS_FINE_LOCATION), however now the user might want to request only approximate location (android.permission.ACCESS_COARSE_LOCATION) and we should still handle it properly.
However, the fix is more complicated than simply checking for both types of permissions.
The tricky part is that QGeoSatelliteInfoSource cannot work without coarse location at all, while QGeoPositionInfoSource methods rely on preferredPositioningMethods.
Attachments
For Gerrit Dashboard: QTBUG-127847 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
585984,5 | Android: fix location permission check | dev | qt/qtpositioning | Status: MERGED | +2 | 0 |
587830,2 | Android: fix location permission check | 6.8 | qt/qtpositioning | Status: MERGED | +2 | 0 |
587852,3 | Android: fix location permission check | 6.7 | qt/qtpositioning | Status: MERGED | +2 | 0 |