Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 2611 [details]
May be related to this bug (https://bugzilla.xamarin.com/show_bug.cgi?id=7428).
The CLLocationManager's UpdateLocation event is not firing since upgrading the MT 6.0.0 and ARMv7. Neither is the Failed event.
In the above mentioned bug, there is a solution that shows that the Xamarin Mobile dll is not picking up the location either in the simulator or device. So I rewrote it to use the CLLocationManager (class attached) and I still am unable to get a lock on the device's location.
You need to handle the LocationUpdated event instead of UpdateLocation event in iOS6.
See here for more information: http://lists.ximian.com/pipermail/monotouch/2012-September/011799.html