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
First off thanks for the effort invested into building and maintaining this library!
I'm currently using it in a KMM project and I've noticed that sometimes multiple seconds can pass before (mainly the first) result of the .current() request resolves:
// Exampleprivateval geolocator =Geolocator.mobile()
...
suspendfungetLocationAndMoveCamera() {
when (val result = geolocator.current()) { // Can take up to several seconds before result is resolved on iOS ...
}
}
While doing some research I've noticed that this seems to be an issue for some Flutter libraries too:
I've tried doing things like trying to "pre-initialise" the Geolocator (adding and fetching during the DI setup, calling .current() during onCreate(), etc...) but none of these things seemed to make a (big/noticeable) difference.
Is this an anomaly in my setup and/or are there any suggestions you could give me to deal with this?
The text was updated successfully, but these errors were encountered:
Hey everyone,
First off thanks for the effort invested into building and maintaining this library!
I'm currently using it in a KMM project and I've noticed that sometimes multiple seconds can pass before (mainly the first) result of the
.current()
request resolves:While doing some research I've noticed that this seems to be an issue for some Flutter libraries too:
Baseflow/flutter-geolocator#964
Baseflow/flutter-geolocator#887 (comment)
I've tried doing things like trying to "pre-initialise" the Geolocator (adding and fetching during the DI setup, calling
.current()
duringonCreate()
, etc...) but none of these things seemed to make a (big/noticeable) difference.Is this an anomaly in my setup and/or are there any suggestions you could give me to deal with this?
The text was updated successfully, but these errors were encountered: