tannker

Ok. Yes, what I have noticed is the position after initial load (sometimes 0, 20, 80 ms). I also noticed the same issue with seekTo to either to the start...

I have encountered the issue with latest versions in scenario when Geolocator.getCurrentPosition() is called while Geolocator.getPositionStream(locationSettings: locationSettings).listen() is active. After that position stream start to trigger every second regardless of...

I have added some additional logic to the application that makes sure that getCurrentPosition is not called while stream is active. I am storing location information from stream to state...

I stumbled on this issue today as well as a result of upgrading the package. As far as I understand, getUserData cannot be used with Limited login as it goes...