- Bug fix where a null reference exception occurs because the timestamp of the
Position
could benull
when fetching aPlacemark
using theplacemarkFromAddress
orplacemarkFromCoordinates
methods.
- breaking The
getPositionStream
method now directly returns an instance of theStream<Position>
class, meaning there is no need toawait
the method before being able to access the stream; - breaking Arguments for the methods
getCurrentPosition
andgetLastKnownPosition
are now named optional parameters instead of positional optional parameters; - By default Geolocator will use FusedLocationProviderClient on Android when Google Play Services are available. It will fall back to LocationManager when it is not available. You can override the behaviour by setting
Geolocator geolocator = Geolocator()..forceAndroidLocationManager = true;
- Allow developers to specify a desired interval for active location updates, in milliseconds (Android only).
- Added timestamp to instances of the
Position
class indicating when the GPS fix was acquired; - Updated the dependency on the
PermissionHandler
to version >=2.0.0 <3.0.0.
- Fixed bug on Android when not supplying a locale while using the Geocoding features.
- Added support to supply a locale when using the
placemarkFromAddress
andplacemarkFromCoordinates
methods. - Depracated the static method
checkGeolocationStatus
in favor of the instance methodcheckGeolocationPermissionStatus
(the static version will be removed in version 2.0 of the Geolocator plugin).
- Added feature to check the availability of Google Play services on the device (using the
checkGooglePlayServicesAvailability
method). This will allow developers to implement a more user friendly experience regarding the usage of Google Play services (for more information see the article Set Up Google Play Services); - Fixed the error
'List<dynamic>' is not a subtype of type 'Future<dynamic>'
on Flutter 0.6.2 and higher (thanks @fawadkhanucp for reporting the issue and solution); - Fixed an error when calling the
getCurrentPosition
,getPositionStream
,placemarkFromAddress
andplacemarkFromCoordinates
from an Android background service (thanks @sestegra for reporting the issue and creating a pull-request).
- Hot fix to solve cast exception
- Fixed a bug which caused stationary location updates not to be streamed when using the new
FusedLocationProviderClient
on Android (thanks @audkar for the PR).
- Use the Location Services (through the
FusedLocationProviderClient
) on Android if available, otherwise fallback to theLocationManager
class; - Make sure that on Android the last know location is returned immediately on the stream when requesting location updates through the
getPositionStream
method; - Updated documentation on adding location permissions on Android.
- It is now possible to check the location permissions using the
checkGeolocationStatus
method [ISSUE #51]. - Improved the example App [ISSUE #54]
- Solved a bug on Android causing a memory leak when you stop listening to the position stream.
- breaking Solved a bug on Android where permissions could be requested more then once simultaniously [ISSUE #58]
- Solved a bug on Android where requesting permissions twice would cause the App to crash [ISSUE #61]
Important:
To be able to correctly fix issue #58 we had to change the
getPositionStream
method into aasync
method. This means the signature of the method has been changed from:
Stream<Position> getPositionStream([LocationOptions locationOptions = const LocationOptions()])
to
Future<Stream<Position>> getPositionStream([LocationOptions locationOptions = const LocationOptions()])
.Meaning as a developer you'll now have to
await
the result of the method to get access to the actual stream.
- Added feature to query the last known location that is stored on the device using the
getLastKnownLocation
method; - breaking Renamed the
getPosition
togetCurrentPosition
; - Fixed bug where calling
getCurrentPosition
on Android resulted in returning the last known location; - breaking Renamed methods
toPlacemark
andfromPlacemark
respectively to the, more meaningfull names,placemarkFromAddress
andplacemarkFromCoordinates
;
- Added support for iOS
kCLLocationAccurayBestForNavigation
(defaults tobest
when on Android).
- Added the option to check the distance between two geocoordinates (using the
distanceBetween
method).
- Make sure that an Android App using the plugin is informed when the platform stops transmitting location updates.
- Added feature to throttle the amount of locations updates based on a supplied distance filter.
Important:
This introduces a breaking change since the signature of the
getPositionStream
has changed fromgetPositionStream(LocationAccuracy accuracy)
togetPositionStream(LocationOptions locationOptions)
.
- Made some small changes to ensure the plugin no longer is depending on JAVA 8, meaning the plugin will run using the default Android configuration.
- Added support to translate an address into geocoordinates and vice versa (a.k.a. Geocoding). See the README.md file for more information.
- Fixed reported formatting issues
- Fixed a warning generated by xCode when compiling the example project (see issue #28)
- Fixed some warnings generated by Dart static code analyser, improving code quality
- Introduced the option to supply a desired accuracy.
Important:
This introduces a breaking change, the
getPosition
andonPositionChanged
properties have been replaced by methods (getPosition([LocationAccuracy desiredAccuracy = LocationAccuracy.Best])
andgetPositionStream([LocationAccuracy desiredAccuracy = LocationAccuracy.Best])
respectively) accepting a parameter to indicate the desired accuracy.
- Updated the Android part to make use of the LocationManager instead of the FusedLocationProviderClient
- Improved support for handling position requests that happen in rapid succession.
- Updated documentation
- API defined stable
- Solved problem with missing geolocator-Swift.h header file (see also issue Flutter#16049).
- Initial release