sarsenyev Reporter
	Description • 12 years ago

Description:
 The Geolocation worked on previous build, but after today’s update on "Unagi"    phone, build ID:20130123070202, the geolocation doesn't work, even if you  restart the phone or reset it, with WI-FI on and off (data only)
 
 Steps to reproduce:
 1. Update “Unagi” phone with build ID:20130123070202
 2. Turn device ON
 3. Tap on “unlock” button if it’s locked
 4. Slide right to see icons
 5. Tap on “Here Maps” icon
 6  Tap “I have read and agree to the Nokia Service Terms & Privacy Policy”     make sure it’s marked
 7. Tap on "start" and wait for awhile

 Actual result:
 Nothing happened, no location found, to verify tap on “Setting” button in the  right corner and then tap “Route” icon, warning message will appear: “Can’t find your location. Please enter your starting point above".

 Notes:
 Repro’ed  5/5 on 3 devices
 This bug refers to bug ID:815217

	Jason Smith [:jsmith]
	Comment 1 • 12 years ago

I believe this issue was mentioned in today's apps meeting was due to the fact that the maps app packaged is failing to call out the geolocation permission. So we'll never get the prompt.

	sarsenyev Reporter
	Comment 2 • 12 years ago

Kernel Dec 5

	Donovan Preston [:fzzzy] Assignee
	Comment 3 • 12 years ago

Ok, after updating the manifest file to ask for the geolocation and storage permissions, geolocation works once again in the maps app.

Apparently there was a tightening of restrictions lately and apps now need to explicitly request the permissions they need, even if those capabilities would normally be a part of the mobile web dom.

We are adding the updated package to the marketplace, and I will be making a pull request to refer to the new package once this is ready.

	John Ford [:jhford] CET/CEST Berlin Time
	Comment 5 • 12 years ago

This was landed on v1-train with:
https://github.com/mozilla-b2g/gaia/commit/c9ad0e0c3e177012a950f5b0f567b6167766825e

This was landed on v1.0.0 with:
https://github.com/mozilla-b2g/gaia/commit/f2a79575b32ecbbe1708a55a24a1a56e01a4249f

	Lukas Blakk [:lsblakk] use ?needinfo
	Comment 6 • 12 years ago

updating status flags as per comment 5.

	Jeni
	Comment 7 • 12 years ago

Verified issue is fixed on build 20130212070205 Dec 5th Kernel