Skip to content
This repository has been archived by the owner on Apr 23, 2023. It is now read-only.

Simplify FusedLocationProvider Internal Check #214

Closed
sarahsnow1 opened this issue Jun 7, 2017 · 1 comment
Closed

Simplify FusedLocationProvider Internal Check #214

sarahsnow1 opened this issue Jun 7, 2017 · 1 comment

Comments

@sarahsnow1
Copy link
Contributor

sarahsnow1 commented Jun 7, 2017

Because LocationEngine#removeRequest disables and re-enables the engine (if there are still remaining requests), we no longer need to check to see if the engine should be disabled in FusedLocationProviderApi#checkAllListenersPendingIntentsAndCallbacks but as @ecgreb pointed out we could as an enhancement call LocationEngine#removeAllRequests when the last client is disconnected "to avoid this issue of needing to explicitly remove all requests before shutting down a client"

@msmollin
Copy link
Contributor

Closing as this repo is no longer maintained.

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

No branches or pull requests

2 participants