Bad GPS coordinates returned on IPhone device

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Call Display.getInstance().getLocationManager().getCurrentLocation();

What is the expected output? What do you see instead?
On the iPhone, I'm getting a location that would put me somewhere in the South 
Atlantic Ocean near Cameroon, but I'm actually in Canada.  I verified that the 
iPhone Maps is able to show my current position.  Also verified that I get the 
correct coordinates from this call on a Symbian device.

What version of the product are you using? On what operating system?
0.1 Build 20120315 on Ubuntu 11.10, IPhone 3G on IOS 4.2.1

Original issue reported on code.google.com by 1815...@coolman.ca on 21 Mar 2012 at 12:49

[GoogleCodeExporter]

I'll take a look, its probably a difference between the iOS and Android 
coordinate system. Thanks!

Original comment by shai.almog on 21 Mar 2012 at 4:03

• Changed state: Accepted
• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I'm assuming you are checking whether the connection is available  but aren't 
listening to location events though, right?
I'm guessing the available value is marked as available despite the data not 
being there yet. I'll try to write a test case for the location functionality 
so I can verify it more easily.

Original comment by shai.almog on 21 Mar 2012 at 6:24

[GoogleCodeExporter]

I made some fixes here, I'm not sure if they work since we don't have a proper 
demo for location (its in my huge todo list).
I'm deploying to the servers right now so it should just work in future builds.

Original comment by shai.almog on 21 Mar 2012 at 3:50

• Changed state: Fixed

[GoogleCodeExporter]

I missed your previous note, most of your assumption was correct, except I 
didn't test the status first (oops).  I have my iphone loaned out for moment 
but will add that check and resubmit to try it again later this eve.

Original comment by 1815...@coolman.ca on 21 Mar 2012 at 8:32

[GoogleCodeExporter]

The update worked, got the right coordinates this time, thanks!

Original comment by 1815...@coolman.ca on 22 Mar 2012 at 2:12