You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 19, 2024. It is now read-only.
Xamarin.Geolocation.Geolocator geolocator = new Xamarin.Geolocation.Geolocator (context);
geolocator.GetPositionAsync (timeout: 6000).ContinueWith (task => { // task.IsCanceled is always equal to true. });
May it be related to the initial issue?
Are there other reasons for this badly behaviour?
I can see this happening on both Xamarin.Mobile component 0.6.3 and 0.7 versions. It also happens when downloading the master branch of this repository as a Zip file and importing it inside my project.
I have just tried to run the GeolocationSample project on a Samsung Galaxy S3 and got the same results:
My beta testers are also notifying me about this localization issue and they are using different devices from me.
Not likely, each platform has a completely different implementation and this only occurs after repeatedly creating new geolocators. I created a separate issue for you: #16.
Repeatedly creating new Geolocator instances and asking for locations on WinRT ends up not returning results.
The text was updated successfully, but these errors were encountered: