1190418 - After OTA update, already authorized geolocation apps need permission again

Status: RESOLVED WORKSFORME

(Core Graveyard :: DOM: Apps, defect, P3)

Description

[Sheeri Cabral [:sheeri]]

tl;dr after the OTA update this morning to buildid 20150727151800, apps that previously had permission for location services needed to gain permission again.

I did an OTA update this morning, and geolocation no longer works - tried it out in the TomTom Beta, Google Maps and the add-on for temperature in the status bar - all are complaining about lack of geolocation. I went to settings, and turned it off and on again, but still had the same problems.

Went to the GPS Calibration app, and I was asked if I wanted to share geolocation data with it (which I have said OK and Remember My Choice in the past). Clicked OK and Remember My Choice, and ran the app. The app seemed to run smoothly but none of the apps that use geolocation work.

Then I restarted the phone. Upon reboot, I got a "System would like to know your location" and so I shared it. Now, all the apps that use geolocation work, although they ask if I want to share data again (e.g. if I open Check-in Fox).

I'm not sure why apps and the system itself lost these permissions, and I'm not sure why I had to manually reboot the system for the system and apps to ask again.

Comment 1

[Nika Layzell [:nika] (ni? for response)]

This bug may be caused by bug 1189070 (I'm not sure what the URIs look like for system permissions in b2g, or if they would be affected by the error in that bug).

Comment 2

[Mahendra Potharaju [:mahe]]

[Blocking Requested - why for this release]:

Comment 3

[Pi Wei Cheng [:piwei] (inactive)]

I was NOT able to reproduce this issue. I flashed to Aries RC4 build on 6/19, ensured that geolocation worked on Google Maps via Browser and Here Maps app downloaded from Marketplace, updated the phone to dogfood-latest, and geolocation still worked on Google Maps and Here Maps.

Leaving qawanted tag for someone else to attempt.

Issue does NOT repro on this build after OTA:
Device: Aries
BuildID: 20150807120638
Gaia: 59ce66c60e71b434061aeaf11e945814b234c355
Gecko: 3e51753a099f
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 42.0a1 (2.5 Master) 
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0

Comment 4

[Martin Shuman [:Marty]]

I was able to reproduce this issue by flashing back to the RC4 build on 6/19, ensuring that geolocation had been enabled and set to remember on the Camera, Maps Online, and Calibrate GPS apps.  I then OTA'd using the dogfood-test channel, and after the update, all three apps requested geolocation permission again. I did not have any trouble with geolocation functionality after granting permission, however.

Environmental Variables:
Device: Aries 2.5
Build ID: 20150806112625
Gaia: 497fe3f938722b0aa49c93f975fad5d9ed3b0a82
Gecko: 22476236b3e1
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 42.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0

I was NOT able to reproduce issue on Flame devices, using the same apps and steps.

Environmental Variables:
Device: Flame 2.5
Build ID: 20150807030205
Gaia: 59ce66c60e71b434061aeaf11e945814b234c355
Gecko: 91de9c670800
Gonk: 41d3e221039d1c4486fc13ff26793a7a39226423
Version: 42.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0

Comment 5

[Gregor Wagner [:gwagner]]

Fabrice, any idea where this is coming from?

Comment 6

[[:fabrice] Fabrice Desré]

Hm, that should have been fixed by bug 1022791. Maybe we regressed? Our lack of OTA testing is not helping there...

Comment 7

[Mahendra Potharaju [:mahe]]

Blocked for 2.5. Need to identify what caused this issue.

Comment 8

[Martin Shuman [:Marty]]

I am able to reproduce this issue when running an OTA on the ‘dogfood-latest’ channel by updating from both the RC4 6/19 build as well as the earliest dogfood build available, from 6/03.

Because this is an OTA issue, we will be unable to run a regression window on this.

Environmental Variables:
Device: Aries 2.5
BuildID: 20150603164854
Gaia: ff80db87926a5c2769e158801090465b4ed117fa
Gecko: 196d99aabc27
Gonk: 3af1ede0d0956cfbf9c549df7cd9a6807a9efdf2
Version: 41.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

Comment 9

[Alberto Pastor [:albertopq]]

Let's try to find a regression window

Comment 10

[Jayme Mercado [:JMercado] (Inactive 3/4/2016)]

A regression window cannot be found for this issue per comment 8

Comment 11

[Mahendra Potharaju [:mahe]]

Fabrice, 

Can you please set a priority for this issue and also find an owner?

Thanks

Comment 12

[[:fabrice] Fabrice Desré]

I don't think this should be very high priority given how infrequent updates are. And I don't know of anyone available to take that :(

Comment 13

[Mahendra Potharaju [:mahe]]

Setting P3 priority based on comment 12.

Comment 14

[Mahendra Potharaju [:mahe]]

[Blocking Requested - why for this release]:

QAnalysts, Can you please check if this issue still exists?

Setting to nomination and removing the blocker flag.

Comment 15

[Pi Wei Cheng [:piwei] (inactive)]

The issue where Geolocation permission setting is NOT remembered after OTA is still occurring. I think I did see this when I did comment 3, but the issue where geolocation doesn't work in apps after OTA did not repro for me at comment 3 and still did not repro for me today. Apps worked fine with geolocation after I granted them permissions again after OTA.

Geolocation did work but permission was not remembered after OTA to:
Device: Aries 2.5
BuildID: 20151019104907
Gaia: f75bd584aca0a751a5bed115800250faa8412927
Gecko: d3e87bb40753327550143ba8ac8ee27b300cd4a9
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 44.0a1 (2.5) 
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0

Comment 16

[Mahendra Potharaju [:mahe]]

Sheeri, 

Can you confirm if you are still seeing a similar problem? Want to see if this needs to be fixed in 2.5

Thanks

Comment 17

[Sheeri Cabral [:sheeri]]

I haven't seen the problem in any of the OTA updates (or even side-load ones) since the original bug filing.

Comment 18

[Mahendra Potharaju [:mahe]]

Great. Thanks Sheeri. Will close this for now, please re-open if you encounter it again.