Skip to content
This repository was archived by the owner on Jun 19, 2024. It is now read-only.

Repeat new Geolocators fails to return values #6

Open
ermau opened this issue Apr 17, 2013 · 3 comments
Open

Repeat new Geolocators fails to return values #6

ermau opened this issue Apr 17, 2013 · 3 comments

Comments

@ermau
Copy link
Member

ermau commented Apr 17, 2013

Repeatedly creating new Geolocator instances and asking for locations on WinRT ends up not returning results.

@ghost ghost assigned ermau Apr 22, 2013
@ermau
Copy link
Member Author

ermau commented Apr 24, 2013

I saw this first hand at Evolve, but have not been able to reproduce it locally.

@georgepiva
Copy link

I think I am facing the same issue on Android.

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:

screenshot_2013-10-03-15-00-52

My beta testers are also notifying me about this localization issue and they are using different devices from me.

@ermau
Copy link
Member Author

ermau commented Oct 9, 2013

I think I am facing the same issue on Android.

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants