Bug 15201 - Xamarin.Geolocation.Geolocator GetPositionAsync always returns a canceled task.
Summary: Xamarin.Geolocation.Geolocator GetPositionAsync always returns a canceled task.
Status: RESOLVED FIXED
Alias: None
Product: Mobile API (Preview)
Classification: Xamarin
Component: Xamarin.Android ()
Version: Preview
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bill Holmes
URL:
Depends on:
Blocks:
 
Reported: 2013-10-04 08:08 UTC by George Piva
Modified: 2017-05-23 21:35 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description George Piva 2013-10-04 08:08:57 UTC
I am unable to get locations using the Xamarin.Mobile component.
Whenever I ask geolocator.GetPositionAsync (...) it returns a canceled task without any results.

Please take a look at:
https://github.com/xamarin/Xamarin.Mobile/issues/6

Are some of you able to reproduce the problem?
Comment 1 George Piva 2013-11-24 07:26:40 UTC
Just updating the correct GitHub issue url:
https://github.com/xamarin/Xamarin.Mobile/issues/16
Comment 2 Matthew Leibowitz 2017-05-23 21:35:32 UTC
Closing this as the GitHub issue was resolved.