Skip to content

Releases: psteiger/LocationFetcher

8.0.0-alpha05

06 Nov 06:58
Compare
Choose a tag to compare
8.0.0-alpha05 Pre-release
Pre-release
8.0.0-alpha05

8.0.0-alpha04

06 Nov 06:51
Compare
Choose a tag to compare
8.0.0-alpha04 Pre-release
Pre-release
8.0.0-alpha04

8.0.0-alpha03

06 Nov 06:29
Compare
Choose a tag to compare
8.0.0-alpha03 Pre-release
Pre-release
8.0.0-alpha03

8.0.0-alpha02

06 Nov 06:23
Compare
Choose a tag to compare
8.0.0-alpha02 Pre-release
Pre-release
8.0.0-alpha02

8.0.0-alpha01

06 Nov 06:16
Compare
Choose a tag to compare
8.0.0-alpha01 Pre-release
Pre-release
8.0.0-alpha01

7.0.0

12 Oct 06:44
Compare
Choose a tag to compare

API changes:

  • LocationFetcher.create() and LocationSource.create() abandoned
    in favour of builder functions LocationSource() and LocationFetcher().

  • LocationSource flows are now StateFlows instead of SharedFlows.

  • LocationSource's setCustomLocation(Location) and setPreferredSource(Source)
    changed to vars, customLocation and locationSource.

  • Dropped @ExperimentalCoroutinesApi.

  • Context.LocationFetcher() requires an explicit LifecycleOwner (previously,
    the ProcessLifecycleOwner singleton was used implicitly).
    ComponentActivity.LocationFetcher() still uses the Activity as the
    LifecycleOwner.

  • LocationFetcher.Config.requestLocationPermissions and
    LocationFetcher.Config.requestEnableLocationSettings booleans changed to:

var requestLocationPermissionOnLifecycle: Lifecycle.State? = Lifecycle.State.STARTED,
var requestEnableLocationSettingsOnLifecycle: Lifecycle.State? = Lifecycle.State.STARTED,

Which defines the Lifecycle state that will be used for asking for
location permission or location setting enablement. To disable them,
set to null.

6.0.1

26 Aug 04:12
Compare
Choose a tag to compare
Fix README.

6.0

26 Aug 03:53
Compare
Choose a tag to compare
6.0

This release contains breaking API changes:

  • The following methods do not return results anymore:

    suspend fun requestLocationPermissions()
    suspend fun requestEnableLocationSettings()

    The reason for the change is that waiting for an ActivityResult
    and holding onto the coroutine continuation meanwhile is inherently
    unsafe.

    Users should observe the following flows to get the results:

    • permissionStatus
    • settingsStatus

Non-breaking API changes:

  • New builders:
    • ComponentActivity.locationFetcher(config: LocationFetcher.Config.() -> Unit)
    • Context.locationFetcher(config: LocationFetcher.Config.() -> Unit)

Other changes:

  • Added configuration option isWaitForAccurateLocation for LocationRequest
    providers.
  • Receive location on a worker thread.
  • Bump versions and migrate gradle files from Groovy to Kotlin (.kts).
  • Depend on ComponentActivity instead of FragmentActivity.

5.22

02 Feb 03:01
Compare
Choose a tag to compare

Includes changes of library versions:

  • androidx.lifecycle: 2.3.0-beta01 to 2.2.0
  • androidx.activity: 1.2.0-beta01 to 1.2.0-rc01
  • androidx.fragment: 1.3.0-beta01 to 1.3.0-rc01
  • com.github.psteiger:flow-lifecycle-observer: 0.1.1 to 0.2.1

5.21

09 Dec 20:43
Compare
Choose a tag to compare

Provide dagger/hilt annotations for easily providing two type of instances:

  • Global (@ApplicationLocationFetcher)
  • Activity (@ActivityLocationFetcher)