Closed Bug 855189 Opened 7 years ago Closed 2 years ago

Geolocation prompt for system app is not shown when the permission is actually used

Categories

(Firefox OS Graveyard :: Gaia::System::Lockscreen, defect)

x86
macOS
defect
Not set

Tracking

(b2g-v1.4 affected, b2g-v2.1 affected)

RESOLVED WONTFIX
Tracking Status
b2g-v1.4 --- affected
b2g-v2.1 --- affected

People

(Reporter: pauljt, Unassigned)

References

()

Details

(Whiteboard: OpenCrun1.4-3, [2.1-flame-test-run-3])

Attachments

(1 file)

STR:
Setup: You need to have lockscreen enabled with a passcode set.

1. Apply a fresh build to the phone
2. enable and set a passcode lock
3. lock the phone
4. Open the lockscreen camera 
5. Press the home button
6. unlock the phone

Expected:
A prompt for geolocation should be shown when the camera is first shown.

Actual:
After you unlock the phone, the user is immediately shown a geolocation prompt. There is no indication as to why the system needs the location , or that it is because it wants to geotag your photos.


To me, the solution to this issue is not just "show the prompt at the lockscreen". That approach would have its own security issues (especially since someone could enable this, and then you never know that your system photos were being geotagged).


I am mainly raising this from a privacy perspective (i.e. no surprises). In future versions it would nice to a UI inside the camera functions (in the system app, and camera app) that allows users to control the geotagging in a more intuitive way.
Updating this bug (hit it in OpenCrun1.4-3). Added URL, tracking flag "status-b2g-v1.4: affected", and whiteboard "OpenCrun1.4-3".
Whiteboard: OpenCrun1.4-3
Attached file Logcat
Adding the logcat
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Whiteboard: OpenCrun1.4-3 → OpenCrun1.4-3, [2.1-flame-test-run-3]
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.