Bug 9051 - No first position update without moving
Summary: No first position update without moving
Status: RESOLVED FIXED
Alias: None
Product: Mobile API (Preview)
Classification: Xamarin
Component: Xamarin.iOS ()
Version: Preview 0.6.1
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bill Holmes
URL:
Depends on:
Blocks:
 
Reported: 2012-12-19 10:56 UTC by ursin.brunner@gmail.com
Modified: 2017-05-24 23:54 UTC (History)
2 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 ursin.brunner@gmail.com 2012-12-19 10:56:49 UTC
We try to use the the Geolocator in listener-mode. For that we call Geolocator.StartListening and we expect a first position-update (at least within a few seconds), even without moving. On the simulator, that works as expected (except if you set Location->none) but on the real device, we never get a position-update without moving. The apple specification for CLocationManager defines that you always get an initial position-update after calling the start-listening method (other naming in CLocationmanager but same functionality). It would be nice this behaviour is the same with the Geolocator-class, because otherwise we have no possibility to get the users initial-position. As a workaround we use the native CLocartionManager from Apple at the moment, but it would be nice if we could drop him because of code-reuse for our other platforms.

Thx for fixing this bug and keep on the good work, we all love mono!

Apple-spec of CLocationManager:
https://developer.apple.com/library/mac/#documentation/CoreLocation/Reference/CLLocationManager_Class/CLLocationManager/CLLocationManager.html
Comment 1 Matthew Leibowitz 2017-05-24 23:54:20 UTC
I was not able to reproduce this with the latest version (v0.7.7), and thus I conclude that it was resolved in an update. Feel free to open an issue if this is still the case.

In addition, the Mobile API is being deprecated in favor of various plugins (which have the equivalent/same API):
 - Contacts: https://www.nuget.org/packages/Xam.Plugin.Contacts
 - Geolocator: https://www.nuget.org/packages/Xam.Plugin.Geolocator
 - Media: https://www.nuget.org/packages/Xam.Plugin.Media

This plugin model has several advantages:
 - Each plugin is independent, and can be updated as such
 - It is no longer an all-or-nothing package
 - Plugins can be mixed/replaced with other plugins that offer similar features

Thanks for using the Mobile API, and we hope that the new plugin model will enable you to produce even better mobile apps.